SORTIE-NDSoftware for spatially-explicit simulation of forest dynamics
Tree life history stages and transitions
Tree life history stage (also referred to as tree type), along with species, is the basic way to classify trees. When you set up behaviors for a run, you tell each behavior which trees to act on by species and type. There is support for seven tree life history stages in the model:
Tree life history stage transitioning - growth
Seed to seedling. Seeds are modeled only as aggregates, not individuals. Seeds become individual seedlings when they are processed by an establishment behavior.
Seedling to sapling. When a seedling reaches the maximum seedling height set for its species, it becomes a sapling. The diam10 value is converted to a DBH value, which is then used to calculate the rest of the sapling's new dimensions. Since height is re-calculated with a different equation and input parameters, there may be a discontinuity in height values right around the seedling/sapling transition point. If a species uses different allometric relationships for its saplings and adults, another discontinuity may occur at the time of this transition as well. For more on the allometric relationships and how they are calculated, see the Allometry topic. (The automatic updating of these allometric relationships during the growth phase can be overridden. For more, see the Growth behaviors topic.)
Sapling to adult. When a sapling's DBH reaches the minimum adult DBH for its species, it becomes an adult.
Tree life history stage transitioning - death
Death also produces tree life history stage transitions. Behaviors can request to a tree population that a tree be killed. How the tree population responds to this request depends on the type of tree, the reason for death, and the type of run.
The reasons why a tree is killed are:
There are life history stages for dead trees, but a run may not be set up to handle them. The tree population takes this into account. It examines the run to see if any behaviors directly deal with stumps and snags. If either is the case, the run is classified as "stump aware" and/or "snag aware".
Here's what happens to a tree to be killed in different situations:
Stumps exist only for the timestep in which they were created, and then disappear.
You can include information on dead trees in output files. For the purposes of output, dead trees are those which have been removed from memory and are no longer interacting with the model in any way. In this case, a snag is considered alive, although a tree that produced a snag will show up in output mortality records in the timestep in which it died to become a snag. Then the snag would show up again when it was finally removed from the model.