{"_id":"57621497c058720e00662947","version":{"_id":"574a3bc0d1d1381900b73fae","project":"574a3bc0d1d1381900b73fab","__v":7,"createdAt":"2016-05-29T00:45:52.939Z","releaseDate":"2016-05-29T00:45:52.939Z","categories":["574a3bc0d1d1381900b73faf","574be6d52aa7221700c51bed","574c0b6d281b010e00008f89","574c1afbcf99610e00ef7d2b","574d13b9a1f0be2000ae3803","574d14140db0870e0075382d","591eb3a72c1b1f0f000fa9f2"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3517.0.0","version":"3517"},"__v":15,"githubsync":"","parentDoc":null,"project":"574a3bc0d1d1381900b73fab","category":{"_id":"574c1afbcf99610e00ef7d2b","__v":0,"project":"574a3bc0d1d1381900b73fab","version":"574a3bc0d1d1381900b73fae","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-30T10:50:35.767Z","from_sync":false,"order":9999,"slug":"documentation-1","title":"1. Forest Description"},"user":"574bfb9290d8b32000864973","metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-06-16T02:53:11.994Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"The forest management information within the standard forest description describes all the possible forest management alternatives across the model's planning horizon.\n\nThere are three optional forest management worksheets in the standard forest description workbook.  The first (worksheet 'Silviculture') defines all possible management alternatives for the current rotation.  The second (worksheet 'Replanting') defines all possible replanting options and constraints for the forest estate as it is clearfelled at maturity.\n\nThe third (worksheet 'Management') is similar to the worksheet 'Silviculture' but it has been developed to simplify the process of providing the same sort of functionality that can be developed using the worksheet 'Silviculture'.  It provides a simple way to list alternative core-data classes for existing plunits while avoiding having to create a set of completely new plunits on the worksheet 'Plunit' that do not contain any area.\n\nThe forest management information is held on the following worksheets:\n\n1. [Worksheet 'Silviculture'](doc:forest-management#worksheet-silviculture)\n\n2. [Worksheet 'Replanting'](doc:forest-management#worksheet-replanting)\n\n3. [Worksheet 'Management'](doc:forest-management#worksheet-management)\n\n<br />\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Worksheet 'Silviculture'\"\n}\n[/block]\nOutlines all the possible management alternatives that can be considered by the optimization model for the estate that is defined at the beginning of the forest estate model. The alternatives are only valid for the **current rotation areas and ages classes ** only (i.e. the 'current rotation'), which exist as planning units at the outset of the forest estate model (beginning of modelling period 1).\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Optional Worksheet\",\n  \"body\": \"The worksheet 'Silviculture' is an optional worksheet in the forest description workbook.\"\n}\n[/block]\n.\n<br />\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Worksheet 'Replanting'\"\n}\n[/block]\nOutlines all the possible replanting alternatives that can be considered by the optimization model when planning units are clearfelled throughout the models planning horizon.  These alternatives represent the regenerated options for **subsequent rotations of the forest estate** (i.e. 'future rotations'). Replanting constraints can be applied and the time between clearfell and reestablishment can be defined.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"The worksheet 'Replanting' is an optional worksheet in the forest description workbook.\",\n  \"title\": \"Optional Worksheet\"\n}\n[/block]\n.\n<br />\n[block:api-header]\n{\n  \"title\": \"Worksheet 'Management'\"\n}\n[/block]\nThe 'Management' worksheet has been designed to be a replacement for the 'Silviculture' worksheet.  The 'Silviculture' worksheet and the 'Management' worksheet can both be present in the same forest description and will function side-by-side because the 'Silviculture' worksheet does offer some additional functionality that the 'Management' worksheet currently cannot.\n\nThe 'Management' worksheet has primarily been designed to greatly simplify the definition of multiple production thinning regimes and associated alternative clearfell yield table options for current rotation planning units defined on the 'Plunit' worksheet.\n\nThe 'Management' worksheet removes the requirement to pre-define multiple planning units that do not have an area or year of establishment on the 'Plunit' worksheet.  When using the 'Management' worksheet the destination planning units that will receive area transferred from other planning units are automatically created during the optimization of the forest description.\n\nLike the 'Silviculture' worksheet, the 'Management' worksheet outlines possible management alternatives that can be considered by the optimization model for the estate that is defined at the beginning of the forest estate model. The alternatives are only valid for the **current rotation areas and ages classes** only (i.e. the 'current rotation'), which exist as planning units at the outset of the forest estate model (beginning of modelling period 1).\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Optional Worksheet & Parallel Processing Import\",\n  \"body\": \"The worksheet 'Management' is an optional worksheet in the forest description workbook; and it can only be used if a forest description is imported using the 'Parallel Processing' import routines.\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"A software build number of 3517.10063.6425.* and above is required to correctly use the latest version of the 'Management' worksheet.  The final release version of the 'Management' worksheet allows the planning unit 'Species' to be changed.  This is required when creating models that are based on optimum land use and land management.  Pre-release versions of the 'Management' worksheet did not allow this functionality.\",\n  \"title\": \"The Management Worksheet Requires Software Build 3517.10063.6425.*\"\n}\n[/block]\nAt it's simplest, the Management worksheet presents alternative core-data classes for a plunit.  Where as the 'Silviculture' worksheet explicitly requires alternative plunits to be created on the 'Plunit' worksheet and then area transferred between plunits, the Management worksheet takes away the need to create alternative plunits and rules for transfer.  The Management worksheet simply allows an alternative Croptype or Regime core-data class (for example) to be nominated as an alternative option for any plunit.  The optimization model will then consider each alternative managment option for the plunit.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/d2c6d8c-worksheet-management.jpg\",\n        \"worksheet-management.jpg\",\n        1320,\n        498,\n        \"#1c1a53\"\n      ],\n      \"sizing\": \"full\",\n      \"caption\": \"\"\n    }\n  ]\n}\n[/block]\n<br />\n\n##How to Use the 'Management' Worksheet\n\n\nIn the example below, the Group/Attribute in the red box is Plunit/Stand 001.  Each row on the Management worksheet represents an alternative combination of the two core-data classes of Regime and Croptype that can exist for Plunit/Stand 001.  If a core-data class is blank (i.e. no new data) then whatever entry exists for the original planning unit on the 'Plunit' worksheet prevails.\n\nImportantly, whereas when using the 'Silviculture' worksheet the user is required to explicitly create the plunit alternatives that area can be transferred into, when using the 'Management' worksheet the software does not require the user to pre-define these planning unit alternatives.  The software will automatically create the alternative plunits for the user as part of the optimization process.\n\nIn the example below then there will be **four (4) **alternatives in the optimization model for Plunit/Stand 001.  The user only creates the original planning unit with an area and year of establishment on the 'Plunit' worksheet (Option 1 below).  All the other alternative planning units needed for Options 2, 3 & 4 are created automatically and do not need to be shown on the 'Plunit' worksheet as would have been necessary had the 'Silviculture' worksheet been used.  All the planning unit data are the same for all options apart from the core-data classes changed via the 'Management' worksheet definitions.  The options that the example below produces are:\n\n1. All 'Stand 001' core-data classes and Group/Attributes as the user created on worksheet 'Plunit'\n2. All 'Stand 001' data plus alternative Regime/Lower Altitudes - T1 & Croptype/YTGEN 100\n3. All 'Stand 001' data plus alternative Regime/Lower Altitudes - T2 & Croptype/YTGEN 200\n4. All 'Stand 001' data plus alternative Regime/Lower Altitudes - T3 & Croptype/YTGEN 400\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/9781179-worksheet-management-2.jpg\",\n        \"worksheet-management-2.jpg\",\n        1314,\n        327,\n        \"#111027\"\n      ]\n    }\n  ]\n}\n[/block]\nThe use of regular expressions is allowed on the 'Management' worksheet.  This gives a powerful syntax for quickly assigning many possible alternatives of management to the current rotation planning units.  The example below illustrates two key properties of wild card use on the 'Management' worksheet.  These are:\n\n1.  Firstly, in the example below the use of the regular expression  **{ = 'Croptype' } ** in the core-data class 'Regime' tells the system to replace the attribute of the core-data class 'Regime' with whatever attribute is allocated to the planning unit for the core-data class 'Croptype'.\n\n2.  Secondly, in the example below the use of the regular expression  **{ LIKE '%Stand 002%' } **creates a filter of any and all 'Croptype' data-classes that contain the string 'Stand 002'.\n\nThe effect of the example below were there 50 core-data classes on the 'Croptype' worksheet that contained the string 'Stand 002' somewhere in their name, would be 50 additional management options for the Plunit/Stand 002 within the optimization of the forest description.  With a single row as below, then 50 additional management options for a single plunit have been created without the user needing to create all 50 additional planning units on the 'Plunit' worksheet.  The number of planning unit alternatives is essentially being defined by the number of yield table alternatives being presented to the model on the 'Croptype' worksheet (in this example).\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/cd0ffd3-worksheet-management-3.jpg\",\n        \"worksheet-management-3.jpg\",\n        1324,\n        322,\n        \"#111029\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"forest-management","type":"basic","title":"Forest Management"}
The forest management information within the standard forest description describes all the possible forest management alternatives across the model's planning horizon. There are three optional forest management worksheets in the standard forest description workbook. The first (worksheet 'Silviculture') defines all possible management alternatives for the current rotation. The second (worksheet 'Replanting') defines all possible replanting options and constraints for the forest estate as it is clearfelled at maturity. The third (worksheet 'Management') is similar to the worksheet 'Silviculture' but it has been developed to simplify the process of providing the same sort of functionality that can be developed using the worksheet 'Silviculture'. It provides a simple way to list alternative core-data classes for existing plunits while avoiding having to create a set of completely new plunits on the worksheet 'Plunit' that do not contain any area. The forest management information is held on the following worksheets: 1. [Worksheet 'Silviculture'](doc:forest-management#worksheet-silviculture) 2. [Worksheet 'Replanting'](doc:forest-management#worksheet-replanting) 3. [Worksheet 'Management'](doc:forest-management#worksheet-management) <br /> [block:api-header] { "type": "basic", "title": "Worksheet 'Silviculture'" } [/block] Outlines all the possible management alternatives that can be considered by the optimization model for the estate that is defined at the beginning of the forest estate model. The alternatives are only valid for the **current rotation areas and ages classes ** only (i.e. the 'current rotation'), which exist as planning units at the outset of the forest estate model (beginning of modelling period 1). [block:callout] { "type": "info", "title": "Optional Worksheet", "body": "The worksheet 'Silviculture' is an optional worksheet in the forest description workbook." } [/block] . <br /> [block:api-header] { "type": "basic", "title": "Worksheet 'Replanting'" } [/block] Outlines all the possible replanting alternatives that can be considered by the optimization model when planning units are clearfelled throughout the models planning horizon. These alternatives represent the regenerated options for **subsequent rotations of the forest estate** (i.e. 'future rotations'). Replanting constraints can be applied and the time between clearfell and reestablishment can be defined. [block:callout] { "type": "info", "body": "The worksheet 'Replanting' is an optional worksheet in the forest description workbook.", "title": "Optional Worksheet" } [/block] . <br /> [block:api-header] { "title": "Worksheet 'Management'" } [/block] The 'Management' worksheet has been designed to be a replacement for the 'Silviculture' worksheet. The 'Silviculture' worksheet and the 'Management' worksheet can both be present in the same forest description and will function side-by-side because the 'Silviculture' worksheet does offer some additional functionality that the 'Management' worksheet currently cannot. The 'Management' worksheet has primarily been designed to greatly simplify the definition of multiple production thinning regimes and associated alternative clearfell yield table options for current rotation planning units defined on the 'Plunit' worksheet. The 'Management' worksheet removes the requirement to pre-define multiple planning units that do not have an area or year of establishment on the 'Plunit' worksheet. When using the 'Management' worksheet the destination planning units that will receive area transferred from other planning units are automatically created during the optimization of the forest description. Like the 'Silviculture' worksheet, the 'Management' worksheet outlines possible management alternatives that can be considered by the optimization model for the estate that is defined at the beginning of the forest estate model. The alternatives are only valid for the **current rotation areas and ages classes** only (i.e. the 'current rotation'), which exist as planning units at the outset of the forest estate model (beginning of modelling period 1). [block:callout] { "type": "info", "title": "Optional Worksheet & Parallel Processing Import", "body": "The worksheet 'Management' is an optional worksheet in the forest description workbook; and it can only be used if a forest description is imported using the 'Parallel Processing' import routines." } [/block] [block:callout] { "type": "warning", "body": "A software build number of 3517.10063.6425.* and above is required to correctly use the latest version of the 'Management' worksheet. The final release version of the 'Management' worksheet allows the planning unit 'Species' to be changed. This is required when creating models that are based on optimum land use and land management. Pre-release versions of the 'Management' worksheet did not allow this functionality.", "title": "The Management Worksheet Requires Software Build 3517.10063.6425.*" } [/block] At it's simplest, the Management worksheet presents alternative core-data classes for a plunit. Where as the 'Silviculture' worksheet explicitly requires alternative plunits to be created on the 'Plunit' worksheet and then area transferred between plunits, the Management worksheet takes away the need to create alternative plunits and rules for transfer. The Management worksheet simply allows an alternative Croptype or Regime core-data class (for example) to be nominated as an alternative option for any plunit. The optimization model will then consider each alternative managment option for the plunit. [block:image] { "images": [ { "image": [ "https://files.readme.io/d2c6d8c-worksheet-management.jpg", "worksheet-management.jpg", 1320, 498, "#1c1a53" ], "sizing": "full", "caption": "" } ] } [/block] <br /> ##How to Use the 'Management' Worksheet In the example below, the Group/Attribute in the red box is Plunit/Stand 001. Each row on the Management worksheet represents an alternative combination of the two core-data classes of Regime and Croptype that can exist for Plunit/Stand 001. If a core-data class is blank (i.e. no new data) then whatever entry exists for the original planning unit on the 'Plunit' worksheet prevails. Importantly, whereas when using the 'Silviculture' worksheet the user is required to explicitly create the plunit alternatives that area can be transferred into, when using the 'Management' worksheet the software does not require the user to pre-define these planning unit alternatives. The software will automatically create the alternative plunits for the user as part of the optimization process. In the example below then there will be **four (4) **alternatives in the optimization model for Plunit/Stand 001. The user only creates the original planning unit with an area and year of establishment on the 'Plunit' worksheet (Option 1 below). All the other alternative planning units needed for Options 2, 3 & 4 are created automatically and do not need to be shown on the 'Plunit' worksheet as would have been necessary had the 'Silviculture' worksheet been used. All the planning unit data are the same for all options apart from the core-data classes changed via the 'Management' worksheet definitions. The options that the example below produces are: 1. All 'Stand 001' core-data classes and Group/Attributes as the user created on worksheet 'Plunit' 2. All 'Stand 001' data plus alternative Regime/Lower Altitudes - T1 & Croptype/YTGEN 100 3. All 'Stand 001' data plus alternative Regime/Lower Altitudes - T2 & Croptype/YTGEN 200 4. All 'Stand 001' data plus alternative Regime/Lower Altitudes - T3 & Croptype/YTGEN 400 [block:image] { "images": [ { "image": [ "https://files.readme.io/9781179-worksheet-management-2.jpg", "worksheet-management-2.jpg", 1314, 327, "#111027" ] } ] } [/block] The use of regular expressions is allowed on the 'Management' worksheet. This gives a powerful syntax for quickly assigning many possible alternatives of management to the current rotation planning units. The example below illustrates two key properties of wild card use on the 'Management' worksheet. These are: 1. Firstly, in the example below the use of the regular expression **{ = 'Croptype' } ** in the core-data class 'Regime' tells the system to replace the attribute of the core-data class 'Regime' with whatever attribute is allocated to the planning unit for the core-data class 'Croptype'. 2. Secondly, in the example below the use of the regular expression **{ LIKE '%Stand 002%' } **creates a filter of any and all 'Croptype' data-classes that contain the string 'Stand 002'. The effect of the example below were there 50 core-data classes on the 'Croptype' worksheet that contained the string 'Stand 002' somewhere in their name, would be 50 additional management options for the Plunit/Stand 002 within the optimization of the forest description. With a single row as below, then 50 additional management options for a single plunit have been created without the user needing to create all 50 additional planning units on the 'Plunit' worksheet. The number of planning unit alternatives is essentially being defined by the number of yield table alternatives being presented to the model on the 'Croptype' worksheet (in this example). [block:image] { "images": [ { "image": [ "https://files.readme.io/cd0ffd3-worksheet-management-3.jpg", "worksheet-management-3.jpg", 1324, 322, "#111029" ] } ] } [/block]