-
Notifications
You must be signed in to change notification settings - Fork 25
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
Slow processing of L2 uncertainties (top priority) #80
Comments
Pathway discussed Sept 20: calculate partial LUT for min/max parameters (e.g., wind, AOT, etc.) impact on difference between M99 and Z17 rather than calculated Z17 for each spectrum or LUTs for all possible parameterizations. |
pySAS, M99, turning off satellite convolution to Aqua reduces timing from to 2 min. The snag is in instrument.rrsHyperUNCFACTORY is quite slow, ~160s per ensemble/xSlice:
… [Repeat for each ensemble]
0.0% of Rrs_HYPER spectra flagged |
Without Aqua convolution takes < 1 minute:
|
…See Issues comments and updated Sample_Data and README for details
Also, while Z17 is apparently not the logjam here, I have so far found that updating Z17 has only increased its size, considering the newly added AOD to 0.5. From 2.47 GB, it goes to 3.28 GB. I can bring it back down to 2.26 GB by truncating AOD of 0 and SZA of 0 (i.e., starting at 0.05 and 10, respectively). Does not seem worth it yet, but will continue to experiment. |
Two issues to address: Z17 uncertainties at L2 are too slow (i.e., processing time is nearly. as long as data collection time). For this we need a LUT for M99 - Z17. The second issue is that the convolutions to satellite bands are excessively slow, making even M99 processing interminable. Setting created to forgo convolution uncertainties until a resolution can be identified. |
One confusing element about the slowness of running Z17 uncertainties is that when zhangWrapper runs Z17 for uncertainty estimates, each run takes much longer than the run of Z17 to do the glint correction: ... |
The LUTs are built, but AR needs to reconcile differences between LUT results and full model runs. |
Issues related to the way in which interpolation is performed - e.g. linear inteprolation applied to things that logarithmic dependence. @raphidoc and @ARamsay17 to coordinate on this. |
@juanchossn @oceancolorcoder @raphidoc the new zhang17 Lookup table can be found on the box: HyperCP Project Team -> Data -> Zhang_LUTs -> Z17_LUT_new.nc I will test on my end. The code to fully utilise the LUT is in PR #308 which is waiting to be merged. |
Ideas to pursue:
Reduce the size of Z17 by confining it to protocol geometries (DA).
Build LUTs in lieu of full calculations for given conditions (AR).
The text was updated successfully, but these errors were encountered: