SMS:CMS-Flow Simulation: Difference between revisions
No edit summary |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
*A CMS-Flow [[SMS:CMS-Flow_Coverages#Boundary_Conditions|Boundary Conditions]] coverage | *A CMS-Flow [[SMS:CMS-Flow_Coverages#Boundary_Conditions|Boundary Conditions]] coverage | ||
*A CMS-Flow [[SMS:CMS-Flow_Coverages#Save_Points|Save Points]] coverage (optional) | *A CMS-Flow [[SMS:CMS-Flow_Coverages#Save_Points|Save Points]] coverage (optional) | ||
*An [[SMS:Generic Coverages|Activity Classification]] coverage | *An [[SMS:Generic Coverages|Activity Classification]] coverage (optional, but recommended to speed up the model run) | ||
A simulation cannot include multiple coverages of the same type. So if building multiple boundary condition coverages, only one of the boundary condition coverages can be included in the simulation. Coverages can be merged if needed. | A simulation cannot include multiple coverages of the same type. So if building multiple boundary condition coverages, only one of the boundary condition coverages can be included in the simulation. Coverages can be merged if needed. | ||
==Linking Components== | ==Linking Components== | ||
After a simulation has been created, components may be added to the simulation. Components are usually added by clicking on the component item in the Project Explorer and dragging the item under the CMS-Flow simulation. A link is then created between the component and the simulation. If the component is updated, it is updated automatically in all simulations that are linked to it. | After a simulation has been created, components may be added to the simulation. Components are usually added by clicking on the component item in the Project Explorer and dragging the item under the CMS-Flow simulation. A link ([[File:Coverage Link.svg|16 px]] or [[File:Quadtree Link.svg|16 px]]) is then created between the component and the simulation. If the component is updated, it is updated automatically in all simulations that are linked to it. | ||
Components can also be added to a simulation by right-clicking on the component in the | Components can also be added to a simulation by right-clicking on the component in the Project Explorer and selecting the simulation name in the ''Link To'' submenu. Simularly, components can be unlinked from a simualtion by right-clicking on the component and selecting the simulation name in the ''Unlink From'' submenu. The ''Link To'' and ''Unlink From'' submenus become available once a simulation has been created. | ||
==CMS-Flow Model Check== | ==CMS-Flow Model Check== | ||
| Line 28: | Line 28: | ||
* Make sure model control has been set up correctly (i.e. if a tidal boundary exists, make sure that tidal constituents have been defined to force with). | * Make sure model control has been set up correctly (i.e. if a tidal boundary exists, make sure that tidal constituents have been defined to force with). | ||
* Ensure that CMS-Flow has been set up to output the specific data for any existing observation station and that observation stations exist for any specified output data. Observation is not required to run CMS-Flow so this is a reminder that something may have been intended but forgotten. | * Ensure that CMS-Flow has been set up to output the specific data for any existing observation station and that observation stations exist for any specified output data. Observation is not required to run CMS-Flow so this is a reminder that something may have been intended but forgotten. | ||
* Ensure that no invalid hard bottom specifications exist in the grid. An invalid specification may be created, for example, by setting an infeasible hard bottom scalar value in the | * Ensure that no invalid hard bottom specifications exist in the grid. An invalid specification may be created, for example, by setting an infeasible hard bottom scalar value in the Edit Window or adjusted the grid's geometry without updating the hard bottom. | ||
The model check is not all inclusive. Just because a model passes the model check does not guarantee the model will run and produce viable solutions. | The model check is not all inclusive. Just because a model passes the model check does not guarantee the model will run and produce viable solutions. | ||
==Running | ==Running a CMS-Flow Simulation== | ||
After all components have been added to the simulation and the model parameters have been established, the simulation can be run. This is done by right-clicking on the simulation and choosing the '''Launch CMS-Flow''' command or the '''Save, Export, and Launch CMS-Flow''' command. | After all components have been added to the simulation and the model parameters have been established, the simulation can be run. This is done by right-clicking on the simulation and choosing the '''Launch CMS-Flow''' command or the '''Save, Export, and Launch CMS-Flow''' command. | ||
The CMS-Flow Model Wrapper should appear. If there are any errors in the model run, the model wrapper will exit early. The model run can also be exited early by clicking the '''Abort''' button. When the model run is completed, select '''Exit''' to close the model wrapper. | The CMS-Flow Model Wrapper should appear. If there are any errors in the model run, the model wrapper will exit early. The model run can also be exited early by clicking the '''Abort''' button. When the model run is completed, select '''Exit''' to close the model wrapper. | ||
The ''Load solution'' option in the model wrapper is selected by default. This option will load the solution from the CMS-Flow model run in to SMS as soon as the model run is complete. | The ''Load solution'' option in the model wrapper is selected by default. This option will load the solution from the CMS-Flow model run in to SMS as soon as the model run is complete. | ||
==Related Topics== | ==Related Topics== | ||
| Line 47: | Line 46: | ||
{{Navbox SMS}} | {{Navbox SMS}} | ||
[[Category:CMS-Flow]] | [[Category:CMS-Flow|Simulations]] | ||
[[Category:SMS Simulations|CMS-Flow]] | |||
Latest revision as of 19:10, 21 September 2017
CMS-Flow makes use of simulations starting in SMS 12.1 and later. Simulations are useful as multiple simulations can be used in the same project.
Simulations for CMS-Flow are created by right-clicking in the Project Explorer and selecting New Simulation | CMS-Flow. The simulation will appear in the Project Explorer under the "Simulation Data" item.
Right-clicking on the simulation gives access to the CMS-Flow menus, including access to the CMS-Flow Model Control dialog. Each CMS-Flow simulation can have its own parameters based on what is entered into the Model Control. Each simulation can share the same components or use different components or any combination of shared and different components.
CMS-Flow Components
Components for CMS-Flow usually include:
- A quadtree grid
- A CMS-Flow Boundary Conditions coverage
- A CMS-Flow Save Points coverage (optional)
- An Activity Classification coverage (optional, but recommended to speed up the model run)
A simulation cannot include multiple coverages of the same type. So if building multiple boundary condition coverages, only one of the boundary condition coverages can be included in the simulation. Coverages can be merged if needed.
Linking Components
After a simulation has been created, components may be added to the simulation. Components are usually added by clicking on the component item in the Project Explorer and dragging the item under the CMS-Flow simulation. A link (
or 
) is then created between the component and the simulation. If the component is updated, it is updated automatically in all simulations that are linked to it.
Components can also be added to a simulation by right-clicking on the component in the Project Explorer and selecting the simulation name in the Link To submenu. Simularly, components can be unlinked from a simualtion by right-clicking on the component and selecting the simulation name in the Unlink From submenu. The Link To and Unlink From submenus become available once a simulation has been created.
CMS-Flow Model Check
Whenever the using the Model Check command, and just before launching an analysis, SMS performs a check on the model. If conditions are detected that are out of the ordinary or recommended range, warnings are given with suggestions to correct the problem. If serious problems are detected, errors are reported, again with suggestions.
These checks include:
- All water boundaries have boundary conditions specified.
- Cell aspect ratio is no greater than 2.
- Max time step size is suggested according to an internal calculation made within SMS.
- Make sure model control has been set up correctly (i.e. if a tidal boundary exists, make sure that tidal constituents have been defined to force with).
- Ensure that CMS-Flow has been set up to output the specific data for any existing observation station and that observation stations exist for any specified output data. Observation is not required to run CMS-Flow so this is a reminder that something may have been intended but forgotten.
- Ensure that no invalid hard bottom specifications exist in the grid. An invalid specification may be created, for example, by setting an infeasible hard bottom scalar value in the Edit Window or adjusted the grid's geometry without updating the hard bottom.
The model check is not all inclusive. Just because a model passes the model check does not guarantee the model will run and produce viable solutions.
Running a CMS-Flow Simulation
After all components have been added to the simulation and the model parameters have been established, the simulation can be run. This is done by right-clicking on the simulation and choosing the Launch CMS-Flow command or the Save, Export, and Launch CMS-Flow command.
The CMS-Flow Model Wrapper should appear. If there are any errors in the model run, the model wrapper will exit early. The model run can also be exited early by clicking the Abort button. When the model run is completed, select Exit to close the model wrapper.
The Load solution option in the model wrapper is selected by default. This option will load the solution from the CMS-Flow model run in to SMS as soon as the model run is complete.
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 | ||
