In the Model parameter files table, the names of the files containing the model parameters to be manipulated by AutoCal are specified.
AutoCal can manipulate parameters in the model parameter files associated with the numerical calculation kernels. For some simulation models only one model parameter file is associated, but for some models (e.g. MIKE 11 and MIKE SHE) several model parameter files can be manipulated. AutoCal can also manipulate parameters in any ASCII file.
When a model parameter file is selected, a corresponding template file is automatically created -with _Autocal added to the file name. This template file is simply a replica of the model parameter file. It is used for placing parameter identification tags at the locations where the values of the model parameters to be manipulated in AutoCal are given. The template file can be directly edited from AutoCal. For MIKE Zero PFS files, the corresponding editor is opened. For ASCII files, Notepad is opened.
Identification tags for model parameters
In AutoCal, reserved floating point values are used as identification tags. The identification tags are the values 1.01e-35, 1.02e-35, ..., 9.99e-35. In the model editor, the identification tag is placed in the field where the numerical value of the model parameter is given. Individual parameters must be given unique identification tags.
If several model parameters should be given the same parameter value in AutoCal, the same identification tag can be used. If different identification tags are used, then the parameters can be coupled using the parameter options on the Model Parameters tab.
When the template file has been created and the parameter identification tags have been entered, a table with the model parameters is automatically created on the Model Parameters tab.
When running AutoCal, a second template file is created (.tpl is added to the file name) that is used internally by AutoCal.
Units used in AutoCal
AutoCal optimizes the parameters stored in the pfs file. However, parameters stored in these files are stored using the base units for the parameter type. The base units are always standard SI units. Thus, if you are not using the base parameter units (e.g. feet instead of metres), AutoCal will ignore these unit changes. Thus, you must always use the base units if you want to use AutoCal - or at least be aware that the optimized values output by AutoCal are in the base SI units.