|
|
(5 intermediate revisions by the same user not shown) |
Line 48: |
Line 48: |
| ===Importing Native ADCIRC Model=== | | ===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: | | 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 {url} for more details. | | 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 individually for ADCIRC projects that were created in SMS 13.0 and being migrated to SMS 13.1 or later. When importing the native ADCIRC files, pay attention to the following: | | 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 fort22 files in the same folder. | | *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 BC component | | *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. | | *Reading a fort.13 independently just creates the nodal attribute datasets. |
|
| |
|
Latest revision as of 23:00, 17 March 2021
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:
1. Create an ADCIRC Boundary Conditions map coverage.
|
- Create a new coverage with the "ADCIRC Boundary Condition" type.
1. Create new coverage from scratch.
|
- Select Map Data in the Project Explorer and use the New Coverage right-click command.
- Use the New Coverage dialog to create a new coverage by selecting the desired coverage type, and naming the coverage.
|
2. Create new coverage from an existing coverage.
|
- Use the Duplicate command on an existing coverage. This will copy any feature objects on the coverage.
- Use the Rename command to give the coverage a new name.
- Change the coverage type.
|
|
2. Create the mainland arc.
|
1. Import an existing mainland arc. (optional)
|
- Use the File | Open command to import a coastline file containing a coastline arc.
- Right-click on the coastline arc using the Select Feature Arc tool and select the Attributes command.
- Define the arc as a mainland arc in the ADCIRC Linear BC dialog.
|
2. Create a feature arc to use as a mainland.
|
1. Use the Create Feature Arc tool to digitize the coastline.
|
1. Create feature arcs, nodes and vertices.
|
- In the Map module, create feature objects in the active coverage.
- Use the Create Feature Arc tool to create arcs in the map coverage.
- Begin creating a new arc by clicking in the Graphics Window at either arc end. If clicking on an existing feature node, vertex or arc, the new arc will snap to that object.
- Double-click or press the Enter key to terminate the arc.
- Use the Create Feature Node tool to create additional nodes alone or to split arcs.
|
2. Modify arcs.
|
- Feature arcs often need to be edited after initial creation.
3. Split arcs.
|
- An existing arc can be split by:
2. Add a node the arc.
|
- Use the Create Feature Node tool to add a node on an arc in order to split it into two arcs.
|
3. Add a new connecting arc.
|
- Use the Create Feature Arc tool to start or end a new arc on an existing arc to split the existing arc into two arcs.
|
|
4. Merge arcs.
|
- Two arcs that share an end node can be merged together.
- Select the shared node using the Select Feature Node tool.
- Right-click on the node and select the Convert to Vertex command to merge the arcs.
- If desired, the Select Feature Vertex tool can be used to select and delete the new vertex.
|
|
|
2. Assign attributes to the mainland arc.
|
- Right-click on the coastline arc using the Select Feature Arc tool and select the Attributes command.
- Define the arc as a mainland arc in the ADCIRC Linear BC dialog.
|
|
|
4. Assign ocean arc attributes.
|
- Right-click on the domain arc using the Select Feature Arc tool and select the Attributes command.
- Define the arc in the ADCIRC Linear BC dialog.
|
5. Assign other boundary condition attributes. (optional)
|
1. Use the Create Feature Arc tool to digitize the boundary condition arc.
|
1. Create feature arcs, nodes and vertices.
|
- In the Map module, create feature objects in the active coverage.
- Use the Create Feature Arc tool to create arcs in the map coverage.
- Begin creating a new arc by clicking in the Graphics Window at either arc end. If clicking on an existing feature node, vertex or arc, the new arc will snap to that object.
- Double-click or press the Enter key to terminate the arc.
- Use the Create Feature Node tool to create additional nodes alone or to split arcs.
|
2. Modify arcs.
|
- Feature arcs often need to be edited after initial creation.
3. Split arcs.
|
- An existing arc can be split by:
2. Add a node the arc.
|
- Use the Create Feature Node tool to add a node on an arc in order to split it into two arcs.
|
3. Add a new connecting arc.
|
- Use the Create Feature Arc tool to start or end a new arc on an existing arc to split the existing arc into two arcs.
|
|
4. Merge arcs.
|
- Two arcs that share an end node can be merged together.
- Select the shared node using the Select Feature Node tool.
- Right-click on the node and select the Convert to Vertex command to merge the arcs.
- If desired, the Select Feature Vertex tool can be used to select and delete the new vertex.
|
|
|
2. Assign attributes to the arc.
|
- Right-click on the boundary condition arc using the Select Feature Arc tool and select the Attributes command.
- Define the arc with the desired boundary condition in the ADCIRC Linear BC dialog.
|
|
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:
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