fase 3: Evaluación integral

There are several text files in the URBS software modelling tool for catchment definition, rainfall input and output results. These files offer a way that can be used to integrate the URBS model with Windows interfaces in DSSFCMR. Details of the integration with the URBS model in DSSFCMR are given in Chapters 4 and 5. Only the structure of URBS model input and output files used in DSSFCMR are described below to help understand the integration of URBS with DSSFCMR through these files.

Figure 3.1 shows an example of the Catchment Definition file used in the URBS model. Note that although the contents of the file are given in two columns in Figure 3.1, it is a one- column file. The default value of parameter n (of channel roughness) is used in Figure 3.1. Most lines in the file are self-explained and therefore they are not described below. However, the other lines are explained as follows:

• mr0001: the file name of the Catchment Definition file with the extension urb. In this case, this catchment file is mr0001.urb stored in the URBS home directory (e.g.

c:\dssfcmr\ modelbase\urbs\ mr0001.urb).

• Model: BASIC: the basic method of routing is used.

• USES: L,U,F : The catchment variables L, U and F in Equation (3-1) are used in the model.

• alpha and m : parameters α and m in Equation (3-1).

• Factor : parameter f in Equation (3-1)..

• Rain # i means only the rainfall in subcatchment i is routed through the conceptual storage using Equation (3-1) and computes the hydrograph at the downstream end of the

reach of this subcatchment. It is used when there is no subcatchment upstream of subcatchment i.

mr0001 MODEL:BASIC USES:L,U,F

DEFAULT PARAMETERS: alpha= 1.2 m= 0.8 18 SUB-CATCHMENTS OF AREA : 114.4 86.9 67.5 81.7 62.5 75.6 70 64.9 65.5 168 44.9 15 80 68 124.1 75.9 44.9 54.3 FACTOR=0.5 RAIN # 1 L=11.7 U=0 F=0 FACTOR=1

ADD RAIN # 2 L=16 U=0 F=0 FACTOR=1

ADD RAIN # 3 L=18.9 U=0 F=0 FACTOR=1

ADD RAIN # 4 L=26.4 U=0 F=0 STORE.

FACTOR=0.5

RAIN # 5 L=7 U=0 F=0 FACTOR=0.5

ADD RAIN # 6 L=3 U=0 F=0 GET.

ROUTE L=14.1 U=0 F=0 FACTOR=1

ADD RAIN # 7 L=27.35 U=0 F=0 STORE. FACTOR=0.5 RAIN # 8 L=6.55 U=0 F=0 GET. ROUTE L=12.65 U=0 F=0 FACTOR=1

ADD RAIN # 9 L=15.2 U=0 F=0 STORE.

FACTOR=0.5

RAIN # 10 L=14.9 U=0 F=0 FACTOR=0.5

ADD RAIN # 11 L=14.4 U=0 F=0 GET.

ROUTE L=3.3 U=0 F=0 FACTOR=1

ADD RAIN # 12 L=5.1 U=0 F=0 STORE.

FACTOR=0.5

RAIN # 13 L=9.4 U=0 F=0 DAM ROUTE VBF=24670 NUMBER = 14 24670 0 24820 2.63 25305 16 25870 39.47 26470 67.89 27070 99.47 27625 131.58 27950 160.53 28170 173.68 28710 226 29250 268 29790 315 30010 343 30350 375 FACTOR=1

ADD RAIN # 14 L=10.5 U=0 F=0 STORE. FACTOR=0.5 RAIN # 15 L=15.8 U=0 F=0 GET. ROUTE L=11.1 U=0 F=0 FACTOR=1

ADD RAIN # 16 L=11.35 U=0 F=0 FACTOR=1

ADD RAIN # 17 L=18.35 U=0 F=0 GET.

ROUTE L=12 U=0 F=0 FACTOR=1

ADD RAIN # 18 L=16 U=0 F=0 PRINT. Keilor

BASEFLOW = 0

END OF CATCHMENT DATA.

5 PLUVIOGRAPHS: LOCATION. Romsey 3 SUB-CATCHMENTS: 1 2 3 LOCATION. Bulla 4 SUB-CATCHMENTS: 11 12 17 18 LOCATION. Macedon 3 SUB-CATCHMENTS: 13 14 15 LOCATION. Dguim 4 SUB-CATCHMENTS: 4 5 6 7 LOCATION. Cfield 4 SUB-CATCHMENTS: 8 9 10 16 END OF PLUVIOGRAPH DATA.

3 GAUGING STATIONS: LOCATION. bulla LOCATION. sunbury LOCATION. keilor

END OF GAUGING STATION DATA. 0 RATING CURVE:

END OF RATING CURVE DATA.

Figure 3.1 Example of a Catchment Definition File

• ADD Rain # i: It is similar to Rain # i, but is used when there is a subcatchment upstream of the subcatchment i. The rainfall of the subcatchment i is added to the runoff

hydrograph of the upstream subcatchment and routed using Equation (3-1) to provide the outflow hydrograph at the downstream end of the reach of this subcatchment.

• STORE: the hydrograph before this command is stored and no further routing is done to this hydrograph until a GET command is executed. This is used at river / tributary confluences.

• GET: the previously stored hydrograph is accessed and is added to the current hydrograph. This gives the hydrograph just below the river / tributary confluences.

• ROUTE: the current hydrograph is routed through a conceptual storage along the specified reach using Equation (3-1). This action is used when there are no additional rainfall inputs.

• DAM ROUTE VBF=24670 NUMBER = 14: this line and the next 14 lines dictated by

NUMBER, indicates that there is a dam, and the current hydrograph is routed through this dam. VBF value (i.e. is 24670 in this case) is the storage volume above which outflow from the dam occurs. The NUMBER 14 indicates 14 pairs of storage-discharge curve values used for this dam, which are given the next 14 lines.

• PRINT. Keilor: the hydrograph at a specified location (in this case, Keilor) is written to an output file. This location is used as the output filename.

• BASEFLOW = 0: it sets the baseflow in cumecs ( in this case, zero baseflow).

• 5 PLUVIOGRAPHS: LOCATION. Romsey

3 SUB-CATCHMENTS: 1 2 3

These commands define the pluviograph sites until the line END OF PLUVIOGRAPH DATA.

The first line indicates that 5 pluviometers are used for estimating the hydrograph. The second line LOCATION. Romsey shows Romsey as one of the 5 pluviometers. The third line shows that 3 subcatchments use the rainfall data in Romsey for rainfall-runoff routing. The next line shows the subcatchments, which use Romsey rainfall data, are subcatchments 1, 2 and 3.

For each pluviometer, similar information is provided.

• 3 GAUGING STATIONS: LOCATION. bulla

LOCATION. sunbury LOCATION. keilor

These lines define the gauging stations until the line END OF GAUGING STATION DATA. The gauging stations can be used to store recorded data for calibrating a model. The first line indicates that 3 gauging stations are used for this application. The next line LOCATION. bulla indicates that one of the gauging stations is bulla. The other lines are similar.

• 0 RATING CURVE:

END OF RATING CURVE DATA.

These lines define the Rating Curves until the line END OF RATING CURVE DATA. In this application, no rating curves are used.

Figure 3.2 shows an example of a rainfall file used in the URBS model. This file describes the pluviograph stations used in the application and rainfall on the subcatchments for the storm event. The items in the file are described below:

10/14/1983 PLUVIOGRAPHS FORECAST RUN

TIME INCREMENT: 1 HOURS RUN DURATION: 50 HOURS

OURS STORM DURATION: 38 H PLUVIOGRAPH. Romsey PLUVIOGRAPH. Bulla n PLUVIOGRAPH. Macedo PLUVIOGRAPH. Dguim PLUVIOGRAPH. Cfield RAIN ON SUB-CATCHMENTS: 61 61 61 78.4 78.4 78.4 78.4 83.8 83.8 83.8 76.8 76.8 104 104 76.8 104 83.8 104

LOSS: UNIFORM CONTINUING

Figure 3.2 Example of Rainfall File

• The first line 10/14/1983 PLUVIOGRAPHS is the heading.

• The line FORECAST RUN indicates that the type of run is FORECAST RUN model. This type of run can be used either to calibrate a model using historical rainfall data or to forecast streamflow during a rainfall event. The DESIGN RUN and MATCHING RUN are the other choices of this line.

• The line TIME INCREMENT: 1 HOURS indicates that the time step used in this application is 1 hour, and this time step will be used by the model for calculating and outputting the results.

• The line STORM DURATION: 38 HOURS indicates that 38 hours of pluviometer data will be used for generating the runoff hydrograph (and the data after 38 hours will be ignored). This value should be always less than the value of RUN DURATION.

• PLUVIOGRAPH. Romsey indicates that the pluviometer data at Romsey are used for this application. The pluviometer data are stored in a file called romsey.r for the Romsey pluviometer. Similar line exists for other pluviometers. The data in these pluviometers are used for the subcatchments listed in the Catchment Definition file (Figure 3.1). • RAIN ON SUB-CATCHMENTS: 61 61 61 78.4 78.4 78.4 78.4 83.8 83.8 83.8 104 104 76.8 76.8 76.8 83.8 104 104

These lines show the total rainfall for the storm in the 18 subcatchments defined in the Catchment Definition file.

• LOSS: UNIFORM CONTINUING indicates that the uniform continuing loss model is used for this application.

Figure 3.3 shows an example of the rainfall data file. This file contains data at the Romsey pluviometer for the storm defined in the rainfall file (Figure 3.2). The file is called romsey.r. The items in the file are described below:

Romsey Pluviograph 10 1983 Event

after URBS_TIME) Starting Time: 20 :00:00: (0 seconds or 0 hours

hour ) intervals 38 values at 3600 second ( 1 0 3600 38 0.8 0.4 2.2 1.8 1 0.4 0.4 0.2 0 1.8 2 0.6 2.2 3 4.6 0. 0 0 0 0 0 1.2 3.6 5.6 8.2 7.8 1.6 0 0.4 2 1.2 1.6 2.2 0.2 0.8 0.8 2.6 1.2 0.4

Figure 3.3 Example of a Rainfall Data File

• The first line Romsey Pluviograph is the heading.

• The next 3 lines are comment lines, which describe the data file for user to identify the file.

0.8 0.4 2.2 1.8 1 0.4 0.4 0.2 0 1.8 0.6 2.2 3 4.6 0.2 0 0 0 0 0 1.2 3.6 5.6 8.2 7.8 1.6 0 0.4 2 1.2 0.2 0.8 0.8 1.6 2.2 2.6 1.2 0.4

The first line includes three important parameters, which define the pluviometer data at this station for this storm event. 0 is the time in seconds from the starting time of the URBS run (a parameter called URBS_TIME) to the time when the first pluviometer data item is used; 3600 is the time step in seconds of the pluviometer data; and 38 is the total number of pluviometer data items. The 38 rainfall data items in Romsey are then followed in the next 8 lines (i.e. 5 data items in each line, with last line having 3 data items).

Figure 3.4 shows an example of an output hydrograph data file. In this case, the hydrograph details are shown for Keilor. The output file is Keilor.q. Almost all contents in the file are self-explanatory. The column Calc shows the calculated flow, while the column Recd shows the observed flow data.

An good understanding of the URBS model data input and output format, the data file structure and the contents of the data file is essential for development of an integrated system and user-friendly interfaces, which allow the user effectively to interact with the URBS model to perform calibration and forecasting functions.