There is a PESTSU file that can be specified in the FILES block.
FILES
<FILE> <UN#>***<----FILE NAME------------------------------------------------->
MESSU 24 3a.ech
WDM1 25 sjrb_met.wdm
WDM2 26 sjrb_lsj.wdm
WDM3 27 irrig_3A.wdm***
80 3a_land.out
82 3a_reach.out
BINO 81 3a_land.hbn
BINO 83 3a_reach.hbn
PESTSU 41 3a_hspf.sup
END FILES
And then in most tables you can specify a record to look up values in the PESTSU file. The record ID to lookup is quoted by "~".
PWAT-PARM2
*** 3A REACH 1 - Lake Dias Outlet Location 301
1 ~111130101~
2 ~111130102~
END PWAT-PARM2
The contents of the 3a_hspf.sup file would look something like:
111130101 7
0.2 8.0 0.7 400. .001 0.0 .98
111130102 7
0.21 8.0 0.745634223223 400. .001 0.04 .994
Where a record covers two lines, the first line is the record ID and the number of values on the second line that are used to fill out the table in the UCI file. The second line is space-delimited values. This was to support the parameter estimation process which required high precision that was larger than the 10 spaces typically available in the standard UCI table. Note need a value for each parameter, no defaulting.
There is a PESTSU file that can be specified in the FILES block.
And then in most tables you can specify a record to look up values in the PESTSU file. The record ID to lookup is quoted by "~".
The contents of the 3a_hspf.sup file would look something like:
Where a record covers two lines, the first line is the record ID and the number of values on the second line that are used to fill out the table in the UCI file. The second line is space-delimited values. This was to support the parameter estimation process which required high precision that was larger than the 10 spaces typically available in the standard UCI table. Note need a value for each parameter, no defaulting.