Revision as of 10:32, 24 January 2023 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,789 edits →Boundary Condition Conversion ← Older edit		Revision as of 10:34, 24 January 2023 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,789 edits →Boundary Condition Conversion Newer edit →
Line 150: <li> Provide the HEC-DSS filename in the “Source” column. <li> Leave “Column 1”, which is used for time, blank (DSS files store the time with the curve values). <li> Identify the pathname in “Column 22”.” Event placeholders such as __event__ can be used as part of the pathname. Wilcards () can be used for parts of the path, however, ensure the wildcards will not select more than one path within the file. <li> The “Add” and “Mult” columns can be used to offset or scale the time-series values, the same as non-DSS time-series curves. </ol> The image below shows how the time-series curve above could be included in a boundary condition database. A wildcard is used for ~~Part~~“Column D2” of the pathname (date range). Note that the pathname must start with a forward slash (/). <tt>Name, Source, Column 1, Column 2, Add Col 1, Mult Col 2, Add Col 2, Column 3, Column 4▼ FC01, EG.dss, , /Example/EG01/FLOW//5Minute/BC/, , , , , </tt>▼ ▲ Name, Source, Column 1, Column 2, Add Col 1, Mult Col 2, Add Col 2, Column 3, Column 4 ▲ FC01, EG.dss, ,/Example/EG01/FLOW/*/5Minute/BC/, , , , , By default, TUFLOW uses the first point in the time-series curve as TUFLOW time-zero. This can be changed using the TCF command “HEC-DSS Start Date” to identify the date/time that should be used for time-zero. The date should be in the isodate format: yyyy-mm-dd hh:mm:ss, where the time portions are optional.<br> :<font color="blue"><tt>HEC-DSS Start Date </tt></font> <font color="red"><tt>== </tt></font> <tt>2022-01-01</tt> <br>

HEC-RAS to TUFLOW: Difference between revisions