Page 2 of 2

Re: modis_L1B.py failures (bad LUT data?)

Posted: Wed Feb 26, 2025 2:27 pm America/New_York
by martakonik
Hello everyone,

I haven't found a solution to this problem, and I am experiencing a similar processing issue.
However, I found an additional comment about the Toolkit version in the logs, which I pasted below.

Does anyone know whether Seadas may require a reinstall?

Thank you,
Marta

****************************************
BEGIN_PGE: Wed Feb 26 19:14:02 2025
MSG_TAG: 11
FILE: /opt/AQUA/LogUser.A2025001103000.L1B_LAC
LOGGING: status message logging enabled
TRACE_LEVEL: tracing disabled
PID_LOGGING: disabled
DISABLED_LEVELS: none
DISABLED_SEEDS: none
DISABLED_CODES: none
THREAD-SAFE MODE: disabled
TOOLKIT_VERSION: SCF TK5.2.20
****************************************

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! W A R N I N G !!
!! The Toolkit version found in the PCF does not !!
!! match the current Toolkit version. The PCF in use !!
!! should be replaced with a PCF constructed from the !!
!! template PCF delivered with THIS version of the !!
!! Toolkit (see TOOLKIT_VERSION in banner, above). !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Re: modis_L1B.py failures (bad LUT data?)

Posted: Thu Feb 27, 2025 10:16 am America/New_York
by OB.DAAC - SeanBailey
I can confirm that with the latest code and the current LUTs modis_GEO and modis_L1B work for data in Dec 2024 and Jan 2025 (including the examples mentioned in this thread).

Which version of the OCSSW code are you running? Are you certain you have the latest MODIS LUTs?

Sean