Patchworks programs now record a log of their activity. These logs contain basic data including the date and time that the program was run, the program name, and all of the command line parameters that would be required to run the program. This information is logged to files name 'patchworksLog.csv' that are located in the dirctory containing the input datasets.

The edge targets algorithm has been adjusted to significantly improve performance. However, the cost of this improvement is an enormous memory requirement. The amount of memory required for an Edge target can be determined by the number of blocks, times the number of periods, times the number of edge indicators, times 8.

The patch shape metric has changed. The metric now computes the ratio of the perimeter of the patch, to the perimeter of a circle having the same area as the patch.

The patching target now accepts a 'threshold' argument that will modify how blocks are evaluated for membership in a patch. Currently, blocks will join a patch if their patching criteria is greater than 0. The new method will test if the per-unit-area value of the criteria is greater than a user specified value. The default value is 0, which gives the same behaviour as before. Use the 'control.setPatchThreshold' method to adjust the threshold value.

The accounting methods were reorganized to improve performance when multiple attributes are being added to a single account. This reorganization should yield much better performance when multiple attributes are being added into large road or patch accounts.

The patching algorithm was changed to add a significant performance improvement to the measurement of large patch objectives. This change speeds up the scheduler considerable for patches that have a large number of connected polygons.

This build adds a new sub-target to patch targets. The new target measures the amount of criteria that is contained within the patch size class.

Minor changes and fixes: