Additional Datafile Formats
  • 21 Sep 2022
  • 1 Minute to read
  • Dark
    Light

Additional Datafile Formats

  • Dark
    Light

This section contains descriptions of important additional file formats that can be utilised within Flood Modeller.

Calibration Datafiles

Calibration (time series) data is stored in a file with extension .cal. The format and an example are provided below. The basic format of the file is repeated for all calibration data points. A hash symbol followed by a comment can be added to the end of any line to aid interpretation of the file. 

General

Line 1 : keyword 'HOURS' or 'SECONDS'

Line 2 : node label

Line 3 : keyword 'STAGE' or 'FLOW'

Line 4 : n1

Line 5 to Line 4+n1 : variable and time 

Line 5+n1 : node label

Line 6+n1 : keyword 'STAGE' or 'FLOW' 

Line 7+n1 : n2

Line 8 to Line 7+n2 : variable and time

where the keyword 'HOURS' or 'SECONDS' denotes the unit of time, the keyword 'STAGE' or 'FLOW' denotes the variable type, and n1, n2, etc. are the number of data point pairs following.

Example

Calibration Datafile Example
HOURS #Calibration for the 16/04/2021 event
RRZ40 #Town Bridge
STAGE
2
12.41     10.00
11.06     15.0
RJH410 #Town gauging station
FLOW
3
140.0     17.0
163.0     32.0
179.0     24.6

Custom Datafile

Custom calibration (long series) data is stored in a file with extension .cus. The format and an example are provided below. The basic format of the file is repeated for all calibration curves. 

General

Line 1 : #COMMENT optional comment line

Line 2 : #CURVE_NAME <curve-string>

Line 3 : #TYPE <type-string>

Line 4 : <label1> <value1>

Line 5 : <label2> <value2>

Line 5 is repeated for all required labels. Lines 1 to 5 can be repeated for other data.

<curve-string> is the title of the data which follows and can be any text

<type-string> is a variable name, such as flow or velocity, which is used to determine if the data are going to be plotted on the current long section. If the <type-string> is set to level then the data will be plotted whenever the long section shows a level type variable (stage, initial conditions, bed, banks, envelope). The string can be upper case, lower case or a mixture of the two.

<label> must exactly match a node label in the model (case sensitive)

An example custom datafile is shown below:

RiverSimulationsimagescustomdatafile.gif


Was this article helpful?