Dear Support,
First, $OCSSWROOT/benchmark/seadas_benchmark.bash ran successfully.
But it failed with any recent L0 files:
$ modis_L1A -o out.L1A MOD00.A2023087.1520_1.PDS
MODIS L1A version 6.0.6, built Nov 28 2022 12:23:38
modis_l1a: ERROR: MODIS L1A processing failed.
Please examine the LogStatus and LogUser files for more information.
Following is the content of LogStatus.out.L1A
****************************************
BEGIN_PGE: Tue Mar 28 22:50:47 2023
MSG_TAG: 11
FILE: /work/o/oo_processing/tmp/junk3/LogStatus.out.L1A
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). !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
level1a():MODIS_U_L1A_BEGIN:286763081
The L1A process started: L1A version 6.0.6 built on Nov 28 2022, at 12:23:38
PGS_PC_GetPCSDataRetrieveData():PGSPC_W_NO_CONFIG_VALUE:76803
No configuration value exists for logical
PGS_PC_GetPCSData():PGSPC_W_NO_CONFIG_VALUE:76803
No configuration value exists for logical
PGS_PC_GetConfigData():PGSPC_W_NO_CONFIG_FOR_ID:76810
The Product ID does not contain a configuration value. Problematic ID is 599004.
get_pcf_config_data():MODIS_E_GETCONFIG_FAILED:286764563
A non-success message was returned while trying to retrieve data from the PCF file: The MOD_PR01 LUT RCS Revision number could not be retrieved
initialize_level1a():MODIS_F_NO_PCF_CONFIG_DATA:286765122
All configuration data could not be retrieved from the PCF file: error occured in trying to get PCF config data values Granule Length or Scan Rate
level1a():MODIS_E_INITIALIZATION_FAILED:286764566
Program failed initialization: Routine initialize_level1a failed
PGS_IO_L0_ManageTable():PGSIO_E_L0_UNUSED_TABLE_ENTRY:11825
File table lookup index points to unused table entry
PGS_IO_L0_Close():PGSIO_E_L0_VIRTUAL_DS_NOT_OPEN:11806
Virtual data set is not open
close_processing_run():MODIS_E_PGS_IO_LO_CLOSE:286764589
PGS_IO_L0_Close failed to close the L0 file successfully: Unable to close the L0 file successfully LUN: 0
level1a():MODIS_U_L1A_END:286763082
The L1A process ended: L1A return code = 1
Please advice!
Yuyuan
V2023.0 -- MODIS L1A processing failed
-
- Posts: 278
- Joined: Wed Apr 06, 2005 12:11 pm America/New_York
-
- Subject Matter Expert
- Posts: 509
- Joined: Tue Feb 09, 2021 5:42 pm America/New_York
- Been thanked: 1 time
Re: V2023.0 -- MODIS L1A processing failed
Yes, V2023.0 has issues with both modis_L1A and modis_GEO. Please use V2022.3
-
- User Services
- Posts: 1412
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 1 time
Re: V2023.0 -- MODIS L1A processing failed
The issue is that the LUT updates required for the update MODIS L1A and GEO codes failed to be included in the V2023.0 release. This will be corrected soon (and you'll see V2023.1). The proper LUTs are available in the T2023.7 test tag.
Sean
Sean