H01.SiamOutput is the SIAM Output Data file. H01.SiamInput is the SIAM Input Data file. SedXS01 is the cross section output file. SedHeadXS01 is the header file for the cross section output. sed is the detailed sediment output file. When sediment transport computations are performed, RAS creates a set of intermediate files:
SedCap01 is the extension for Sediment Transport Capacity data. This file contains flow data, boundary conditions, and sediment data. S01 is the file extension for Sediment Data. c# files might be a good idea for larger models so that RAS can skip the pre-processing step. Sending output files are optional, but will allow the reviewer to avoid rerunning the model on their end. If submitting your final model to a client or a reviewer, you will likely only send the necessary input files. bco01 is the Unsteady Flow Log output file. This file is rewritten each time you change your geometry file. Contains the hydraulic properties tables, rating curves, and family of rating curves for each cross-section, bridge, culvert, storage area, inline and lateral structure. c01 is the Geometric Pre-Processor output file. See the Hot Start post for more guidance.įor Unsteady Flow analysis, these files are categorized as “intermediate,” which means that they are not essential for running a model or viewing results, since they are recreated by RAS during run-time. This option can be switched on by the user in the Output Control Options window. rst is a Restart File (also called a Hot Start File, or Initial Conditions File). This can be switched on in the Unsteady Flow Analysis window. hyd01 is the Detailed Computational Level output file. The messages file is not required to view final results, but can be useful in troubleshooting errors identified by RAS. Records the computational messages that pop up in the computation window. comp_msgs.txt is the Computational Message text file. The run file is created during the model simulation, and is not required to view final results. Contains all of the necessary input data required for the RAS computational engine. r01 is the Run file for steady flow analysis. dss file will be necessary to run the model and should be included in your group of files you send to a reviewer. inflow hydrographs, stage hydrographs, observed data, etc.), then that. If your model links to a dss file for use as input data (e.g.
#Breach and clear deadline runtime error series
This file contains time series data that is viewable by any program that can read dss files (typically HEC software). dss file is automatically generated as an output. This file is written in binary format and can only be read from the user interface. Contains all of the computed results from the associated plan. Note that some of these are only used by RAS as intermediate files during computations. The following screenshot shows the input and output files after the steady flow model has been run. These are all text files and can be directly read and edited in a text editor. Contains a list of the associated input files, and all simulation options. For Quasi-Unsteady Flow (for a sediment analysis).This is where hydrographs and initial conditions are stored, as well as any user-defined flow options. Profile information, flow data and boundary conditions written in this file. Cross-sectional data, hydraulic structures and modeling approach data are stored here. Contains current plan files, units and project description. Differences between Steady and Unsteady files are listed when relevant. If someone asks you to send them your model, these files must be sent, at a minimum. At the very least, you need these input files to run the model. This screenshot is a folder containing the input files generated by RAS after opening and saving one of the installed example projects. Numbers can go as high as "99" and are assigned in the order in which the files were created. Although these examples all use the number "01" in the extension, RAS can have multiple instances of each of these files for a given project (except the. This post will feature a steady flow example project, and will list common HEC-RAS files that you’ll see for Unsteady flow, Sediment Analysis, Water Quality, and Hydraulic Design projects. Keeping track of these files in an organized manner is good practice, especially as your models grow in size and complexity. It is important to know what each of these files does and how they fit into the overall scheme of your project.
All rights reserved.īehind the scenes, HEC-RAS automatically creates a series of input and output files when working with a model.
0 kommentar(er)
