Bug report: MoorDyn Initialization Output to Command Line

[Ian-Ammerman]

When running OpenFAST by calling from Matlab, the MoorDyn initialization outputs all on one line, causing the output to be truncated and further status messages to not be displayed. Experienced when running released compiled version:

OpenFAST-v4.0.2
Compile Info:

• Compiler: Intel(R) Fortran Compiler 2021
• Architecture: 64 bit
• Precision: single
• OpenMP: No
• Date: Feb 11 2025
• Time: 13:30:00
  Execution Info:
• Date: 02/27/2025
• Time: 18:43:02-0500

Matlab command line displays the following after ~ 30 seconds of MoorDyn initialization:

FairTen 1: 1.59282E+06, 1.57859E+06, 1.55966E+06 t=26.2 FairTen 1: 1.60080E+06, 1.59282E+06, 1.57859E+06 t=26.3 FairTen 1: 1.60337E+06, 1.60080E+06, 1.59282E+06 t=26.4 FairTen 1: 1.60387E+06, 1.60337E+06, 1.60080E+06 t=26.5 FairTen 1: 1.60672E+06, 1.60387E+06, 1.60337E+06 t=26.6 FairTen 1: 1.61533E+06, 1.60672E+06, 1.60387E+06 ... Output truncated. Text exceeds maximum line length for Command Window display.

[RyanDavies19]

@Ian-Ammerman,

Thanks for pointing this out. Matlab is annoying with messages sent to the command line, we've had to deal with this on the MoorDyn-C code that's coupled with WEC-Sim. Bug fix coming soon.

In the meantime, if you're looking for MD status messages, using the 2 writeLog flag in the MoorDyn options list will create a log file of all the outputs sent to the command line and more.