Model output - Revision history

Santosh: /* Numerical output */

2012-10-17T09:40:09Z

Numerical output

← Older revision		Revision as of 09:40, 17 October 2012
Line 64:		Line 64:
	[[file:Jams_timeloop.png\|1000x1000px\| Timeloop file]]		[[file:Jams_timeloop.png\|1000x1000px\| Timeloop file]]

−	The output variables in the timeloop can be viewed instantly after the model run. The following tutorial describes the detailed information about the use and fuctions of JADE component within the JAMS framework. [http://ilms.uni-jena.de/ilmswiki/index.php/Tutorial_Basic_Users#Exercises_for_the_Tutorial_Basic_Users# Data analysis using JADE]	+	The output variables in the timeloop can be viewed instantly after the model run. The following tutorial describes the detailed information about the use and fuctions of JADE component within the JAMS framework. [http://ilms.uni-jena.de/ilmswiki/index.php/Tutorial_Basic_Users#Exercises_for_the_Tutorial_Basic_Users Data analysis using JADE]

	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		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

Santosh: /* Numerical output */

2012-10-17T09:39:32Z

Numerical output

← Older revision		Revision as of 09:39, 17 October 2012
Line 64:		Line 64:
	[[file:Jams_timeloop.png\|1000x1000px\| Timeloop file]]		[[file:Jams_timeloop.png\|1000x1000px\| Timeloop file]]

−	The output variables in the timeloop can be viewed instantly after the model run. The following tutorial describes the detailed information about the use and ~~fuction~~ of JADE component within the JAMS framework. [http://ilms.uni-jena.de/ilmswiki/index.php/Tutorial_Basic_Users#Exercises_for_the_Tutorial_Basic_Users# JADE ~~component~~ ]	+	The output variables in the timeloop can be viewed instantly after the model run. The following tutorial describes the detailed information about the use and fuctions of JADE component within the JAMS framework. [http://ilms.uni-jena.de/ilmswiki/index.php/Tutorial_Basic_Users#Exercises_for_the_Tutorial_Basic_Users# Data analysis using JADE]

	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		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

Santosh: /* Numerical output */

2012-10-17T09:35:37Z

Numerical output

← Older revision		Revision as of 09:35, 17 October 2012
Line 64:		Line 64:
	[[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 described in previous paragraph for~~	+	The output variables in the timeloop can be viewed instantly after the model run. The following tutorial describes the detailed information about the use and fuction of JADE component within the JAMS framework. [http://ilms.uni-jena.de/ilmswiki/index.php/Tutorial_Basic_Users#Exercises_for_the_Tutorial_Basic_Users# JADE component ]

		+	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.		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.

Santosh: /* Efficiency measurement */

2012-10-17T09:15:45Z

Efficiency measurement

← Older revision		Revision as of 09:15, 17 October 2012
Line 73:		Line 73:
	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 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:Efficiency2.png\|700x700px\| JAMS efficiency]]

	The details of the objective functions are provided below:		The details of the objective functions are provided below:

Santosh at 09:07, 17 October 2012

2012-10-17T09:07:57Z

← Older revision		Revision as of 09:07, 17 October 2012
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. ~~Similaly~~, the values can be downloaded by clicking the save ~~botton~~ (the red box in right hand side). The GIS shape file with HRU ID and values associated with each HRUs are saved.	+	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 ~~deterimed~~ 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.	+	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 ~~desribed~~ in previous paragraph for	+	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 ~~everytime~~ when the model is run. Disabling the HRULoop.xml will not produce HRULoop.dat file.	+	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 '~~ExicutionInfo~~' 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 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]]

Santosh: /* Numerical output */

2012-10-17T09:02:25Z

Numerical output

← Older revision		Revision as of 09:02, 17 October 2012
Line 67:		Line 67:


−	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 everytime when the model is run. ~~Removing~~ the HRULoop.xml ~~file (from output folder)~~ will not produce HRULoop.dat file.	+	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 everytime when the model is run. Disabling the HRULoop.xml will not produce HRULoop.dat file.

	===Efficiency measurement===		===Efficiency measurement===

Santosh: /* Numerical output */

2012-10-17T09:01:54Z

Numerical output

← Older revision		Revision as of 09:01, 17 October 2012
Line 66:		Line 66:
	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 desribed in previous paragraph for		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 desribed in previous paragraph for

−	*HRULoop.xml file
−	~~[[file:HRULoop.png\|700x700px\| HRULoop file]]~~

	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 everytime when the model is run. Removing the HRULoop.xml file (from output folder) will not produce HRULoop.dat file.		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 everytime when the model is run. Removing the HRULoop.xml file (from output folder) will not produce HRULoop.dat file.

Santosh: /* Numerical output */

2012-10-16T15:35:55Z

Numerical output

← Older revision		Revision as of 15:35, 16 October 2012
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 deterimed inside the TimeLoop.xml file which is placed outside the current folder. ~~The~~ variables of the timeloop can be changed 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.	+	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 deterimed 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]]

−	~~The TimeLoop.xml has daily output variables as shown in Figure below. If users do not need some variables~~, ~~they can comment out~~ the ~~particular variables as shown in the case of netRain in the figure.~~	+	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 desribed in previous paragraph for
−		+
−	*TimeLoop.xml file	+
−	~~[[file:Timeloop.png\|800x800px\| Timeloop file]]~~	+
−		+
−	~~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 ~~comment out some~~ variables as ~~shown~~ in ~~the case of wind below.~~	+

	*HRULoop.xml file		*HRULoop.xml file

Santosh: /* Numerical output */

2012-10-16T15:29:39Z

Numerical output

← Older revision		Revision as of 15:29, 16 October 2012
Line 60:		Line 60:
	===Numerical output===		===Numerical output===

−	The ~~model~~ outputs ~~on a daily resolution~~ are provided in the output folder (current-->> Timeloop.dat filename) after each model run. ~~The~~ variables which need to be produced as output data is deterimed inside the TimeLoop.xml file which is placed outside the current folder. The variables of the timeloop can be changed 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.	+	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 deterimed inside the TimeLoop.xml file which is placed outside the current folder. The variables of the timeloop can be changed 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]]

Santosh: /* Numerical output */

2012-10-16T15:21:24Z

Numerical output

← Older revision		Revision as of 15:21, 16 October 2012
Line 60:		Line 60:
	===Numerical output===		===Numerical output===

−	The model outputs on a daily resolution are provided in the output folder (current-->> Timeloop.dat filename) after each model run. The variables which need to be produced as output data is deterimed inside the TimeLoop.xml file which is placed outside the current folder. The variables of the timeloop can be changed 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' ~~(as shown in figure below)~~.	+	The model outputs on a daily resolution are provided in the output folder (current-->> Timeloop.dat filename) after each model run. The variables which need to be produced as output data is deterimed inside the TimeLoop.xml file which is placed outside the current folder. The variables of the timeloop can be changed 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]]