SMS:CMS-Wave Files: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
A CMS-Wave simulation consists of: | |||
* A Cartesian grid which defines the bathymetric depths over the model domain | |||
* A set of spectra that represent the input wave conditions to be modeled | |||
* Model parameters controlling what options should be used in this simulation | |||
* Optional spatially varied input fields over the same domain such as wind datasets, surge (water level) datasets, and current datasets | |||
In order to run the | SMS stores all of this information internally in its own formats. This includes: | ||
* An XMDF (HDF5) file to store the bathymetry and other datasets on the grid | |||
* An XMDF (HDF5) file to store the spectral grids and wave states entering the domain from the boundary | |||
* Model parameters in the project (sms) file. | |||
In order to run the numeric model, the data must be exported into model native file formats. SMS exports these files when instructed to do so from either the CMS-Wave menu or by right clicking on the CMS-Wave grid. SMS includes three commands in either location. These include: | |||
# "Export CMS-Wave Files" - this command creates the native files described below for the simulation. If the data has not been previously saved to establish the name of the simulation, SMS prompts the user for a simulation name. | |||
# "Launch CMS-Wave"- this command uses the saved files to invoke the simulation | |||
# "Save project, export and launch CMS-Wave" - this command, as described saves the SMS project and then replicates the functionality of the other two commands. | |||
The model native files are referenced by a simulation file, which includes all the names of the other files used as input for a simulation, or that will be created by CMS-Wave when it runs. | |||
SMS stores a simulation name associated each CMS-Wave grid loaded into a session. If a new grid is created, the name is blank and SMS will prompt the user for a name when it is needed. | SMS stores a simulation name associated each CMS-Wave grid loaded into a session. If a new grid is created, the name is blank and SMS will prompt the user for a name when it is needed. | ||
If the '''Launch CMS-Wave''' command is issued without having first saved the model native files, SMS will bring up a message indicating that the files must first be saved. | If the '''Launch CMS-Wave''' command is issued without having first saved the model native files, SMS will bring up a message indicating that the files must first be saved. | ||
Revision as of 22:02, 5 September 2013
A CMS-Wave simulation consists of:
- A Cartesian grid which defines the bathymetric depths over the model domain
- A set of spectra that represent the input wave conditions to be modeled
- Model parameters controlling what options should be used in this simulation
- Optional spatially varied input fields over the same domain such as wind datasets, surge (water level) datasets, and current datasets
SMS stores all of this information internally in its own formats. This includes:
- An XMDF (HDF5) file to store the bathymetry and other datasets on the grid
- An XMDF (HDF5) file to store the spectral grids and wave states entering the domain from the boundary
- Model parameters in the project (sms) file.
In order to run the numeric model, the data must be exported into model native file formats. SMS exports these files when instructed to do so from either the CMS-Wave menu or by right clicking on the CMS-Wave grid. SMS includes three commands in either location. These include:
- "Export CMS-Wave Files" - this command creates the native files described below for the simulation. If the data has not been previously saved to establish the name of the simulation, SMS prompts the user for a simulation name.
- "Launch CMS-Wave"- this command uses the saved files to invoke the simulation
- "Save project, export and launch CMS-Wave" - this command, as described saves the SMS project and then replicates the functionality of the other two commands.
The model native files are referenced by a simulation file, which includes all the names of the other files used as input for a simulation, or that will be created by CMS-Wave when it runs.
SMS stores a simulation name associated each CMS-Wave grid loaded into a session. If a new grid is created, the name is blank and SMS will prompt the user for a name when it is needed.
If the Launch CMS-Wave command is issued without having first saved the model native files, SMS will bring up a message indicating that the files must first be saved.
To change the name of the simulation associated with a grid, the user can select the File|Save as... command and select the CMS-Wave simulation option. SMS will then prompt the user for the new simulation name to be associated with the active CMS-Wave grid. We recommend that this option be utilized only after duplicating the CMS-Wave grid, since the link to the old simulation files is lost when the new simulation name is specified.
Input Files:
- Required files
- Optional files
- projname.cur
- projname.eta (uses the same format as the .dep file)
- projname.struct
- projname.fric (uses the same format as the .dep file)
- projname.fref (uses the same format as the .dep file)
- projname.bref (uses the same format as the .dep file)
- Auxilliary files
Output Files
- Spatially varied data (value for each cell)
- Full spectra a selected cells (have the same format as the .eng file)
- projname.obs
- projname.nst
- Additional files
Related Topics
SMS – Surface-water Modeling System | ||
|---|---|---|
| Modules: | 1D Grid • Cartesian Grid • Curvilinear Grid • GIS • Map • Mesh • Particle • Quadtree • Raster • Scatter • UGrid |  |
| General Models: | 3D Structure • FVCOM • Generic • PTM | |
| Coastal Models: | ADCIRC • BOUSS-2D • CGWAVE • CMS-Flow • CMS-Wave • GenCade • STWAVE • WAM | |
| Riverine/Estuarine Models: | AdH • HEC-RAS • HYDRO AS-2D • RMA2 • RMA4 • SRH-2D • TUFLOW • TUFLOW FV | |
| Aquaveo • SMS Tutorials • SMS Workflows | ||
