Crop task activity

CLEM.Activities.CropActivityTask

A task associated with growing a crop.

There are usually a number of tasks required in order to successfully produce crop products each with labour and/or financial requirements. Any number of these Crop task activities can be added below a Manage crop product activity. This activity component is only needed to manage finances and labour associated with the crop and may restrict crop outputs if resource shortfalls occur.

The following parameters are used to define this activity

A category label for this task for grouping transactions (see Resource ledger report for more details).

As some activities are generic and can apply to a range of tasks or costs, these Activities provide a Category property to identify the action in any transaction ledger. For example, there may be multiple crop tasks and costs associated with growing a crop and each of these should provide a Category to describe them such as "Fertilise" could be associated with all tasks and costs relating to applying fertiliser.

This parameter will determine what action is taken if there are insufficient resources to perform this activity.

You can report an error and stop the simulation, skip this activity or use the resources available. See What to do when resources are limiting

The following components will add additional functionality to this activity.

This activity provides the following units for components: fixed, per packet and amount

Any Activity fee will include financial costs based on any specified identifiers and units and may limit the outcomes if supported and OnPartialResourcesAvailableAction set to UseAvailableWithImplications

Any Labour requirement will include labour allocation to perform this activity based on any specified identifiers and units and may limit the outcomes if supported and OnPartialResourcesAvailableAction set to UseAvailableWithImplications

Crop tasks will be performed each time step unless a Timer is provided. The Crop harvest timer is provided for this situation as events can be tied to the next harvest date for the product being managed.

This activity is managed by it's parent activity (the activity holding it as a child in the simulation tree).

 

See also