-
Notifications
You must be signed in to change notification settings - Fork 156
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
Horizontal cut plane fails with user-specified resolution and bounds #61
Labels
bug
Something isn't working
Comments
Thanks for reporting! Could I just ask which branch? |
develop |
Merged
ok, I submitted a pull request, would you check this: I believe the DF needed one additional sort to avoid this sort of scrambling, also, the bounds should be in meters, this wasn't said anywhere so I added some comments, but probably this could still be much clearer, thanks for reporting the bug!! |
I've approved the PR. Thanks! |
misi9170
pushed a commit
to misi9170/floris
that referenced
this issue
Dec 13, 2023
* initial commit * first pass edit of 01 example * ruff formatting * bugfix * bugfix * Convert to 4d * correct docstrings * fix docstring * convert tests to 4d * back to gch * Update conditions to evaluate block to 4d * fix floris_interface test and add power tests * Add shape test * Update example 04 * Convert 05 * Update 06 to 4d * Update 09 to 4D * Update 18 to 4d * Update 21 to 4d * Update 22 to 4d * convert 24 to 4d * remove wind speed from call to PointsGrid * change PointsGrid to 4d * change call to set_tilt to pass n_findex * Update comment * start fixing * Remove todo * Remove todo * Clean up some comments * More comment clean up --------- Co-authored-by: Rafael M Mudafort <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
Resulting visualization from calling
wfct.visualization.visualize_cut_plane()
To Reproduce
Expected behavior
Manually sorting and plotting the data:
Floris Version
commit 2833cc7
The text was updated successfully, but these errors were encountered: