-
Notifications
You must be signed in to change notification settings - Fork 11
TREES Process
perrygeo edited this page Feb 27, 2012
·
1 revision
The previous semi-automated-but-mostly-manual process for running timber land scenarios was called the TREES process
Here's a brief technical outline...
Trees process Developed by Mike Mertens, et. al. in 2009? Docs by Matthew Perry Overview
The TREES process takes standard forestry inventory information, runs several scenarios in a growth and yield model and schedules harvesting activity to optimize for a maximum steady flow of merchantable timber at the property level.
Current Process Outline
- Data in tabular FPS-like format (initially txt files but will eventually come from postgres)
- Stand attributes table
- Tree inventory
- Data translated to FVS input files using StandProcessor.py
- single .slf file for stands attributes
- one .fvs file per stand with tree inventory
- FVS Key files developed for each prescription scenario.
- assumption: They all use a XX_YY.key format where XX is the perscription and YY is the offset. Base keys, therefore must be named XX_01.key
- assumption: Must have a COMPUTE … Offset = 0 … END section and use that Offset variable in the equations
- Careful about hardcoded include files .. look for G:* after Open keywords.. convert to relative paths with unix file seperators
- Create offsets using "analysis\scheduling\create_offsets.pl"
- reads in base Rxs
- outputs directory (“offsets”) with multiple key files offset, as well as .bat files to run them
- must manually add a “Grow-only” key as the final step (?)
- Run all the .bat files in the offsets dir using analysis\scheduling\offsets\proc_gy.php
- Run the gy_*_extract.pl scripts
- parses FVS outputs into csvs for use in the scheduler
- data must be moved manually from the offsets directory to *_treelists (?)
- outputs several *.txt files to *_treelists directory
- must be run separately for both “alt” and “bus” (and other?) Rxs
- .txt files moved to ./data
- Run the adjacency AML at "analysis\scheduling\stand_delin\sch_inputs.aml"
- outputs adj.txt file which defined adjacency
- Run the scheduler executable
- reads *.txt from the ./data directory
- outputs *_sch.txt and *_summary.txt
- Join _sch with shapefile
- Copy ? into carbon calc spreadsheet and do (?)
Required scripts
StandProcessor.py
create_offsets.pl
proc_gy.php
gy_age_extract.pl
gy_carbon_extract.pl
gy_carbon_extract_agl.pl
gy_cut_extract.pl
gy_cut_extract_cubic.pl
gy_cut_extract_lutwork.pl
gy_live_extract.pl
schedule.c
sch_inputs.aml