Development Status

Steps to run the current integration test case:

Check out the gcbm_preprocessing "cleanup" branch
find the integration directory, all required configuration files are here
customize integration\pathRegistry.json set the "Working_Dir" variable to point at a directory of your choosing. With these scripts this should be a totally empty directory.
examine the commands in integration\runAll.bat you can run this batch file directly or run each of the commands in sequence. Please be aware of what these commands do:
- preprocessorsetup copies external spatial data from M to the working dir you specified in step 3. (This will take several minutes) and sets up your postgis credential
- regionclipper clips the spatial input to the specified subregions
- regiongridder grids the subregion's spatial data
- rollback creates the inventory and rollback disturbances. Creates the rollback tiler config
- historic runs the historic slashburn process, creates the historic tiler config
- gcbm input tools generate runnable GCBM input
- run gcbm tool runs gcbm scenarios
at the end of these processes you should have GCBM results

Command Line Tools Development Status

Region Clipper: working, but based on Arc/ArcPy so new development is likely soon
Region Gridder: working, PostGis functionality is integrated
Rollback: working, PostGis functionality is integrated
Historic Processor: working, PostGis functionality is integrated
Run tiler: working, stable
Future processor: working, requires review
GCBM Input: working
[Run GCBM](Run GCBM) working

documentation (this wiki)
de-arc Region Clipper
set up script version numbers
use Postgres Password file rather than current working dir method
review Historic Processor it may be possible to unify rollback/historic to avoid code duplication
review configs after integration of postGis work. There may be orphaned/redundant items
decouple tilerconfig from other tools if possible
build other project configs (Ontario etc.) and ensure they work