Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge dev into MDv2-farm #28

Merged
merged 292 commits into from
Sep 9, 2022
Merged

Conversation

andrew-platt
Copy link

This PR merges the latest release (v3.2.0 -- that is currently being posted) into the MDv2-farm branch.

Once this is completed, we can merge MDv2-farm into OpenFAST/dev for the upcoming 3.3.0 release.

andrew-platt and others added 30 commits December 8, 2021 09:24
Include a more explicit C string length variable
abort_error_level should be greater than 0 so that error_status of 0 doesn’t cause a false error
Rather than aborting the process completely
This is not a Python problem, but its a human eyes problem.
First call FAST_End to deallocate internal arrays and then call FAST_DeallocateTurbines to free up the Turbine array
Removes the requirement to pass TMax and InitInpAry since passing TMax overrides the input file value. This commit preserves this functionality, but makes it optional. The system TMax is also now returned so that calling-codes can determine how many time steps to loop over.
NOTE: this may break any codes using FAST_Library.h as that header does not support the optional arguments to FAST_Sizes
This is currently used during the linearization simulations with CalcSteady enabled. After do NLinTimes steps, the simluation should simply end.
This is currently already handled in FAST_Prog, and this commits adds the same behavior in FAST_Library
# Conflicts:
#	glue-codes/python/OpenFAST.py
Storing the error status on the class was causing it to be overwritting when doing the deinitialization routines. The error would be caught, but it would then report back Error 0: <empty string>.
This was checking for an error in the openfastlib but `fatal_error` is a function not an attribute so the if-statement was evaluating to True. In any case, the errors should be handled in the library.
Adds more of the exising OpenFAST regression tests. Only the tests that have dt and dt_out matching are compatible. The FAST_Library outputs values at each call to FAST_Update, but the output files from FAST_Prog are written at dt_out intervals. The Python interface would have to parse dt_out and export files similarly to match the existing regression test baselines.
andrew-platt and others added 29 commits August 24, 2022 12:53
…-rtest

r-test: Remove -m64 in CMAKE_Fortran_FLAG from r-test
Improvements to regression test python scripts
Seg Fault due to hub model and external inflow
AeroAcoustics: fix BL-thickness for heavily-tripped airfoil
…InputLine

HD: increase max length of line read from kinematics files
…OpenFAST tests that were removed.

- 5MW_ITIBarge_DLL_WTurb_WavesIrr_py
- hd_5MW_ITIBarge_DLL_WTurb_WavesIrr
- hd_5MW_OC4Jckt_DLL_WTurb_WavesIrr_MGrowth
This will help a bit in minimizing a race condition during test running. See comments in PR OpenFAST#1199
Use dt_out when storing OpenFAST outputs in Python interface
If a turbine is using SubDyn, the shared moorings connection will be to the platform reference point and not the SubDyn structure.  This can lead to some incorrect behaviour if the mooring connections need to be at points on a flexible platform.
Reg-test scripts modification to help avoid race condition and cleanup of caselist
Small improvements for -VTKLin visualization outputs
@mattEhall mattEhall merged commit 679d850 into mattEhall:MDv2-farm Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.