-
Notifications
You must be signed in to change notification settings - Fork 7
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
NonConvexHull() call is sucking down the electricity!! #69
Comments
Oh dear. It's also causing a core dump:
|
Best & easiest way is to extract g-ring info.
NonConvexHull probably isn’t too hard to parallelize.
|
I haven’t looked at MOD09, not sure if something specific to ‘05 got into the generic MOD L2 code.
|
Note, for MODIS data we can probably introduce a stride of 10 because of the number of detectors along the track. |
A little help is available with the PR SpatioTemporal/STAREmaster#103 which parallelizes a loop in the MOD05 STARE indexing, but not the NonConvexHull. We should leave this issue open as we should still look at parallelizing STARE and NonConvexHull. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That NonConvexHull() call really gives my CPU a workout! ;-)
Is there an easy way to make that multi-threaded? Because actually I have multiple cores, and the test is running, and one core is pegged at 100% while the rest are mostly idle...
The text was updated successfully, but these errors were encountered: