Set ref wind height to -1 for turboparkgauss.yaml #999
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
Sounds good! Should I hold this PR and wait for that? Or go ahead and merge? |
|
@paulf81 good to merge |
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.
Set ref wind height to -1 for turboparkgauss.yaml
Doing some other work I noticed that among the example inputs turboparkgauss.yaml uses 90.0 instead of -1. This isn't really a bug, but since we often use these example inputs as starters for other turbine models, probably nice if they all use the more generic option. I think this is the only case of this (the multiple turbine input correctly specifies the height since there isn't a single height).