-
Notifications
You must be signed in to change notification settings - Fork 34
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
Optimized Geometry Functions using Numba #1072
Conversation
I still need to finish adjusting all the tests and ensure that everything is passing, but I wanted to quickly updated you on some initial timings.
This was without any parallelization. Since the bounding box for each face can be computed interpedently, my next step will be to parallelize the loop that calls |
ASV BenchmarkingBenchmark Comparison ResultsBenchmarks that have improved:
Benchmarks that have stayed the same:
Benchmarks that have got worse:
|
sounds great! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you remove all face_latlon_bounds usages in this PR?
Please prioritize merging the face_latlon_bounds here. You can set the use_spherical_bounds
by default as false
, but please try to at least keep the implementation in this PR
I did the opposite. I removed the usages of the naive implementation. All constant longitude and constant latitude queries now use the There is no longer a |
Ohh I see. I guess I was misled by those “No implementation warning ” for |
Those are the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work!
Closes #936
Overview
point_within_gca()
extreme_gca_latitude()
gca_gca_intersection()
_point_within_gca_cartesian()
_extreme_gca_latitude_cartesian()
_gca_gca_intersection_cartesian()
pyfma
package.