Extrapolation and Calibration Modes
dmvdostem has two primary "modes":
- Extrapolation Mode
- Calibration Mode
MORE INFO....
The calibration interface to dvmdostem provides a way to dynamically view the
progress of a dvmdostem simulation in the eq run stage as well as pause
the simulation and modify certain run-time variables before resuming the
simulation.
The calibration interface relies on two primary components:
- Control of the simulation is handled on the "C++ side".
- Visualization of the simulation is handled on the "Python side".
The linkage between these two components is done
with json files that are stored in your /tmp/ directory. Provided in the
project's' calibration/ directory are a set of scripts for visualizing the
progress of the simulation. The progress of the simulation is being recorded in
the json files in your /tmp/ directory.
Why write files to
/tmp/and not some location within the project directory? The volume of files produced is not insignificant. Writing to/tmp/means that the operating system will eventually clean up the files if we forget to delete them.
The arrangement is depicted in the image below.
Right now our calibration viewer consists of the ExpandingWindow.py python
script in the calibration/ directory. "Expanding Window" refers to the fact
that the x-axis of the plot will adjust its range to accommodate the .json
files present in /tmp/. There is much more info about the script available
with the --help flag:
$ ./calibration/ExpandingWindow.py
usage: ExpandingWindow.py [-h] [--pft {0,1,2,3,4,5,6,7,8,9}]
[--suite {Environment,Soil,VegSoil,Vegetation}]
[--list-suites]
[--tar-cmtname {heath tundra,shrub tundra,tussock tundra,BLANK,wet sedge tundra,deciduous forest,black spruce forest,maritime forest,white spruce forest} | --tar-cmtnum {7,4,5,0,6,3,1,8,2}]
[--list-caltargets] [-l LOGLEVEL]