Ansys|91国内精品视频|Matlab|91国内精品久久久|R语言培训课程班-91国内精品久久-曙海培训深圳成都南京苏州杭州

      ☆ 1、如有部分內容理解不透或消化不好，可免費在以后培訓班中重聽；
      ☆ 2、在課程結束之后,授課老師會留給學員手機和E-mail,免費提供半年的課程技術支持，以便保證培訓后的繼續消化；
      ☆3、合格的學員可享受免費推薦就業機會。
      ☆4、合格學員免費頒發相關工程師等資格證書，提升您的職業資質。

• QHM 軟件是基于Windows系統的水域連續流量和質量模擬模型，主要針對水域管理和雨水設計。
• QHM is a Windows-based continuous watershed quantity and quality simulation model intended for watershed management and stormwater design. The program can also be used as an effective teaching tool. Most applications have been watershed analysis usually related to selection and sizing of stormwater BMPs, particularly, flow control and treatment ponds. QHM offers an important planning and design tool to watershed managers and designers of stormwater quantity and quality control systems.
• QHM is capable of continuous simulation of:
• Surface runoff and base flow
• Detention pond routing
• Reservoir routing
• Soil freeze-thaw
• Snowmelt and snow removal/disposal
• Evaporation and evapotranspiration
• Pollutant generation and routing
• Stream erosion potential
• QHM is capable of continuous simulation of:
• Surface runoff and base flow
• Detention pond routing
• Reservoir routing
• Soil freeze-thaw
• Snowmelt and snow removal/disposal
• Evaporation and evapotranspiration
• Pollutant generation and routing
• Stream erosion potential
• QHM simulation can represent a period of indefinite length (limited only by available disk space). The model can be used on a discrete event or multi-event continuous basis.
• QHM Constituents
• Constituents that can be simulated are: stormwater runoff (flow rate and volume) and, optionally, one or any combination of: one pollutant exhibiting first-order decay or characteristics simulated using a rating curve; sediments (in up to five size fractions) characterized by discrete particle settling; and instream erosion indices based on cumulative excess boundary shear stress.
• Appropriate flow and pollutant records obtained elsewhere (monitoring or other simulation models) can be routed through ponds or river reaches by the model.
• QHM System Components
• Components of a physical system that can be simulated are:
• Catchments
• Detention ponds
• Reservoirs
• River reaches which may have junctions and bifurcation (flow splits)
• A system comprised of any combination and any number of the above components can be simulated provided that each component of the system and the system as a whole can be described as "one-way" or "non-feedback."
• Looping networks, or ponds where outflow depends on water depth in the receiving channel, are examples of situations which might not be well-represented in this model. A typical application appropriate for QHM would be a dendritic river network with channels adequately represented by uniform flow conditions.
• QHM ORGANIZATION
• When the QHM program opens, the user can select from seven options of which four represent standard Windows utilities. The other three are specific to QHM: HELP, RUN, and UTILITY; these are introduced here and explained in more detail below.
• The HELP menu includes, in addition to Windows Help, the complete contents of the user's manual.
• The RUN menu includes three commands:
• RUN QHM starts a simulation run using information provided under UTILITY/SET RUN OPTIONS; if specified by the user, the options will be displayed before the run commences.
• INPUT INTERFACE, which is described below, allows the user to create a new input file. Some users will prefer to create a new file using the FILE and EDIT commands to modify an existing file.
• PLOT GRAPH is used to select, view, and print a graph previously created using the UTILITY/CREATE GRAPH command.
• UTILITY also includes three commands:
• CONVERT DATA FORMAT changes standard data formats for precipitation, temperature, and flow into other standard formats. It can also be used to ignore meteorological data that is not needed for a simulation run, and to remove from a file, error codes that will not be recognized by QHM.
• CREATE GRAPH FILE will identify files and simulation periods for a graph to be viewed and printed by the RUN/PLOT, GRAPH command.
• SET RUN OPTIONS allows determination of the files to be used in the next simulation run; whether, during a simulation run, the name of the command that is currently being executed will be displayed; and the output to be displayed when a simulation run is complete (this option is not available if the previous one is selected).
• The DEFAULT button will display settings that many users prefer.
• ?
• The QHM program is structured as a series of commands which are summarized in the PROGRAMS COMMAND section herein and described in detail in the user's manual.
• GETTING STARTED WITH QHM
• This section summarizes information that a user must have at hand before using QHM. Appendix A of the user's manual includes three step-by-step exercises that will guide a first-time user through the basic operation of QHM.
• Defining the Problem
• It is assumed that the user has identified the problem that the simulation will address:
• What is to be simulated - flow; quality parameters; stream erosion; snow removal
  Calibration - flow; quality
  System components and configuration - a system schematic; identifying sub-watersheds; stream reaches; ponds; and reservoirs
  QHM Input Data
• ?
• Further details about input data requirements and file formats are provided in the INPUT DATA section of the user's manual. Required data includes:
• Meteorological data as required by the proposed simulation - precipitation file, extension .pre; temperature file, extension .tmp; evaporation data, to be entered in input file
• Calibration data - flow, extension .flo; quality, extension depends on parameter
• Input file formats must be standard formats that are recognized by QHM and must be identified during program setup.
• QHM Output
• In the input file, the user will specify the nature and form of outputs required after a simulation run: each output file is identified in terms of a Series and ID number. The program, in UTILITY/SET RUN OPTIONS, will ask the user to select the name and extension for the output file and to select output options.
• QHM ID and Series Numbers
• An ID number is used by QHM to identify a file that contains a time series of flow data that is generated by the program. ID numbers are assigned by the user to identify a flow series at the outlet of a sub-watershed, watershed, pond, reservoir, or channel. Because output quality data, if generated, will be contained in the same file as the flow data, they will also be identified by the same ID number.
• The maximum number of flow series files that is retained by the program is 24. If a simulation run creates more than 24 flow series, the user must decide which of the previously created files will be overwritten in order to reassign the ID number to another series; the data in the overwritten files will be lost. In many cases this will not matter, e.g., after flows simulated for two sub-watersheds are combined, the individual files may not be of interest.
• If the user wants to retain a record of a flow series before an ID number is reassigned, that series can be recorded by the PRINT SERIES, DUMP PRINT, or DUMP PLOT commands.
• In addition to an ID number, each outflow series is also assigned a Series Number. Series Numbers are not recognized by the program; they are intended to allow the user to keep track of files when many files are generated by a single simulation run.
• If a simulation run does not generate more than 24 flow series, they will all be identified by their ID numbers; in this case Series Numbers, although they must be entered, will be redundant, and dummy values can be used.
• QHM Time Steps
• Input data time steps may be 5, 10, 15, 20, 30 or 60 minutes, or 24 hours, for precipitation; monthly for evaporation; or hourly or daily for flow.
• The program can be instructed to perform calculations based on any specified time step. If the calculation time step is less than the precipitation time step, the program will use the average precipitation value in each calculation time step. If the calculation time step exceeds the precipitation time step, the latter will be used as the calculation time step.
• Time steps for input precipitation data are specified in the START command. Calculation time steps are specified in the GENERATE command. If a flow series not generated by the program is to be provided using the STORE command, the data input time step will be identified under that command. The routing time step for the POND, RESERVOIR, and REACH commands is specified in those commands.
• QHM SAMPLE FILES
• Table 1 lists sample input files that are included with the program, sample data files that are recognized by each input file and indicates the program command that the input file is intended to illustrate. It also indicates the data format of each sample data file.
• TABLE 1 - QHM SAMPLE INPUT FILES
• File Name
• TEST_GEN.INP
• TEST_EVAP.INP
• ?
• TEST_BSFLW.INP
• TEST_RES.INP
• TEST_SPL.INP
• TEST_QUA.INP
• TEST_RCH.INP
• ?
• TEST_SNO.INP
• TEST_SRM.INP
• TEST_ERSN.INP
• TEST_POND.INP
• TEST_BAT.INP
• TEST_EVENT.INP
• Associated Files
• RAIN85.PRE
• RAIN85.PRE
• ?
• RAIN85.PRE
• 2YR.PRE
• CAL65.PRE
• RAIN85.PRE
• 2YR.PRE
• ?
• SNOW.PRE
• SNOW.TMP+SNOW.PRE
• 2YR.PRE
• RAIN90.PRE
• 2YR.PRE
• EVENT10.PRE
• Purpose is to test:
• GENERATE COMMAND
• EVAPORATION IN GENERATE
• COMMAND
• BASE FLOW ALGORITHM
• ROUTE RESERVOIR COMMAND
• SPLIT SERIES COMMAND
• POLLUTION GENERATION
• REACH COMMAND FOR STREAM ROUTING
• WINTER SEASON SIMULATION
• SNOW REMOVAL/DISPOSAL
• INSTREAM EROSION INDEXES
• POND COMMAND
• BATCH POND OPERATION
• FREE FORMAT RAINFALL OPTION
• TABLE 2 - QHM SAMPLE DATA FILES
• File Name
• 2 YR.PRE
• CAL_65.PRE
• RAIN85.PRE
• RAIN90.PRE
• SNOW.PRE
• SNOW.TMP
• FLOW.FLO
• HEC.FLO
• EVENT_10.PRE
• EVENT_15.PRE
• EVENT_30.PRE
• EVENT_5.PRE
• Description
• rainfall data
• rainfall data
• rainfall data
• rainfall data
• winter precipitation data
• temperature data file
• flow sample file
• flow sample file
• rainfall data
• rainfall data
• rainfall data
• rainfall data
• Data Period
• 81-06-10 - 81-06-30
• 65-05-01 - 66-04-01
• 85-02-01 - 85-12-31
• 90-06-01 - 90-10-29
• 70-11-02 - 71-05-04
• 83-01-03 - 87-04-10
• 70-11-01 - 71-05-04
• 92-05-30 - 92-06-30
• 92-05-30 - 92-06-30
• 97-08-07 - 97-08-09
• 97-08-07 - 97-08-09
• 97-08-07 - 97-08-09
• 97-08-07 - 97-08-09
• Data Format
• AES Hourly
• AES Hourly
• HEC Hourly
• HEC Hourly
• AES Hourly
• AES Hourly
• AES Hourly
• IWD Hourly
• HEC Hourly
• 10min. file
• 15min. file
• 30min. file
• 5min. file