CLEM component

CLEM does not make assumptions about how users may need to define a simulation and therefore aims to provide access to specify all values used in a simulation with very few hard coded values (i.e. values considered a constant and defined in the code with no ability to be adjusted). This means the user may be overwhelmed with the range of properties that require a value. This burden is reduced by providing default values assigned upon creation of a component where appropriate, separating parameters to be defined with the appropriate component only as included, and disabling or hiding properties in the user interface when not available based on other settings. Some components such as the Ruminant type (i.e. defining a ruminant breed) contain a large list of parameters, many of which should not be changed as they relate to all ruminants, or only changed by experienced users, with detailed understanding of the underling functionality and equations, when defining a new breed.

To avoid users being tempted to change parameter values that should not be modified some components use the user type specified here to group parameters to better define their level and limit the access to high level parameters not appropriate to the user. The following user types are available.

General

This represents a general CLEM user who is building a simulation. The properties available will include all those needed to define the simulation and the farm specific values that would apply to resources such as feed and ruminants.

Creator

This represents an advanced user who requires access to more detailed parameters. An example of a creator user would be a user that is defining a new ruminant breed for their simulation or other users where the task requires a detailed understanding of the ruminant growth model and equations.

Developer

This represents an advanced user who requires access to the most fundamental parameters, many of which could be considered constants to other users. This would be required for detailed model validation and exploration. Few parameters are in this category, mostly associated with Ruminant breeds and the latest animal production activities.

A single CLEM farm in a simulation may represent a number of farms in a region or village. This is especially important for tracking the movement of resources to and from a shared Market. This parameter provides the multiplier to be used for calculating the amount of resources entering and leaving this farm through the market and therefore accounting for multiple instances of the farm.

This parameter affects which values for crops and forages are selected from the Crop database. They do not need to be different climate regions, but could be different villages within a region. This index can be used in the crop and forage database to list simulation outputs for different climate-soil combinations that can then be selected for CLEM simulations.

This parameter was used in IAT simulations, and may be removed from CLEM in future.

A full description off all setting in your simulation is a valuable record of a simulation (e.g. for reporting with publications). This switch will determine if this CLEM component will provide it's full summary description in an overall simulation summary description file (HTML format).

This switch enables the use of the component name as the Transaction Category label.

This switch will enable the automatic building of the Transaction Category based on the value determines an upper limit to female breeders where the simulation will stop and report an error. This value is multiplied by the Maximum number of breeders kept to define the critical number and Simulation tree structure. This allows the user to supply the single level category label (or use the component name) and reduces duplication of entering nested level labels.

The Resources holder manages all resources available for the simulation.

The Activities holder manages all activities performed in the simulation.