Skip to content

Release v 2.4.0#542

Merged
rafmudaf merged 701 commits intomasterfrom
dev
Sep 14, 2020
Merged

Release v 2.4.0#542
rafmudaf merged 701 commits intomasterfrom
dev

Conversation

@rafmudaf
Copy link
Collaborator

Complete this sentence
THIS PULL REQUEST IS READY TO MERGE

Feature or improvement description
This pull request merges dev into master for a tagged release, v2.4.0. See below for the proposed change log.

Related issue, if one exists
None

Impacted areas of the software
See the proposed change log below.

Test results, if applicable
The baseline results have changed since the last release. See the r-test pull requests for more information.


General

AeroDyn

BeamDyn

ElastoDyn

ExtPtfm

InflowWind

ServoDyn

r-test

andrew-platt and others added 30 commits April 17, 2020 10:03
Documentation update (solver + OutListParameters)
added some quotation marks in case of spaces in path names
added "call" to command line
- remove unused code
- update text formatting
- add version header file to vs-build
- fix some error handling in OpenFOAM.f90
rafmudaf and others added 11 commits July 31, 2020 08:57
Now it is consistent between gfortran and ifort compilers.
Add RANLUX to NWTC Library / HydroDyn
OpenFAST currently uses `DOUBLE_PRECISION` compile-time definition to activate double precision as default during build. This conflicts with the define in the MPI header file (for HPE MPT) when building the C++ API interface. This commit works around this issue by using `OPENFAST_DOUBLE_PRECISION` variable when building with CMake. The code checks for the original `DOUBLE_PRECISION` macro for backward compatibility. The VS build pathway is unaffected.

Fixes #522
* Add error check in FAST_OpFM_Init

* Deallocate Turbine object and let calling routine do the error handling
Copy link
Contributor

@ebranlard ebranlard left a comment

Choose a reason for hiding this comment

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

It's nice to have all these links to the documentation! (they are broken now, but from what I've seen they should point to the right location after the merge).
I checked the API changes in the doc, and I believe they are all there.

@rafmudaf rafmudaf merged commit ff33ca1 into master Sep 14, 2020
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.