Closed oceancolorcoder closed 4 months ago
I can pick up processing after that file, but encounter the same error again at file ...20220719_100000...
I think this is not linked to the BRDF code, but more to Py6S. This is cases where py6s model are all NaN. Is this an error of py6s or is it specific cases where the py6s model is not applicable, I am not sure yet ?
The problem in the PIU.py MC run is in HyperOCR.FRM at L2016 calculating sample_data5. Clearly those all-NaNs cascade down to produce errors in the rest of L2, including BRDF (where it crashes).
The problem does stem from failed 6S model at L1B resulting in all NaNs in the model AND in Es. Also, the crashing at BRDF was fixed with a recent commit from JIG. Closing this issue and opening a new one.
While batch-reprocessing pySAS data beginning with FICE22, I encountered an odd new error in FRM processing.
In the Full-FRM regime I have successfully batched the entire FICE22 cruise (with and without station extraction) for M99MA, M99NN, M99SS, Z17MA, and Z17SS. While running the last configuration, Z17NN, it runs up to …_20220718_090000… with no errors, but the next file, …_20220718_1200000… fails with the error: