Earthdata Forum

Since sometime after 2024-12-26, running modis_L1B.py has failed on all MODISA L1B files. Here's what appears in the command line when we run it:

--------------------
modis_L1B.py --del-hkm --del-qkm -o S20241229200500-L1B-MRA-OBPG.hdf S20241229200500-L1A-MRA-OBPG.hdf S20241229200500-GEO-MRA-OBPG.hdf
MODIS Aqua L1B version 6.2.1_obpg, built Aug 16 2019 12:46:19
ERROR: MODIS L1B processing failed.
Please examine the LogStatus and LogUser files for more information.
--------------------

As suggested, looking in LogStatus we find:

--------------------

****************************************
BEGIN_PGE: Mon Dec 30 20:45:11 2024
MSG_TAG: 11
FILE: /scratch/seadas/LogStatus.S20241229200500-L1B-MRA-OBPG.hdf
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.19
****************************************

TDLUT_ReadPiecewiseLinearFunction():MODIS_F_NOK:295817224
LUT associated with "m1" has times out of order.


Read_L1B_SDS_LUT():MODIS_F_NOK:295817224
Call to TDLUT_ReadPiecewiseLinearFunction() failed.


Read_LUT_Tables():MODIS_F_NOK:295817224
Call to Read_L1B_SDS_LUT() failed.
File LUN: 700050
File type: Reflective_Lookup_Tables_file


:MODIS_F_NOK:295817224
Fatal error(NOK) running...MOD_PR02. TIME:Mon Dec 30 20:45:11 2024
Operator Actions:
Contact MCST.

-------------------

I checked and the appropriate LUT files appear to be up do date:

$ cd /marine-services/ocssw/var/modisa/cal/OPER/
$ ls -lrt
.....
-rw-rw-r-- 1 ubuntu ubuntu 14242967 Dec 17 04:10 MYD02_Reflective_LUTs.V6.2.1.103_OC_v4.1.hdf
-rw-rw-r-- 1 ubuntu ubuntu 117389 Dec 17 04:10 MYD02_QA_LUTs.V6.2.1.103_OC_v4.1.hdf
-rw-rw-r-- 1 ubuntu ubuntu 552736 Dec 17 04:10 MYD02_Emissive_LUTs.V6.2.1.103_OC_v4.1.hdf

------------------

Could someone from the ocean biology group please look into the problem? Thank you!

-Andrew L.

I cannot reproduce your issue. We are using the same LUTs operationally.

Here are the md5sums:

24c4093dcf3f38be28aaa4efcdc079d5 MYD02_Reflective_LUTs.V6.2.1.103_OC_v4.1.hdf
5154ebbb44a9d644321d622a01f0f57a MYD02_Emissive_LUTs.V6.2.1.103_OC_v4.1.hdf
13f653c36a7385598bc3af207c77f0b4 MYD02_QA_LUTs.V6.2.1.103_OC_v4.1.hdf

Tommy

Tommy,

Thank you for your reply.

The checksums match, so we definitely have the same files. Interesting.

Are there other conditions that could cause that exception / error?

I looked back in our archives and the last MODISA file we successfully processed from L1A to L2 was for 2024-12-24 21:30 UTC in case that gives us any ideas. There were not any changes to our systems around that time. In fact we have three separate systems processing MODIS L1A data to L2 and they stopped working at the same time.

-Andrew L.

There was an interruption of our refined Aqua attitude and ephemeris from 12/20 to 12/30 that our provider cleared up now. Maybe try reacquiring the ATTEPH data?

Tommy

I'm getting the identical error when attempting to process the MODISA granule from 2025-01-01 20:15:00

Whatever the issue is it is still present. Do you have any further debugging suggestions, please?

I processed A2024364200500.L1A_LAC to L1B without any error. The tag I used is V2024.8

Hello
sorry to re-open, but I experienced exactly the same error, since exactly the same period and I cannot solve solution, following yours answers.
Could you better explain, please?

Thank you very much
Fabrizio

This problem should be fixed in the latest LUTs:
MYD02_Emissive_LUTs.V6.2.1.106_OC_v4.2.hdf
MYD02_QA_LUTs.V6.2.1.106_OC_v4.2.hdf
MYD02_Reflective_LUTs.V6.2.1.106_OC_v4.2.hdf

Hello

thank you for your answer.
I ran "update_luts.py --verbose aqua"  and I checked for the three files indicated.

However, error is still present.

Any possible suggestion?

Thank you very much
Fabrizio

Hello

sorry for re-up

any help/advice??

Thank you in advance