Replanting

 

Return to Index

 

Replanting Constraints

Replanting constraints are used to restrict the replanting from a croptype or croptypes into other croptype(s).

The replanting constraint window used by LOG 2.0 is shown below.

 

Periods

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.

For Each

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.

Combination

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.

Croptype Source

The croptype that is going to be replanted into another croptype after clearfelling.

Croptype Destination

The croptypes replanted from the source croptypes applying to the constraint.

=,<,>

State whether the constraint is to set the amount replanted is either equal to "=", less than "<" or greater than ">" the stated change.

Change

If "As Percentage" is selected then the constraint is on the percentage of all land replanted from the source croptype. If "As Value" is selected then the constraint is on the volume replanted.

Error Checks*

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.

Other Changes to the LOG 2.0 Replanting Constraint Screen*

Users of the previous version would have found that the replanting constraints did not work exactly as intended. There was a small problem that existed in relation to the LP model. This problem is now fixed.

NEXT