Precipitation-Runoff and Streamflow-Routing Models for the ...

More documents

Recommendations

Info

APPENDIX 13. PROGRAMMING STEPS FOR RUNNING THE SCENARIO GENERATORThe scenario generator executable file is called: willamsg. The control file for the program, whichmust be in the same directory, is called: willam.staThe user activates the scenario generator by typing: willamsgAfter the main menu appears, arrow keys are used to move the cursor to different options. The F2key is then used to activate any option.The current layout for this study uses flow as the only item for display as a ‘scenario.’ However,the user can add new ‘scenarios’ such as different water-quality constituents by adding this data tothe wdmfile and making modifications to the willam.sta file.The flow sites for display may be selected either using ‘Map-basin’ or ‘Location’ submenus.If the ‘Map-basin’ option is selected, a map of the Willamette Basin will appear. The user canselect individual flow sites with the left mouse button. To go back to the menu window, it is necessaryto click on ‘RETURN’ located on the bottom of the map window.If the ‘Location’ option is used, the flow site is selected from a list.After the flow site is selected, the user selects ‘Graph-produce’ submenu to view a hydrograph orflow duration plot. The period of record to be viewed is designated in this submenu under ‘Unitsandtime span of plot’. The ‘Axis-type and scale’ option allows the user to select an arithmetic orlogarithmic scale axis.The file ‘willamsg.sta’ contains the operation settings of the scenario generator. Details about thisfile are provided in the following page. The user can use two versions of the willamsg.sta file. Inthe wdmfile subdirectory there are the files: calibration.sta and network.sta. The calibration.stafile contains 40 flow locations, while the network.sta file contains only the outlet flow locationsfor 12 stream networks. The user can select either file by copying it.cp network.sta willamsg.sta or, cp calibration.sta willamsg.staThe Scenario Generator *.sta fileThe scenario generator *.sta file is a file containing information about the current state of the scenariogenerator. This file is read when the scenario generator is initialized, and it is written justbefore returning to the operating system. The *.sta file contains some general information necessaryto the operation of the scenario generator as well as detailed information about the scenariomapping specifications, and plot specifications. This file is updated when leaving the scenariogenerator; thus any change in these specifications made during a scenario generator run will be“remembered” for subsequent runs. The *.sta file is designed such that, after being set up for aparticular scenario generator, the file should be transparent to the user.186
APPENDIX 13. PROGRAMMING STEPS FOR RUNNING THE SCENARIO GENERATOR—CONTINUEDThe Scenario Generator *.sta file (cont.)The first record in the *.sta file contains the name of the wdm data file associated with this scenariogenerator (FORMAT A64). This file name can be up to 64 characters in length in andshould include the path to the *.wdm file if the *.wdm file does not reside in that directory.Example:/home/hass/ctwsg/bin/truckee.wdmThe second record contains two integer values (FORMAT 2I5). The first value represents the totalnumber of scenarios, and the second value indicates which model this scenario generator will rununder the “simulate” menu option (0-HSPF, 2-DAFLOW).Example:4 0Following the number of scenarios is a series of records containing information about each of thescenarios (FORMAT 4I5,I2,I3,1X,A10). Each of these records contains a scenario identificationnumber, a flag indicating whether this scenario is currently active (1-active, 2-inactive), a series ofintegers specifying line color, line type, symbol type, and fill pattern, and a character string containingthe corresponding scenario name.Example:2 1 0 3 0 0 Scenario 1The next line contains three integer values representing the mapping device (1-screen, 2-printer,3-plotter), the map border specifications (1-USA, 2-latlng, 3-hydro region, 4-state, 5-local), and amap interaction flag (>0-allow user interaction) (FORMAT 3I5).Example:1 2 2The next record specifies minimum and maximum latitude and longitude values as well as a baselongitude value (FORMAT 5F10.1). These values are used in setting the default boundaries onthe map. The base longitude is used to specify the reference point of the map viewer, or in otherwords a location at which map north appears directly vertical on the map projection.Example:38.5 40.5 119.0 120.5 119.0187
Page 1:
Precipitation-Runoff and Streamflow
Page 4 and 5:
U.S. DEPARTMENT OF THE INTERIORBRUC
Page 6 and 7:
Determining Travel Time and Dilutio
Page 8 and 9:
2. Stream-gaging stations used to c
Page 10 and 11:
Page Intentionally Blank
Page 12 and 13:
network-routing models where availa
Page 14 and 15:
made on the main stem at base-flow
Page 16 and 17:
Figure 1. Willamette River Basin, O
Page 18 and 19:
EvapotranspirationINPUTSAirtemperat
Page 20 and 21:
Table 1. Climate stations used to c
Page 22 and 23:
Table 2. Stream-gaging stations use
Page 24 and 25:
Figure 4. Mean annual precipitation
Page 26 and 27:
Major Land Use MapHydrologic Soil G
Page 28 and 29:
0.5 mi 2 , created in the merge of
Page 30 and 31:
Table 6. Geology and soils matrix o
Page 32 and 33:
tion value of the HRU class by the
Page 34 and 35:
Table 8. Selected monthly basinwide
Page 36 and 37:
Figure 9. Location of Precipitation
Page 38 and 39:
Table 11. Statistical analyses of P
Page 40 and 41:
flow can become a significant compo
Page 42 and 43:
diffusion at selected grid interval
Page 44 and 45:
samples were collected at various d
Page 46 and 47:
3,0002,500June 21-30, 1993September
Page 48 and 49:
stream network is shown on figure 1
Page 50 and 51:
122˚30´ 15´122˚00´121˚45´Roc
Page 52 and 53:
123˚22´30´´ 123˚15´ 123˚00´
Page 54 and 55:
123˚00´´ 45´30´122˚15´45˚15
Page 56 and 57:
YamhillRiver123˚45´ 30´ 15´123
Page 58 and 59:
123˚07´30´´ 123˚00´ 45´ 30´
Page 60 and 61:
123˚07´30´´ 123˚00´ 45´ 30´
Page 62 and 63:
44˚15´14166000122˚07´30´´Will
Page 64 and 65:
122˚15´ 122˚00´121˚52´30´´4
Page 66 and 67:
44˚52´30´´45´122˚15´ 122˚00
Page 68 and 69:
observed flow at the Willamette Riv
Page 70 and 71:
DAFLOW model, and peak amplitude is
Page 72 and 73:
20DYE CONCENTRATION, IN MICROGRAMS
Page 74 and 75:
ARC-INFO and Geographic Information
Page 76 and 77:
WILL.WDMData-base file(Observed pre
Page 78 and 79:
WILL.WDMData-base fileSWSTATSFreque
Page 80 and 81:
Jobson, H.E., 1980, Comment on A ne
Page 82 and 83:
Page Intentionally Blank
Page 84 and 85:
APPENDIX 1. STREAM GEOMETRY FOR MAI
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
APPENDIX 2. ARC MACRO LANGUAGE (AML
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
APPENDIX 3. DEFINITIONS OF PARAMETE
Page 124 and 125:
APPENDIX 3. DEFINITIONS OF PARAMETE
Page 126 and 127:
APPENDIX 4. MEASUREMENTS USED TO DE
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
APPENDIX 5. EXAMPLE PRECIPITATION-R
Page 136 and 137:
APPENDIX 5. EXAMPLE PRECIPITATION-R
Page 138 and 139:
APPENDIX 6. DIFFUSION ANALOGY FLOW
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147: APPENDIX 6. DIFFUSION ANALOGY FLOW
Page 148 and 149: APPENDIX 6. DIFFUSION ANALOGY FLOW
Page 150 and 151: APPENDIX 7. PROGRAMMING STEPS TO IN
Page 152 and 153: APPENDIX 8. PROGRAMMING STEPS TO DE
Page 160 and 161: 150Climatemaxtempmintempprecipitati
Page 162 and 163: APPENDIX 10. DIRECTORY TREE AND DES
Page 180 and 181: APPENDIX 11. DIRECTORY TREES AND DE
Page 182 and 183: APPENDIX 11. DIRECTORY TREES AND DE
Page 184 and 185: APPENDIX 12. DIRECTORY FOR will.wdm
Page 198 and 199: APPENDIX 13. PROGRAMMING STEPS FOR
Page 200 and 201: APPENDIX 13. PROGRAMMING STEPS FOR
Page 202 and 203: APPENDIX 14. INPUT FILES FOR BRANCH
show all

Precipitation-Runoff and Streamflow-Routing Models for the ...

Create successful ePaper yourself

Delete template?

Save as template?