Skip to content

Conversation

@andrew-platt
Copy link
Collaborator

DRAFT not ready for merging

Feature or improvement description

  • Description coming soon

Related issue, if one exists
None

Impacted areas of the software
Updates to following modules and interfaces:

  • AeroDyn_Inflow_C_Binding library
  • MoorDyn_C_Binding library
  • SeaState_C_Binding library
  • pyOpenFAST changes
  • NWTC_Library
    • ability to set CU to a different value for writing to file instead of output to screen (used with LabView)

some other details to fill out here

Additional supporting information

Test results, if applicable
New test case

  • add documentation this

Complete before ready for review

  • add missing documentation above
  • convert wavetank test case to full r-test
    • use scaled down RM1 with simplified MD
  • add LabView example (not as a test)
  • add details about how to use this in docs
  • update visual studio projects
  • MD c-bind
    • VTK placeholders
    • split out pre-init routine
  • HD c-bind add VTK placeholders
    • [ ]

rafmudaf added 30 commits May 20, 2025 14:00
@andrew-platt andrew-platt force-pushed the wavetank3 branch 6 times, most recently from 30367e6 to e159244 Compare December 22, 2025 00:18
Without this approach, errors occur when making the _C_Binding.f90 for static and shared in parallel.
@andrew-platt andrew-platt marked this pull request as ready for review December 22, 2025 16:14
Comment on lines 183 to 208
#--------------------------------------
# Error levels
#--------------------------------------
error_levels: Dict[int, str] = {
0: "None",
1: "Info",
2: "Warning",
3: "Severe Error",
4: "Fatal Error"
}

# Debug output file: When coupled into another code, an array of position/orientation,
# velocities, and accelerations are passed in, and an array of Forces + Moments is
# returned. For debugging, it may be useful to dump all off this to a file.
debug_output_file: str = "DbgOutputs.out"
debug_outputs: int = 1 # For checking the interface, set this to 1

#--------------------------------------
# Constants
#--------------------------------------
# NOTE: The length of the error message in Fortran is determined by the
# ErrMsgLen variable in the NWTC_Base.f90 file. If ErrMsgLen is modified,
# the corresponding size here must also be updated to match.
ERROR_MESSAGE_LENGTH: int = 8197
DEFAULT_STRING_LENGTH: int = 1025

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these included in the OpenFASTInterfaceType?

Copy link
Collaborator Author

@andrew-platt andrew-platt Dec 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch.
There is an inconsistency in the names used that I had not sorted out (ERROR_MSG_C_LEN in OpenFASTInterfaceType vs. ERROR_MESSAGE_LENGTH). Several of the other python libraries have this inconsistency.
I'll make an attempt to revise this, but it might take a bit of time. Alternatively, we can add it as an action item on the 5.0.0 release.

Initial commit, it doesn't work yet.  Restructuring required.
There is a huge initial transient that needs addressing at some point
copy of files from MHK_RM1_Floating_Tank-scaled case -- GH actions doesn't have this case copied in the integrations test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants