User Tools

Site Tools


start:hype_tutorials:short_intro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
start:hype_tutorials:short_intro [2018/08/23 13:49]
cpers [Get and run the model]
start:hype_tutorials:short_intro [2019/07/29 13:16]
cpers [Get and run the model]
Line 8: Line 8:
 The code is written in Fortran and is open source under the Lesser GNU Public License. SMHI took the initiative for a HYPE Open Source Community to strengthen international collaboration in hydrological modelling. More information about the initiative can be found at [[http://​hypecode.smhi.se/​|hypecode.smhi.se]].  ​ The code is written in Fortran and is open source under the Lesser GNU Public License. SMHI took the initiative for a HYPE Open Source Community to strengthen international collaboration in hydrological modelling. More information about the initiative can be found at [[http://​hypecode.smhi.se/​|hypecode.smhi.se]].  ​
  
-A HYPE simulation is started from the command line with the path to the model simulation configuration file as argument. Note that the path ends with a slash. For example:+A HYPE simulation is started from the command line with the path to the model simulation configuration file as argument. Note that the path ends with a slash. For example, if your model is put in the folder model1 in the modelsetups folder on the D-drive and your Windows executable is on the P-drive, your command will look like this:
  
 Windows Command Prompt: Windows Command Prompt:
Line 14: Line 14:
 or Linux terminal: or Linux terminal:
   $ ./hype /​data/​hypemodels/​model2/​   $ ./hype /​data/​hypemodels/​model2/​
 +
 +In the Windows example your model is put in the folder model1 in the modelsetups folder on the D-drive and your HYPE executable is in the current folder, i.e on the P-drive. In the Linux example, your model is put in the folder model2 in the hypemodels folder in the data folder and your HYPE executable is in the current folder. ​
  
 Note: Older versions of the HYPE executable (before 5.6.0) return a **//Code 84//** message after a successful run. Note: Older versions of the HYPE executable (before 5.6.0) return a **//Code 84//** message after a successful run.
Line 70: Line 72:
 With no settings given in the [[start:​hype_file_reference:​info.txt|info.txt]] the log-file ([[start:​hype_file_reference:​hyss_yymmddhhmm.log|hyss_seqnr_yymmddHHMM.log]]) is the only result of the simulation. The log-file contains information about running time and input files used. You will also get warning or error messages in the log-file. ​ With no settings given in the [[start:​hype_file_reference:​info.txt|info.txt]] the log-file ([[start:​hype_file_reference:​hyss_yymmddhhmm.log|hyss_seqnr_yymmddHHMM.log]]) is the only result of the simulation. The log-file contains information about running time and input files used. You will also get warning or error messages in the log-file. ​
  
-There are several [[start:​hype_file_reference#​output_files|options for output]] of simulation results, but all result in text-files. The example given above with [[start:​HYPE_file_reference:​timeXXXX.txt|timeseries output]] of discharge will produce a file called ​**timeCOUT.txt** with time series for simulated outflow (''​cout''​) from each subbasin in the model set-up as columns (defined by ''​subid''​). Similarly for other output the variable id and the subbasin id are given in the file name or in the heading of the file. It is also possible to print period mean values of a variable instead of time series. ​+There are several [[start:​hype_file_reference#​output_files|options for output]] of simulation results, but all result in text-files. The example given above with [[start:​HYPE_file_reference:​timeXXXX.txt|timeseries output]] of discharge will produce a file named **timeCOUT.txt** with time series for simulated outflow (''​cout''​) from each subbasin in the model set-up as columns (defined by ''​subid''​). Similarly for other output the variable id and the subbasin id are given in the file name or in the heading of the file. It is also possible to print period mean values of a variable instead of time series. ​
  
 HYPE can calculate performance criteria when observations are provided, e.g file [[start:​hype_file_reference:​qobs.txt|Qobs.txt]] with observed discharge, and the variables to be compared are given in [[start:​hype_file_reference:​info.txt|info.txt]]. A selection of performance criteria will be calculated for every subbasin (with observations) and printed in the [[start:​hype_file_reference:​subassx.txt|subassX.txt]] file, one subbasin per row. Example of performance criteria in [[start:​hype_file_reference:​subassx.txt|subassX.txt]];​ NSE – Nash-Sutcliffe Efficiency, CC – correlation coefficient,​ and MAE – mean absolute error. Some average performance criteria for the whole model set-up are also printed in the log-file and the [[start:​hype_file_reference:​simass.txt|simass.txt]] file. HYPE can calculate performance criteria when observations are provided, e.g file [[start:​hype_file_reference:​qobs.txt|Qobs.txt]] with observed discharge, and the variables to be compared are given in [[start:​hype_file_reference:​info.txt|info.txt]]. A selection of performance criteria will be calculated for every subbasin (with observations) and printed in the [[start:​hype_file_reference:​subassx.txt|subassX.txt]] file, one subbasin per row. Example of performance criteria in [[start:​hype_file_reference:​subassx.txt|subassX.txt]];​ NSE – Nash-Sutcliffe Efficiency, CC – correlation coefficient,​ and MAE – mean absolute error. Some average performance criteria for the whole model set-up are also printed in the log-file and the [[start:​hype_file_reference:​simass.txt|simass.txt]] file.
  
  
start/hype_tutorials/short_intro.txt · Last modified: 2024/01/25 11:37 (external edit)