SMS:ADCIRC Interface Changes for SMS 13.1
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 like they were in SMS 12.3 and earlier. 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 boundary conditions must be applied to the ADCIRC simulation before tidal forcing can be applied to the simulation.
- 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.
- The workflow for adding flow forcing attributes has changed.
An updated workflow for creating an ADCIRC project can be found in the article ADCIRC Project Workflow.
It should be noted that once an ADCIRC project has been imported into SMS 13.1, it cannot be reverted to an earlier version of SMS.
New Boundary Conditions Workflow
Creating ADCIRC boundary conditions use the following workflow:
Expand1. Create an ADCIRC Boundary Conditions map coverage.
Expand2. Create the mainland arc.
Expand3. Define the domain.
Expand4. Assign ocean arc attributes.
Expand5. Assign other boundary condition attributes. (optional)
After the boundary conditions arcs have been created and defined on the ADCIRC boundary condition coverage, the coverage and the mesh are linked to the ADCIRC simulation in the Project Explorer.
New Tidal Forcing Workflow
Tidal constituents are now defined on a simulation that is linked to the ADCIRC simulation. This is done by doing the following:
Expand1. Turn on tidal forcing.
Expand2. Define tidal constituents.
After the tidal constituents have been defined, the tidal constituent simulation must be applied to the ADCIRC simulation before the model run.
New Flow Forcing Workflow
To add flow forcing to an ADCIRC project in SMS 13.1 or later, do the following:
- In the Project Explorer, right-click on the ADCIRC boundary conditions coverage and select Forcing Options.
- Turn on Flow forcing in the Boundary Conditions Forcing Options dialog.
- Define flow forcing parameters.
Importing Native ADCIRC Model
Migrating SMS 13.0 ADCIRC Projects into SMS 13.1 or later is not supported. When importing an ADCIRC 13.0 project into SMS 13.1 or later, the following message will appear:
SMS 13.0 ADCIRC projects are not supported in this version of SMS. Read the native ADCIRC input files to load this ADCIRC model(s). See https://www.xmswiki.com/wiki/SMS:ADCIRC_Interface_Changes_for_SMS_13.1#Importing_Native_ADCIRC_Model for more details.
Therefore, the native ADCIRC files will need to be imported for ADCIRC projects that were created in SMS 13.0 and are being migrated to SMS 13.1 or later. When importing the native ADCIRC files, pay attention to the following:
- Reading a fort.15 creates a new simulation (and possibly a mapped tidal component) and reads all data in the fort.14, fort.13, or fort.22 files in the same folder.
- Reading a fort.14 independently creates a new simulation, mesh, and mapped boundary condition component
- Reading a fort.13 independently just creates the nodal attribute datasets.
Related Topics
[hide] 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 |