User Tools

Site Tools


start:hype_file_reference:info.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:info.txt [2021/04/09 08:08]
cpers [Updating options]
start:hype_file_reference:info.txt [2021/07/05 17:11]
cpers
Line 42: Line 42:
 | ''​outstatecompress'' ​    | //​Y/​N// ​     | defines whether the created outstate files are to be compressed and the text file then deleted. Y for yes, N for no. No is default. The filename of the compressed file is the same as for the ASCII-text state file, but with different file ending (state_saveyyyymmdd[HHMM].tgz). ​                                                                                                                                                                                                                               | | ''​outstatecompress'' ​    | //​Y/​N// ​     | defines whether the created outstate files are to be compressed and the text file then deleted. Y for yes, N for no. No is default. The filename of the compressed file is the same as for the ASCII-text state file, but with different file ending (state_saveyyyymmdd[HHMM].tgz). ​                                                                                                                                                                                                                               |
 | ''​resetstatedate'' ​     | //​date-time// ​      | defines that nutrient soil states will be reset to the starting state. The date should be in the format yyyy-mm-dd [HH:MM]. The default is that no reset is done. Maximum 100 dates may be given. The dates may be written on same or different rows. In the latter case, the code first on every row. The reset starting state is saved in file [[start:​hype_file_reference:​reset_state_save|reset_state_save.txt]]. ​                                                                                                                                                                                                                              | | ''​resetstatedate'' ​     | //​date-time// ​      | defines that nutrient soil states will be reset to the starting state. The date should be in the format yyyy-mm-dd [HH:MM]. The default is that no reset is done. Maximum 100 dates may be given. The dates may be written on same or different rows. In the latter case, the code first on every row. The reset starting state is saved in file [[start:​hype_file_reference:​reset_state_save|reset_state_save.txt]]. ​                                                                                                                                                                                                                              |
-| ''​substance'' ​        | //​string// ​         | gives the substances to be simulated. One or several of: //N P C S T1 T2//. N - nitrogen, P - phosphorus, C - organic carbon, S - total suspended sediment, T1 - tracer, and T2 - water temperature. Substances may be defined on one or several rows (with the code preceding the substance on each row) with one or several substances per row (separated by space). The default is to simulate no substances, only water. ​                                                                                                                                                                                                        |+| ''​substance'' ​        | //​string// ​         | gives the substances to be simulated. One or several of: //N P C S Si T1 T2//. N - nitrogen, P - phosphorus, C - organic carbon, S - total suspended sediment, Si - silica, T1 - tracer, and T2 - water temperature. Substances may be defined on one or several rows (with the code preceding the substance on each row) with one or several substances per row (separated by space). The default is to simulate no substances, only water. ​                                                                                                                                                                                                        |
 | ''​calibration'' ​      | //​Y/​N// ​            | defines whether or not automatic calibration is to be done. //Y// for calibration. Default is //N//. Calibration method and parameters are defined in file [[start:​hype_file_reference:​optpar.txt|optpar.txt]]. Note that reading of initial state does not work with automatic calibration of parameters rivvel and damp, or soilcorr. ​                                                                                                                                                                                                                                                               | | ''​calibration'' ​      | //​Y/​N// ​            | defines whether or not automatic calibration is to be done. //Y// for calibration. Default is //N//. Calibration method and parameters are defined in file [[start:​hype_file_reference:​optpar.txt|optpar.txt]]. Note that reading of initial state does not work with automatic calibration of parameters rivvel and damp, or soilcorr. ​                                                                                                                                                                                                                                                               |
 | ''​weightsub'' ​      | //​Y/​N// ​            | defines if the objective function and performance criteria should be weighted by a given trust in each subcatchment (only for criteria that are average of subbasins). Default is no.                                                                                                                                                                                                                                                               | | ''​weightsub'' ​      | //​Y/​N// ​            | defines if the objective function and performance criteria should be weighted by a given trust in each subcatchment (only for criteria that are average of subbasins). Default is no.                                                                                                                                                                                                                                                               |
Line 116: Line 116:
 The principal outputs are specified with two codes in //​info.txt//,​ first code giving the output type and second specifying content options. After the codes follow the arguments. Content option codes are identical for all basic output types. All outputs are technically optional. The principal outputs are specified with two codes in //​info.txt//,​ first code giving the output type and second specifying content options. After the codes follow the arguments. Content option codes are identical for all basic output types. All outputs are technically optional.
  
-It is possible to get output for several different aggregation periods for the same type of output (basin- , class-, region- or time-output) by specifying several groups of the same type of output with ordinal number between **Code 1** and **Code 2**. See example below the table. The files will then have a suffix to their name to separate them, e.g. //​timeCRUN_DD.txt//​. If only one non-numbered group is used no meanperiod suffix will be added to the file(s). The number between **Code 1** and **Code 2** is also used to hold together classoutput information for different variables/​groups/​meanperiods.+Output can be given for each time step or aggregated to longer periods. This is specified by the code ''​meanperiod''​. For available aggregation periods see table [[info.txt#​aggregation_period_codes|below]]. The aggregation works best if it is in alignment with the simulation and output start date, e.g. yearly output that start 1 January.  
 + 
 +It is possible to get output for several different aggregation periods for the same type of output (basin- , class-, region- or time-output) by specifying several groups of the same type of output with an ordinal number between **Code 1** and **Code 2**. See example below the table. The files will then have a suffix to their name to separate them, e.g. //​timeCRUN_DD.txt//​. If only one non-numbered group is used no meanperiod suffix will be added to the file(s). The number between **Code 1** and **Code 2** is also used to hold together classoutput information for different variables/​groups/​meanperiods. Note that the ordinal number need to begin at 1 and go up, no gaps allowed.
  
  
Line 137: Line 139:
  
 === Aggregation period codes === === Aggregation period codes ===
-Aggregation ​period codes (used for ''​meanperiod''​) and corresponding file name suffix. Simulation period (''​5''​) aggregates are means of annual aggregates. ​+The table below shows aggregation ​period codes (used for ''​meanperiod''​) and corresponding file name suffix. Simulation period (''​5''​) aggregates are means of annual aggregates. ​
  
 ^ Code ^ Suffix ^ Description ^ ^ Code ^ Suffix ^ Description ^
Line 200: Line 202:
 ===== Updating options ===== ===== Updating options =====
  
-HYPE allows updating of simulated discharge and lake water level with observations during model run as well as updating of nitrogen and phosphorus concentrations using correction factors or observations in individual subbasins. Discharge can be updated ​directly ​by discharge ​observations,​ by previously saved errors of simulated discharge, and/or previously saved errors of simulated lake water level. An auto-regressive (AR) model is used to model the errors for the last two methods. Lake water level can be updated by water level observations ​or by previously saved errors of simulated lake water level+HYPE allows updating of simulated discharge and lake water level with observations during model run as well as updating of nitrogen and phosphorus concentrations using correction factors or observations in individual subbasins. Discharge can be updated by discharge or water level observations by various ​methods. Lake water level can be updated by water level observations. ​
  
 The updating methods are described in the [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_tutorials:​updating|tutorial]]. Some updating routines require further settings in an additional input file [[start:​hype_file_reference:​update.txt|update.txt]]. The updating methods are described in the [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_tutorials:​updating|tutorial]]. Some updating routines require further settings in an additional input file [[start:​hype_file_reference:​update.txt|update.txt]].
start/hype_file_reference/info.txt.txt · Last modified: 2024/02/21 08:47 by cpers