Model output
(→Numerical output) |
|||
| Line 51: | Line 51: | ||
[[file:Jamsmap2D.png|700x700px|Four different runoff component]] | [[file:Jamsmap2D.png|700x700px|Four different runoff component]] | ||
| − | The values are provided in daily average. Users can zoom in and out the map. | + | The values are provided in daily average. Users can zoom in and out the map. Similarly, the values can be downloaded by clicking the save button (the red box in right hand side). The GIS shape file with HRU ID and values associated with each HRUs are saved. |
| Line 60: | Line 60: | ||
===Numerical output=== | ===Numerical output=== | ||
| − | The outputs of different variables produced by the model are provided in the output folder (current-->> Timeloop.dat filename) after each model run. These variables which need to be produced as output data is | + | The outputs of different variables produced by the model are provided in the output folder (current-->> Timeloop.dat filename) after each model run. These variables which need to be produced as output data is determined inside the TimeLoop.xml file which is placed outside the current folder. These variables of the timeloop can be changed directly from the JAMS builder before running the model as shown in Figure below. After uploading the model xml file, users need to click on the button 'configure model output' (as shown in red box in the figure). This will bring a new window 'Datastore editor' from where users can include or exclude the output variables. |
[[file:Jams_timeloop.png|1000x1000px| Timeloop file]] | [[file:Jams_timeloop.png|1000x1000px| Timeloop file]] | ||
| − | Similarly, the HRULoop.xml is responsible for producing the daily average values of each variables of interest (as defined inside the xml file) for all HRUs. Users can exclude or include the variables as | + | Similarly, the HRULoop.xml is responsible for producing the daily average values of each variables of interest (as defined inside the xml file) for all HRUs. Users can exclude or include the variables as described in previous paragraph for |
| − | Please note that the HRULoop produces a file which is large in size (due to the information associated all HRUs at each time step). Therefore, it is advised not to produce HRULoop.dat | + | Please note that the HRULoop produces a file which is large in size (due to the information associated all HRUs at each time step). Therefore, it is advised not to produce HRULoop.dat every time when the model is run. Disabling the HRULoop.xml will not produce HRULoop.dat file. |
===Efficiency measurement=== | ===Efficiency measurement=== | ||
| − | The model produces different efficiency results at the end of each model run. The results are published at the bottom of ' | + | The model produces different efficiency results at the end of each model run. The results are published at the bottom of 'ExecutionInfo' of the JAMS launcher. The model is able to break the time period (such as calibration and validation) into different periods as defined by users. |
[[file:Efficiency.png|700x700px| JAMS efficiency]] | [[file:Efficiency.png|700x700px| JAMS efficiency]] | ||
Revision as of 09:07, 17 October 2012
The model results and efficiency are provided in three different ways:
- Graphical display
- Numerical output
- Efficiency measurement
Graphical display
The model provides the graphical display output for many variables. As an example, the output of simulated runoff plot is provided below:
- An example of runoff Plot
The 'TSVisualization' component of the JAMS builder brings graphical display of different output variables. The 'TSVisualization' component can be expanded (click + and - sign on the left side to expand and reduce) as shown in Figure below. The existing TS plots will be shown. The new plot can be created by using the existing plot. Drag one of the existing plots (example, Glacier contribution) and hold CTRL key (a + sign will appear) and leave both the keys. The new plot will appear with the new name (Glacier contribution_1). From the right window, the name and the values of the new plot can be changed. Mainly, four things has to be changed for the new plot.
1. Change the name of the component. Click the [...] box on the right hand side of the 'Name'. This will bring a new window and you can change the name of the new plot.
2. Provide new names for the legend used in the plot. Click on the 'titleLeft' row and change the name of the legends under 'Value' window. In case of more than one legend, separate the name by semicolon.
3. Provide colors to the legends. Click 'colorLeft' row and change the color name under 'Value' window.
4. Provide value for the legends. When 'valueLeft' row is clicked, the window below is activated. The value can be choosen from Timeloop. Use CTRL key to choose more than one value.
Alternatively, this information can be changed by editing the model xml file which has been explained below.
With these lines in xml file as shown in figure below, users can define which output files they wish to see as a plot/graph. In the figure below, four different runoff components is displayed.
After defining the plot, users also need to define a line in a 'Plot & Maps' component of the xml to bring it in the JAMS framework. This has to be done by directly editing the model xml. For example: The last line is dedicated to display the Runoff component plot.
The Runoff component Plot will appear in 'Plots & Maps' group in the JAMS launcher after loading the xml file in JAMS, which users can switch on/off to display as a graph. The spatial distribution of some variables can also be displayed as a map, for which the different component of 'Maps' (as shown in rectangular red window) has to be activated as shown in Figure below. In this example, the average evapotranspiration of the model run period is activated.
After running the model, users can see the plot of different variables as provided below:
- Runoff component components
- Spatial distribution of evapotranspiration
The values are provided in daily average. Users can zoom in and out the map. Similarly, the values can be downloaded by clicking the save button (the red box in right hand side). The GIS shape file with HRU ID and values associated with each HRUs are saved.
To display the spatial distribution of evapotranspiration in 3D map, users have to click the 'Map 3D'.
Numerical output
The outputs of different variables produced by the model are provided in the output folder (current-->> Timeloop.dat filename) after each model run. These variables which need to be produced as output data is determined inside the TimeLoop.xml file which is placed outside the current folder. These variables of the timeloop can be changed directly from the JAMS builder before running the model as shown in Figure below. After uploading the model xml file, users need to click on the button 'configure model output' (as shown in red box in the figure). This will bring a new window 'Datastore editor' from where users can include or exclude the output variables.
Similarly, the HRULoop.xml is responsible for producing the daily average values of each variables of interest (as defined inside the xml file) for all HRUs. Users can exclude or include the variables as described in previous paragraph for
Please note that the HRULoop produces a file which is large in size (due to the information associated all HRUs at each time step). Therefore, it is advised not to produce HRULoop.dat every time when the model is run. Disabling the HRULoop.xml will not produce HRULoop.dat file.
Efficiency measurement
The model produces different efficiency results at the end of each model run. The results are published at the bottom of 'ExecutionInfo' of the JAMS launcher. The model is able to break the time period (such as calibration and validation) into different periods as defined by users.
The details of the objective functions are provided below:
To understand more about the objectives function and their pros and cons in terms of simulating different parts of hydrological dynamics, the article (Krause, 2005) might be helpful:
Krause, P., Boyle, D.P., Bäse, F., 2005. Comparison of different efficiency criteria for hydrological model assessment. Advances in Geosciences 31, 89–97.
