SMS:ADCIRC Interface Changes for SMS 13.1: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
With the release of SMS 13.1, several changes were made to how ADCIRC interfaces with SMS. Changes to the user interface for ADCIRC include the following: | With the release of SMS 13.1, several changes were made to how ADCIRC interfaces with SMS. Changes to the user interface for ADCIRC include the following: | ||
* Depth bathymetry datasets have been eliminated. Instead of a depth dataset, an elevation dataset is used. The elevation dataset uses negative Z-values to represent depth. | * Depth bathymetry datasets have been eliminated. Instead of a depth dataset, an elevation dataset is used. The elevation dataset uses negative Z-values to represent depth. | ||
* Boundary conditions are no longer assigned to nodestrings directly on the ADCIRC mesh. Instead, boundary condition attributes are assigned to feature arcs on an ADCIRC boundary condition coverage which is then mapped to the ADCIRC mesh. This method allows the arc to be snapped to the mesh which reduces the time needed to create boundary conditions. | * Boundary conditions are no longer assigned to nodestrings directly on the ADCIRC mesh. Instead, boundary condition attributes are assigned to feature arcs on an ADCIRC boundary condition coverage which is then mapped to the ADCIRC mesh. This method allows the arc to be snapped to the mesh which reduces the time needed to create boundary conditions. | ||
* The workflow for adding tidal forcing attributes has changed. Tidal forcing attributes are now created as a separate component that are linked to the ADCIRC simulation. | |||
===New Boundary Conditions Workflow=== | |||
===New Tidal Forcing Workflow=== | |||
{{Navbox SMS}} | {{Navbox SMS}} | ||
Revision as of 15:29, 1 October 2020
 |
This contains information about functionality available starting at SMS version 13.1. The content may not apply to other versions. |
 |
With the release of SMS 13.1, several changes were made to how ADCIRC interfaces with SMS. Changes to the user interface for ADCIRC include the following:
- Depth bathymetry datasets have been eliminated. Instead of a depth dataset, an elevation dataset is used. The elevation dataset uses negative Z-values to represent depth.
- Boundary conditions are no longer assigned to nodestrings directly on the ADCIRC mesh. Instead, boundary condition attributes are assigned to feature arcs on an ADCIRC boundary condition coverage which is then mapped to the ADCIRC mesh. This method allows the arc to be snapped to the mesh which reduces the time needed to create boundary conditions.
- The workflow for adding tidal forcing attributes has changed. Tidal forcing attributes are now created as a separate component that are linked to the ADCIRC simulation.
New Boundary Conditions Workflow
New Tidal Forcing Workflow
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 | ||
