-
Notifications
You must be signed in to change notification settings - Fork 169
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
band priority is not optimized in automos #3711
Comments
There were no optimizations added when the initial feature was added. Suggest profiling a large run and identify places to concentrate on. |
This comment has been minimized.
This comment has been minimized.
@victoronline @scsides I missed this in the mission prioritization. Apologies. Is this still an issue that we should add to the mission priority list this sprint? |
Seems reasonable. It is likely unnecessarily slow. |
This is still something we should look into. |
This is still active. |
We weren't able to address the optimization problem this sprint, but we were able to spend some time digging into it. Based on some profiler runs, it looks like the majority of the time is spent in ProcessMosaic::BandPriorityWithNoTracking, which contains a set of 3 nested for loops. It looks like Fx uses a BandCalculator to perform its computations, which is where the optimizations are happening. This issue will likely require a rewrite of the ProcessMosaic::BandPriorityWithNoTracking function to incorporate the cubecalculator. |
@scsides Was this closed in the last support sprint? |
Hello All. I don't know if this was waiting for me or not. I believe we were looking at using an alternate resource stream for work on this by Stuart for LROC. As far as LROC is concerned, this option has been discussed by LROC and is a viable option. |
Any update on this one? Stuart, have you had a chance to look at this one? |
Fixed by #4793 |
ISIS version(s) affected: 3.x and 4.x
Description
Most users use the default "ontop" or "beneath" when making mosaic products with automos. However, there are some cases when band priority is used (i.e. mosaic regions of images such that the emission angle is minimized in the final map product). Using this band option, automos must compare the incoming band to a band in the mosaic. In the current form, this is a slow process and is not optimized. It is actually quicker to compare images in fx and mosaic the output portions later. However, this is not ideal for large datasets and would become a large file management task.
How to reproduce
Compare run times for:
automos priority=ontop ....
automos priority=band ...
Possible Solution
Incorporate optimizations used in other isis functions (i.e. fx) to speed up band comparisons.
Additional context
This issue was discussed with Stuart Sides at the LROC/Diviner team meeting in February 2020.
The text was updated successfully, but these errors were encountered: