MD cbind: correction to description of mesh point mapping #2791
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RyanDavies19
approved these changes
May 1, 2025
andrew-platt
force-pushed
the
b/MD_C_meshpointdocs
branch
from
db87f7d to
2dbf91d
Compare
RyanDavies19
approved these changes
May 5, 2025
This was referenced Jun 16, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Merge after #2735
Feature or improvement description
The documentation in
MoorDyn_c-binding.f90about the input/output mesh was incorrect. Only a single mesh point can be passed across the interface, but it is able to rigidly map over to multiple MoorDyn mesh pointsRelated issue, if one exists
Question raised in #2735 review: #2735 (comment)