Saving and Loading Timing Constraint Tables

Patchworks automatically opens a Timing Constraint table when started. The default table consists of all individual Blocks in the rows, with managed blocks assigned Green and unmanaged Blocks yellow. Changes to this table must be 'Saved' if the table is to be used again in another session. The Timing Constraint Table is not automatically saved when a scenario is saved, the table must be saved separately if it is to be associated with a particular scenario.

The Timing Table is saved as a CSV file with the first row representing the column headings: Unit, Zone, Period00, Period01,.... Each subsequent row represents a unique Unit, the associated Zone and availability for all planning periods. Constraints are represented by the numbers 0 (Green), 1 (Yellow) and 2 (Red). The Timing Table example below is representative of the MARTEN core areas used in the previous example.



A previously saved table can be loaded by chosing 'Load Table' from the bottom right corner of the Editor. This opens a common directory navigation dialog box to find the required table and open it. It is important to remember that loading a Timing Constraint table into a particular scenario will not affect the Block Table until it has been 'Applied'. Once the table has been applied all previously scheduled treatments are changed according to the new eligibility status, therefore load the block availability table first and then assign treatments or load the schedule file.