User Tools

Site Tools


start:hype_file_reference:timexxxx.txt

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_file_reference:timexxxx.txt [2017/12/15 12:33]
cpers
start:hype_file_reference:timexxxx.txt [2018/06/05 15:41]
cpers
Line 18: Line 18:
 Example structure of a map output file //​timeCOUT.txt//​ with daily discharge averages for a model with four sub-catchments:​ Example structure of a map output file //​timeCOUT.txt//​ with daily discharge averages for a model with four sub-catchments:​
  
-   This is a file with timeseries of comp outflow olake in m3/s+  !!This is a file with timeseries of comp outflow olake in m3/s
   DATE        4080    4090    4113    4139   DATE        4080    4090    4113    4139
   2009-07-01 ​ 0.0096 ​ 0.0096 ​ 0.1511 ​ 0.1615   2009-07-01 ​ 0.0096 ​ 0.0096 ​ 0.1511 ​ 0.1615
Line 28: Line 28:
          ​... ​    ​... ​    ​... ​    ​... ​    ...          ​... ​    ​... ​    ​... ​    ​... ​    ...
  
-It is possible to print out timeoutput files for several mean periods at the same simulation. This is controlled from the info-file by numbering the different output information rows for the different types (see [[start:​hype_file_reference:​info.txt|info.txt]] for example). If this option is used the second and following ​outputs will be separated ​from the first by adding the mean period as a code in the file name, e.g. timeCOUT_YR.txt holds yearly average of //cut//.+It is possible to print out timeoutput files for several mean periods at the same simulation. This is controlled from the info-file by numbering the different output information rows for the different types (see [[start:​hype_file_reference:​info.txt|info.txt]] for example). If this option is used the time outputs will be separated by adding the mean period as a code in the file name, e.g. timeCOUT_YR.txt holds yearly average of //cout//.
  
 When ensemble or sequence simulations are made, the results from simulations (I = 1 .. //n// or I = sequence number > 0) are written to files named timeXXXX_00I.txt,​ where //n// is defined by ''​num_ens''​ in [[start:​hype_file_reference:​optpar.txt|optpar.txt]]. ​ Alternatively,​ if a Monte Carlo simulation is done with task set to write all simulations (''​task WS''​ in [[start:​hype_file_reference:​optpar.txt|optpar.txt]]) files will be named //​XXXXXXX_000000I.txt//​. In this case up to 9999999 simulations can be saved. ​ When ensemble or sequence simulations are made, the results from simulations (I = 1 .. //n// or I = sequence number > 0) are written to files named timeXXXX_00I.txt,​ where //n// is defined by ''​num_ens''​ in [[start:​hype_file_reference:​optpar.txt|optpar.txt]]. ​ Alternatively,​ if a Monte Carlo simulation is done with task set to write all simulations (''​task WS''​ in [[start:​hype_file_reference:​optpar.txt|optpar.txt]]) files will be named //​XXXXXXX_000000I.txt//​. In this case up to 9999999 simulations can be saved. ​
 +
 +Class output files may also be called timeXXXX, but they are followed by a suffix naming the class group, e.g. timeCRUN_CG1.txt for the CG1 class group'​s local runoff. The file comment will contain information on which classes are included in the group. Otherwise the file is similar to the ordinary time-files. All subbasins class group variable data is printed. ​
  
start/hype_file_reference/timexxxx.txt.txt ยท Last modified: 2024/01/25 11:38 (external edit)