Minor bugfix: ED blade file parsing (no PichAxis column), AD warnings #2332
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ready to merge
Feature or improvement description
PR #2267 allows skipping the
PitchAxiscolumn in ED blade file. However, there was a logic error that prevented that feature from working.If a new format AeroDyn input file was used that did not have the nodal outputs section, the
printNewOldInputsroutine was being called anyhow to print out the new inputs. This has been correctedRelated issue, if one exists
Impacted areas of the software
ED file parsing, and AD messages only.
Additional supporting information
Thanks to @RBergua for catching these issues.
Test results, if applicable
No changes