-
Notifications
You must be signed in to change notification settings - Fork 2
Development Status
Scott Morken edited this page Apr 16, 2018
·
5 revisions
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
- recliner2GCBM, GCBM config tools generate runnable GCBM input
- at the end of these processes you should have 1 or more runnable GCBM projects
- 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
- recliner2GCBM working, command line interface will likely change soon
- GCBM Config working, command line interface will likely change soon
- documentation (this wiki)
- de-arc Region Clipper
- amalgamate GCBM config/recliner2GCBM and possibly other GCBM related input preparation scripts into a single command line tool
- set up script version numbers
- use Postgres Password file rather than current working dir method
- integrate with mitigation tools (master batch)
- 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 the rest of the BC configs
- build other project configs (Ontario etc.) and ensure they work