Skip to content

Changelog for new versions

Arash edited this page Jun 11, 2020 · 6 revisions

When releasing a new version of VisionEval, we will:

  1. Include the significant changes in the release notes template below
  2. Record the significant changes in the changelog here

Release Notes Template

For releases Make updates where marked with **

If there are changes to inputs that users need to know, make a note of that. Make a note of which models a given new or updated module has been tested with.

Packaged versions of the VisionEval framework are provided as .zip files. Each has an installation .bat file for Windows to automatically prepare the R environment.

These installers are packaged for R versions from **3.5.1 to 3.6.1**.

This release includes the following changes:
**
- Change 1
- Change 2
- Change 3
**

Instructions for Installing
Install one of the supported R versions using its default options (R **3.5.1 to 3.6.1**). Make sure to leave the box checked that offers to add R to the Windows registry.
Download the corresponding installer .zip file
Unzip the downloaded installer into an empty folder of your choice
Double-click “VisionEval.bat” (this is the standard entry point – use it every time to start VisionEval)
a. If VisionEval has not run before, the batch file and associated script will set up a few pointers and the convenience functions (see below)
b. Otherwise, it will move straight to step 5.a below
A command window will briefly appear followed by one of these:
a. RGUI with the “Welcome to VisionEval!” message (you’re good to go)
b. Your default browser pointing at the R download page (if you forgot to do step 1 or if you picked the wrong version) – just redo step 1 or steps 2/3 to get them consistent
The previous instructions for launching VEGUI, VERPAT, etc. remain the same.
a. vegui() starts VEGUI
b. verpat() runs VERPAT in RGUI
c. verspm() runs VERSPM in RGUI
d. Note that there’s no helper function to run VESTATE from the command line yet – that will be added to the installation in a future release. You can just setwd() to the VE-State folder under “models” and then source(‘Run_Model.R’).

Changelog

Version Changes
0.1 Initial release
0.1.1 Numerous updates to VELandUse and other modules
1.0 Added ve.export
Fixed bugs in unit conversions
Fixed issue with Azone file order dependence
1.0.1
Clone this wiki locally