User Tools

Site Tools


start

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
start [2019/11/11 08:42]
cpers [How to run HYPE]
start [2020/02/28 10:46] (current)
cpers [Table]
Line 5: Line 5:
 ** **
  
-{{:​hype_box_picture_v2.png?​300|HYPE water stores and flows}}+{{:​hype_box_picture_v2.png?​600|HYPE water stores and flows}}
  
 HYPE model results are used for operational forecasts, climate-change impact assessments and scientific research (explore results on [[https://​hypeweb.smhi.se/​|hypeweb]]). ​ HYPE model results are used for operational forecasts, climate-change impact assessments and scientific research (explore results on [[https://​hypeweb.smhi.se/​|hypeweb]]). ​
Line 29: Line 29:
 ==== How to run HYPE ==== ==== How to run HYPE ====
  
-HYPE does not provide a graphical user interface. Users provide model set-up options and input data to HYPE using input text files. Model outputs are returned as text files as well. The compiled HYPE executable is run by double-clicking (on Windows) or by call from a command line (Windows or Linux). A system installation is not required. When invoked from the command line, HYPE takes two command line arguments: The search path to the folder where the [[start:​hype_file_reference:​info.txt|info.txt]] file with model setup arguments is stored which is mandatory, ​and a sequence number which is optional. ​+HYPE does not provide a graphical user interface. Users provide model set-up options and input data to HYPE using input text files. Model outputs are returned as text files as well. The compiled HYPE executable is run by double-clicking (on Windows) or by call from a command line (Windows or Linux). A system installation is not required. When invoked from the command line, HYPE takes up to three command line arguments: The search path to the folder where the [[start:​hype_file_reference:​info.txt|info.txt]] file with model setup arguments is stored which is mandatory, a sequence number which is optional, and an optional flag for name of parameter file
  
-^ flag      ^ argument ​      ​^  +^ flag                 ​^ argument ​        ​
-| -infodir //or// -i    | path     ​+| -infodir //or// -i   ​| path             ​
-| -sequence //or// -s    | seqnr    |+| -sequence //or// -s  | seqnr            | 
 +| -p                   | //no argument//  ​|
  
  
-The path can either be given as an absolute address or relative from the folder in which the program is started. The path may have a maximum of 200 characters and need surrounding apostrophes '​path'​ if blanks are included in the path. The search path should end with a slash. The sequence number is an integer between 0 and 999. The sequence number determines which forcing files to use. Seqnr 0 uses forcing files without sequence number.+The path can either be given as an absolute address or relative from the folder in which the program is started. The path may have a maximum of 200 characters and need surrounding apostrophes '​path'​ if blanks are included in the path. The search path should end with a slash. The sequence number is an integer between 0 and 999. The sequence number determines which forcing files to use. The parameter flag determines that the sequence number should be applied to parameter file as well as the forcing files. Seqnr 0 uses forcing files without sequence number.
 If no argument is found. e.g. when double-clicking on the executable, the program tries to find a file filedir.txt in the starting folder and read the path to info.txt there. It is also possible to give the path as the only argument without the -i flag. If no argument is found. e.g. when double-clicking on the executable, the program tries to find a file filedir.txt in the starting folder and read the path to info.txt there. It is also possible to give the path as the only argument without the -i flag.
  
start.1573458167.txt.gz · Last modified: 2019/11/11 08:42 by cpers