Name

treatment — define treatment type and response for a track selection

Synopsis

Content Model


	    <treatment> =  produce?, transition?.

	    

Attributes

NameTypeDefault
labelname of the treatment type (string) Required
minageearly operability limit (numerical)"0"
maxagelate operability limit (numerical)"10 000"
offsetnew age of stand post treatment (numerical)"0"
retainminimum length of time ineligible for another treatment"0"
adjust(A | R) Absolute or relative age adjustments "A"
renewalcurveAn expression that calculates a curve that is used to calculate the renewal age ""
manual(false | true | managed | unmanaged) A flag that indicates if the treatment is only eligible for manual scheduling. false
operabilityA query language expression that can be evaluated to give finer control over the timing of operability for this treatment. true

Description

The treatment element specifies a number of treatment options within a track. It is important to remember that treatments are not applied from the XML file, they are simply defined to provide the range of treatment options that are possible for certain forest stands. The label identifies the treatment type being applied. The minage and maxage attributes define the operability limits for the designated stand. In addition, the operability attribute can specify a query-language statement that can be evaluated to provide a finer control on the timing of operability. Offset, retain and adjust modify the response to the treatment.

Be careful when setting up your input data sets, especially if you are permitting multiple fragments within each block. In this case treatments for the largest fragment will be selected first, and then only those treatments with matching labels will be selected and applied to subsequent fragments. As the matching process proceeds, only treatments that can be sucessifully be applied to all fragments will be allowed. Furthermore, the final set of operability limits will be the least common denominator of the entire set. If the operability limits do not overlap for all fragments, then the treatment will not have an eligible timing and will be discarded.

Parents

These elements contain treatment: track.

Children

The following elements can occur in treatment: produce, transition

Attributes

label

The treatment type is specified by the label attribute. The name of the treatment should be consistent with other treatment labels to maintain continuity throughout the ForestModel.

minage

These attributes define the early operability limits. Stands belonging to the track are only eligible for this particular treatment after reaching this minimum age requirement.

maxage

These attributes define late operability limits. Stands belonging to the track are only eligible for this particular treatment before reaching the maximum age requirement.

offset

Offset defines the new age of the stand following the application of the treatment. A default value of '0' is provided however various treatments may result in a new average age of the stand. A negative number may be defined to mimic the lag time between harvest and regeneration ('-5' would indicate a 5 year period). Older ages could be used to specify advanced regeneration.

retain

The retain attribute defines the minimum length of time that the new stand is ineligible for any management treatment after receiving the current treatment. For example, after an underplanting a minimum of 20 years may be required before the regen has established and the the stand is eligible for an overstory removal.

adjust

Two values are available for this attribute: (A | R). 'A' represents an Absolute adjustment to the new age of the stand after the current treatment. This means that the new age will be the Offset value. 'R' represents a relative adjustment in age, meaning the value of the offset variable is added to the current age of the stand. This variable is available to model partial harvest treatments, such as thinnings and underplantings. The stand age can be left unchanged by using an offset of "0" and an adjust of 'R'.

renewalcurve

If specified, the renewal age is calculated by adding the offset to the current age, and then looking up the resulting curve value. If 'adjust' is 'R' then this value is added to the current age, otherwise this value becomes the renewal age.

The curve expression is evaluated in the Patchworks Query Language, for the stand condition that the treatment is being applied to. For example,

curveId('GCJ.PJ1.Prsnt.Sb')
	      

manual

Manual treatments can only be applied via an explicit method, such as loading in a schedule. The scheduler will not allocate treatments that are flagged as manual. Manual treatments can be used to allow stands to be manually scheduled for harvest at an age younger than their nominal early operability age. This is typically a requirement when loading a pre-defined schedule.

Valid parameters for this value are 'true', 'false', 'managed', and 'unmanaged'. These values are not case-sensitive. 'false' indicates that this is not a manual treatment. 'true' and 'unmanaged' both indicate that this is a manual treatment, and that the portion of the block that this treatment applies to should be considered unmanaged, so long as it is not already considered managed by virtue of other available treatments. 'managed' indicates that the portion of the block should be considered as part of the managed forest.

The implication of the above is as follows. If the treatments that match a portion of a block area all have values equal to 'true' or 'unmanaged', then that portion of the block will be considered to be part of the unmanaged land base. If any treatment that match a portion of the block has a value of 'false' or 'managed', then that portion of the block is considered to be in the managed land base, regardless if any single matching treatment has a contrary value.

For the above mentioned tests, all other rules of treatment eligibility matching simultaneouslly apply, such as age restrictions and operability criteria. For example, if a treatment does not match on the operability criteria, then the value of the manual attribute does not matter.

operability

Operability criteria can be refined using a query-language expression. This expression can refer to and of the attributes associated with the stand. For example, an operability statement could limit the treatment to stands with greater than 140 m3/ha of volume. Any query-language expression is allowed, so long as it evaluates to a true or false condition. When the matrix builder is operating, it will evaluate this expression for each year that it is considering the stand for harvest.

The minage, maxage, retain and offset are numeric values, and can be specified as numbers or as a Patchworks Query Language expression. The expression may make use of numbers, operators, defined values and functions. The expressions will be evaluated in the context of the stand condition that the treatment rule is being applied to.

See Also

track,produce, assign, transition.

Examples

  <select statement="FU eq 'BW1' and IFM in ifm and SILVINT eq 'Exten'">
    <track>
      <treatment label="Intn1" minage="70">
        <produce>
          <assign field="treatment" value="'Intn1'" />
        </produce>
       </treatment>
    </track>
  </select>

  <select statement="FU eq 'BW1' and IFM in ifm and SILVINT eq 'Prsnt'">
    <track>
      <treatment label="Intn1" minage="60">
        <produce>
          <assign field="treatment" value="'Intn1'" />
        </produce>
       </treatment>
    </track>
  </select>
	  

In the above example an 'Intn1' treatment is being applied to two unique tracks. Both tracks are eligible for the Intn1 treatment type, however the treatment specifications are slightly modified to accommodate the differences in the stands they represent. For example, the first track can only receive this treatment when the stand type has reached an age of 70, whereas the second stand type can receive the same treatment 10 years earlier at age 60.

  <select statement="FU eq 'BY1' and IFM in managed and SILVINT in InitialShelterwood">
    <track>
      <treatment label="SCut" minage="70" maxage="150" adjust="R" retain="15">
        <produce>
          <assign field="treatment" value="'SCut'" />
        </produce>
      </treatment>
    </track>
  </select>
	    

In the second example, a track is eligible for a partial treatment 'SCut' within a specified operability range (70 to 150 years of age). In this example however we can see that a relative adjustment of age is applied after the current treatment (the offset is added to the current age of the stand). Since no offset has been defined the default value is '0' is used, so the age of the stand has not change as a result of this treatment application. The retain attribute specifies that a stand which has received this particular treatment is not eligible for another treatment for at least 15 years.

In the following example an operability expression is used to restrict the treatment to stands that have Swd volume in the range of 60 to 140 m3/ha.

<select statement="theme3 = 'JP'">
  <track>
    <treatment label="special" 
      operability="lookupCurve(attribute('feature.Yield.managed.Swd'),offset()) gt 60 
        and lookupCurve(attribute('feature.Yield.managed.Swd'),offset()) le 140">
      <produce>
        <assign field="treatment" value="'special'" />
      </produce>
      <transition>
        <assign field="theme3" value="'newStrata'" />
      </transition>
    </treatment>
  </track>
</select>