User Tools

Site Tools


start:hype_file_reference:optpar.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
start:hype_file_reference:optpar.txt [2018/09/06 15:20]
cpers [File content]
start:hype_file_reference:optpar.txt [2024/01/25 11:37] (current)
Line 1: Line 1:
 ====== optpar.txt ====== ====== optpar.txt ======
  
-The file holds additional model options ​to [[start:​hype_file_reference:​info.txt|info.txt]] and is therefore located in the same folder as [[start:​hype_file_reference:​info.txt|info.txt]]. The file is used to define what kind of optimisation to be done if ''​calibration''​ is set in [[start:​hype_file_reference:​info.txt|info.txt]]. There are several different methods to chose from, each with their settings. Which model parameters to calibrate and within which boundaries are information also given in //​optpar.txt//​.+The file holds additional model settings ​to [[start:​hype_file_reference:​info.txt|info.txt]] and is therefore located in the same folder as [[start:​hype_file_reference:​info.txt|info.txt]]. The file is used to define what kind of optimisation to be done if ''​calibration''​ is set in [[start:​hype_file_reference:​info.txt|info.txt]]. There are several different methods to chose from, each with their settings. Which model parameters to calibrate and within which boundaries are information also given in //​optpar.txt//​. ​
  
 Maximum 100 model parameters may be optimised simultaneously. To optimise more parameters, the code needs to be changed (set //​maxoptpar//​ to a higher value). All parameters are described in the section on [[start:​hype_file_reference:​par.txt|par.txt]],​ but not all of them can be calibrated. The objective function of the optimization is defined in [[start:​hype_file_reference:​info.txt|info.txt]] as the combination of criteria chosen, see [[start:​hype_file_reference:​info.txt#​performance_criteria_options|Performance criteria options]]. ​ Maximum 100 model parameters may be optimised simultaneously. To optimise more parameters, the code needs to be changed (set //​maxoptpar//​ to a higher value). All parameters are described in the section on [[start:​hype_file_reference:​par.txt|par.txt]],​ but not all of them can be calibrated. The objective function of the optimization is defined in [[start:​hype_file_reference:​info.txt|info.txt]] as the combination of criteria chosen, see [[start:​hype_file_reference:​info.txt#​performance_criteria_options|Performance criteria options]]. ​
  
-There are eight methods of optimisation implemented in HYPE as detailed in the table below. Additionally,​ there are two other tasks for output generation, ''​WA''​ and ''​WS'',​ which produce detailed performance and simulation results for all runs performed during optimisation. Tasks ''​WA''​ and ''​WS''​ are compatible with selected optimisation methods only, a denoted in the table. The task of organized scanning ''​SC''​ is a parameter investigation method.+There are eight methods of optimisation implemented in HYPE as detailed in the table below (read more about them in the [[start:​hype_tutorials:​automatic_calibration|tutorial]]). Additionally,​ there are two other tasks for output generation, ''​WA''​ and ''​WS'',​ which produce detailed performance and simulation results for all runs performed during optimisation. Tasks ''​WA''​ and ''​WS''​ are compatible with selected optimisation methods only, a denoted in the table. The task of organized scanning ''​SC''​ is a parameter investigation method.
  
-/** +The optpar.txt ​file may also be used for parameter ensemble simulation (''​parensemble''​ in info.txt), to know which model parameters to useThe parameter ensemble may use the parameters earlier found by calibration.
- * ____________IMPORTANT!__________IMPORTANT!________________IMPORTANT!_______________________IMPORTANT!______________ +
- * +
- ​* ​The table below is maintained in spreadsheed ​file 'file_reference_tables.xlsx' +
- ​* ​in the wiki back-up folder on our server. +
- * Please edit table contents there and then copy-paste the updated full table to this pageAsk René if something is  +
- * unclear. Thanks. +
- * ___________________________________________________________________________________________________________________ +
- */+
  
 <​sortable>​ <​sortable>​
Line 29: Line 21:
 |''​SC''​|organised scanning of two parameters| |''​SC''​|organised scanning of two parameters|
 |''​WA''​|write performance result for all simulations (''​MC'',​ ''​SM''​ or ''​DE''​)| |''​WA''​|write performance result for all simulations (''​MC'',​ ''​SM''​ or ''​DE''​)|
-|''​WS''​|write simulation results ([[.:​xxxxxxx.txt|basin-]],​ [[.:​timexxxx.txt|time-]] ​or [[.:​mapxxxx.txt|map-]]files) for all ensembles in Monte Carlo simulation (''​MC'',​ ''​BP'',​ or ''​DE''​) ​(maximum 9999999 ensembles total)|+|''​WS''​|write simulation results ([[.:​xxxxxxx.txt|basin-]],​ [[.:​timexxxx.txt|time-]][[.:​mapxxxx.txt|map-]], , [[.:​xxxxxxx.txt_regional|regional-]],​ or , [[.:​class_output|class-]]files) for all ensembles in Monte Carlo simulation (''​MC'',​ ''​BP'',​ or ''​DE''​)
 +|''​AS''​|run parameter ensemble simulations with parameters found in allsim.txt| 
 +|''​BS''​|run parameter ensemble simulations with parameters found in bestsims.txt|
 </​sortable>​ </​sortable>​
  
Line 36: Line 30:
  
 In the calibration setting section a row starts with a code indicating a task or other settings. Argument of the code is listed from position 12 and forward on each row. The following options are available for the calibration setting section: In the calibration setting section a row starts with a code indicating a task or other settings. Argument of the code is listed from position 12 and forward on each row. The following options are available for the calibration setting section:
- 
-/** 
- * ____________IMPORTANT!__________IMPORTANT!________________IMPORTANT!_______________________IMPORTANT!______________ 
- * 
- * The table below is maintained in spreadsheed file '​file_reference_tables.xlsx'​ 
- * in the wiki back-up folder on our server. 
- * Please edit table contents there and then copy-paste the updated full table to this page. Ask René if something is  
- * unclear. Thanks. 
- * ___________________________________________________________________________________________________________________ 
- */ 
  
 <​sortable>​ <​sortable>​
Line 64: Line 48:
 |''​DEMC_crossover''​|//​real//​|1|crossover probability for DEMC method. Probability that the proposed candidate is chosen instead of the parent parameter. Large ''​DEMC_crossover''​ values mean larger probability that the proposal is chosen. Set to 1, all proposals are accepted. This makes it harder to find an acceptable overall proposal because all parameters are changed in every generation. Set to 0.5, each parameter candidate has only a 50% chance to be accepted into the next proposal.| |''​DEMC_crossover''​|//​real//​|1|crossover probability for DEMC method. Probability that the proposed candidate is chosen instead of the parent parameter. Large ''​DEMC_crossover''​ values mean larger probability that the proposal is chosen. Set to 1, all proposals are accepted. This makes it harder to find an acceptable overall proposal because all parameters are changed in every generation. Set to 0.5, each parameter candidate has only a 50% chance to be accepted into the next proposal.|
 |''​DEMC_sigma''​|//​real//​|0.1|sample error standard deviation for DEMC method. Base for the standard deviation of the random perturbation,​ which adds random noise to the proposed parameter in addition to the gamma-mutation. This value is multiplied with 3rd-row value for each parameter (see description of parameter rows below).| |''​DEMC_sigma''​|//​real//​|0.1|sample error standard deviation for DEMC method. Base for the standard deviation of the random perturbation,​ which adds random noise to the proposed parameter in addition to the gamma-mutation. This value is multiplied with 3rd-row value for each parameter (see description of parameter rows below).|
-|''​DEMC_accprob''​|//​integer//​|0|scaling factor for probabilistic acceptance for DEMC method (0 = off (default); >0 = on). If set to off, parameter proposals will only (and always) be accepted if the likelyhood score decreases (= better performance). High values will increase the probability of acceptance ​within the probabilistic framework, a value of 1 means no scaling.|+|''​DEMC_accprob''​|//​integer//​|0|scaling factor for probabilistic acceptance for DEMC method (0 = off (default); >0 = on). If set to off, parameter proposals will only (and always) be accepted if the objective function ​decreases (= better performance). If turned on, also proposals with higher value of the objective function can be accepted; better performance will give higher probability of acceptance. High values ​of the scaling factor ​will also increase the probability of acceptance.|
 |''​BR_diagStp''​|//​Y/​N//​|YES|flag for taking a diagonal step at the end of each iteration (BN method)| |''​BR_diagStp''​|//​Y/​N//​|YES|flag for taking a diagonal step at the end of each iteration (BN method)|
 |''​num_maxItr''​|//​integer//​|500|max amount of iterations (interrupt non-MonteCarlo methods)| |''​num_maxItr''​|//​integer//​|500|max amount of iterations (interrupt non-MonteCarlo methods)|
Line 88: Line 72:
   * **Row 3** specifies either a minimum step width for parameter change //or//, in case of the ''​DE''​ method, a parameter specific factor to scale the random noise added to the proposed next-generation parameter, see description of DEMC settings code ''​DEMC_sigma''​ in table above.   * **Row 3** specifies either a minimum step width for parameter change //or//, in case of the ''​DE''​ method, a parameter specific factor to scale the random noise added to the proposed next-generation parameter, see description of DEMC settings code ''​DEMC_sigma''​ in table above.
  
-**NOTE**: If lower and upper boundaries are identical, the parameter is omitted. This allows to calibrate a selection of the values for dependent parameters. ​ +**NOTE**: If lower and upper boundaries are identical, the parameter is omitted. This allows to calibrate a selection of the values for dependent parameters. ​The omitted parameters will not be included in the result in //​bestsims.txt//​ and //​allsim.txt//​. The omitted parameters will be included in the result //​respar.txt//​. ​
  
 Example of parameter rows in //​optpar.txt//:​ Example of parameter rows in //​optpar.txt//:​
start/hype_file_reference/optpar.txt.1536240032.txt.gz · Last modified: 2023/11/16 14:28 (external edit)