Project Meeting 2018.12.06

VEGUI

Work complete, currently working on reconciling revisions with VEState revisions, see PR#222
Will update tutorial, test, and pull through to master in the immediate future

Pie charts replaced with bar charts, see #203
Finalizing VERSPM integration
- Expected to complete the VERSPM side of it by next Wednesday
- Will likely need to make a few updates to the visualizer as a result
Will merge to develop after we get VEGUI integrated released, see PR#223

See Brian's notes
- A standardized approach to module documentation has been developed
- Changing DevType to LocType throughout VE-RSPM code
- Created a VESimLandUseData Package
- Estimating the models for synthesizing Bzones
- Created an Initialize module
- CreateSimBzones module created
- A new module test setup has been developed
VEState merged into develop branch: VEState required some changes to modules that are shared with VERSPM. Hassle to handle in separate branches. Only reason to separate was difficulty in managing testing VERSPM and VESTATE in same branch. Solved this as follows:
New test setup developed. Rather than have test data (defs, inputs, datastore) reside in tests directory, it is in modules/Test_Data in a subdirectory for the model (e.g. VE-RSPM, VE-State). When test script is run, these datasets are copied into the tests directory and tests are run. Each model has its own test script. Some new functions to assist. Test logs and model state file are stored in a directory with the model name in tests. See the VESimHouseholds/tests for example.

See Jeremy's add-on issue to construct a standalone VisionEval installer that can work on all platforms where you can install R 3.5.1.
Installer here
Allow model and inputs+defs to reside in different directories. PR#215
Let's discuss, and also discuss using Docker with Travis and GitHub releases for deployment as well
The old RPAT had an INNO Setup installer script, see RPAT