Fixing datatype of value in WindData objects #872
Merged
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.
Bug fix: setting value as a float in WindData objects and removing a warning when computing AVP
This PR fixes two small issues related to the WindData value array.
assign_value_piecewise_linear
method would also be integers. Since we want values to be able to take non-integer values,dtype=float
is now added when assigning values.get_farm_AVP
in floris_model.py, a warning about values being treated as 1 was printed when the WindData attribute in the floris model was a TimeSeries object. However, TimeSeries objects have a value array, so this warning isn't necessary. Now it only prints the warning when the floris model has no WindData attribute.