Jump to content
GMS, SMS, and WMS User Forum

Renumbering multiple ocean boundaries


Recommended Posts

Please can someone provide insight into renumbering multiple boundaries logically using the ADCIRC unstructured mesh.

Clockwise I have 4 boundaries:

1. An ocean boundary that is renumbered logically [1:106] which will be VARIABLE.

2. A section of a large island (Isle of Wight) classed as "mainland".

3. Another ocean boundary (The Solent) which will be CONSTANT.

4. Then the actual mainland (South coast England.).

For input into SWAN I need to reference [start ,end] node locations of each boundary. Renumbering only renumbers boundary 1 sensibly, leaving ocean boundary 2 and both the mainland boundaries randomly numbered. I would ideally like the numbering to be sequential through all the boundaries, or at least the two oceans.

I have tried merging 1,2, and 3 to create a logical numbering system, but am struggling to "unmerge" the island section.

Any hints/tips/help would be greatly appreciated!



Link to comment
Share on other sites


I am not sure exactly what issue you are talking about. The nodestrings do not require sequential node numbers, you just need to know which nodes make up each nodestring, and SMS saves all this information automatically in the fort.15.

If you renumber nodes from a nodestring, SMS does assign the nodes in that nodestring the intial node IDs, but neither ADCIRC, nor SWAN care about that. We recommend that you use the global node numbering (added in SMS 11.1). Then none of the nodestrings will be numbered with sequential node IDs, but as I said, this is not an issue.

There can be issues with multiple nodestrings connecting end to end. For that situation, you are best off merging the nodestrings into a single nodestring. This requires that the two nodestrings actually share one end point. Select both nodestrings, right click and select merge, and they become one nodestring. If the two nodestrings begin and end at separate nodes, they cannot be merged, but I think ADCIRC will still work for that case because the boundary conditions are actually assigned at the nodes.

If this is not the problem you are encountering, please clarify and we can try again.


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...