make rout=rvic with a default value of rout=stub. That we will want to set here: https://github.com/UW-Hydro/VIC/blob/master/ci/image.travis#L64, try setting a environment variable like extension_options=“rout=stub” (or something like that) in one of the image driver build (https://github.com/UW-Hydro/VIC/blob/master/.travis.yml#L12). We could also create a new build for the image driver with extensions but this is fine for now.
One last thing. What if invoking the RVIC extension was a two step process. First, you have to build it e.g make rout=rvic, then you have to specify a parameter file. Your code would then check if it should run RVIC (both would have to be true).
For example, you might have a block of code that looks like this:
// read global parameters
vic_image_start();
vic_image_start();
if (options.rout) {
// read global parameters for routing
rout_start(); // Routing routine (extension)
}vic_image_start(); in the code?
I am working with VIC 4.0 version and using it for flood forecasting in North West Himalaya in India. The VIC model is showing the error:
- Maximum Energy Error
- Maximum Moist Error
- Error in vegetation file, grid cell 228 not found
I have read the source code, read_vegparam.c . I checked for the 228 grid cell in my grid file and also in vegetation parameter file. It is present in both the files.
The code is showing that if 'vegcel' is not equal to 'gridcel', then this kind of error will come. I did not understand which two files I have to compare to check this vegcel and gridcel mentioned in the source code.
I run the model (VIC 4.2.d). The result is much more than the observation data.
I lowered Dsmax and Ds, and increased the depth of the soil layers, but the correlation coefficient decreases!
Can anyone help me?
Where can the problem be?
The total daily flow rate during the simulation period is 570, but the 7200 model simulates it.
@singhharsh12
There used to be some documentation on calibration at the old UW documentation website, but it appears to be down right now. The general procedure is to run the VIC model, route the runoff to the location of a discharge gauge, and compare the predicted discharge to the measured discharge. There are several parameters in the soil parameter file that you can adjust (Ds, Dsmax, etc.) to try to get a better match between your predictions and the measurements. You can find a description of all the parameters in the soil parameter file here: https://vic.readthedocs.io/en/master/Documentation/Definitions/#depth
Here is one example of a VIC calibration project: https://wwa.colorado.edu/climate/Wood_UTDWR_Report_2015.pdf
File conversions question:
Does anyone know of a tool for converting ASCII input files for VIC 4.2 to the NetCDF format needed for VIC 5's image driver? I have tried tonic (https://github.com/UW-Hydro/tonic), but it seems to still be in development. Specifically, I would like to convert the meteorological forcing files.