Return to Index
At the start of the planning horizon it is possible for areas to be transferred from one croptype to another. For example, there may be several croptypes which each represent a particular silvicultural regime. Untreated young stands may be initially assigned to a croptype arbitrarily and then transferred by LOG into the optimum croptype regime.
The LOG 2.0 transfer screen is shown below.
Specify the age range for which the transfers are permissable.
Original and Destination Croptype Range
For each set of particular transfers, it is necessary to specify the initial croptypes or the original croptype range; and the destination croptype range.
The Original and Destination Croptype Ranges are defined by first specifying a Croptype Category and then the appropriate Croptype Range.
Optional and Compulsory Transfers
Transfers can be either optional or compulsory. If a transfer is compulsory then the area in a specified age range must be transferred to the specified destination croptype. If the transfer is optional however, LOG decides whether it is optimal to conduct the transfer between croptypes.
Using the mouse, check the appropriate box to specify whether the transfer is optional or compulsory.
Add the associated transfer specification to the model.
If the information in a particular transfer changes after it has been added to the model using the Add button, the appropriate Update button can be used to update the information in the model.
This button will remove the corresponding transfer from the model.
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 Transfer Screen*
The transfer screen did work in LOG 1.01. The LP model for the older version was also not accurate. It did not model transfers correctly. Compulsory transfers also did not work. These problems have been fixed for the release of LOG 2.0.