Multiple definitions of BOUNDSPEC for more than one side/segment #115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BOUNDSPEC can be used multiple times in a swan input file to define the boundary condition on the given side. Similarly for segments, each segment could have a separate BOUNDSPEC line with input sp2 or TPAR.
This PR has a first example of how to enable the use of the SIDES object, but should be generalised for segments too - TBD
Rasing the PR now and will add additional mods later for segment. Seeking feedback @rafa-guedes