Return to Index
These constraints are used to restrict the harvesting of any given product, croptype, period or age class.
The constrained cut constraint window of LOG 2.0 is shown below.
This option specifies what periods the constraint is to apply. Checking the box All will mean that the constraint will apply for all periods. Alternatively, a period range can be entered by entering the first and last periods in the two boxes below.
Rather than repeatedly specifying the same constraint for different croptypes or age classes, the For Each option allows the same constraint be applied to every individual croptype or class of croptypes selected in the Croptype Range.
This option means that a single constraint will be applied to the model that encompasses all the croptypes or classes of croptypes specified in the Croptype Range in the constraint.
Depending on what is selected in the Category field, a range of croptypes or attribute names will be available in the Croptype Range list. Using the mouse, highlight the desired croptype ranges for which the current clearfell specification is to apply. To select consecutive items in the list, click the first item, press and hold down the [SHIFT] key and click the last item. To select non-consecutive items, press and hold [CTRL] and click each item.
The age range defines the range of age classes for which the particular constraint will apply.
To specify all age classes, simply ensure that the All Ages box is checked. Note that LOG will check this box automatically.
To specify a range of age classes, ensure that the All Ages box is not checked and enter the first and last age classes in the boxes provided below.
Select by which product the constraint will apply.
State whether the constraint is to set the amount of the selected product either equal to "=", less than "<" or greater than ">" the stated value.
The value that the constraint will have to be either equal to, less than or greater than.
The latest version of LOG now includes error checks on all inputs. This means that all fields need to have appropriate entries before the addition to the model is added. If there is something missing, or something in the wrong form, then a message is shown that prompts the user to remedy the situation.