The forum is locked.

The Ocean Color Forum has transitioned over to the Earthdata Forum (https://forum.earthdata.nasa.gov/). The information existing below will be retained for historical reference. Please sign into the Earthdata Forum for active user support.

Up Topic SeaDAS / MODIS Direct Broadcast Support / leapsec.dat failure
- By teodosiolacava Date 2020-12-09 09:56
Hello
I'm running modisl1d to process our directed acquired MODIS data.
Since the 1st of December 2020 the process in not working anymore.

The error we receive is as the following:

"Running validation test on geolocation file...
/san/modis/programmi/modisl1db1.7/run/scripts/modis_geocheck.csh
A2020342011659.GEO 80
Number of pixels with missing geolocation: 6025300
*** ERROR: No geolocated pixels found in A2020342011659.GEO.
*** Validation test failed for geolocation file A2020342011659.GEO.

modis_GEO.csh: ERROR: MODIS geolocation processing failed.
Please ensure utcpole.dat and leapsec.dat are up-to-date in
/san/modis/programmi/modisl1db1.7/run/var/modis"

I also updated the de200.eos under .../modis/static/
and the error changed a little bit:

"Creating MODIS geolocation file...
/san/modis/programmi/modisl1db1.7/run/bin/geogen_modis
GEO version: 5.0.14 built on Dec 23 2010 (12:16:59)
scan: 0 out of 432 Wed Dec  9 10:04:38 2020
Errore di accesso al segmento di memoria (creato file core)
geogen_modis exit status: 139

Running validation test on geolocation file...
/san/modis/programmi/modisl1db1.7/run/scripts/modis_geocheck.csh T2020343205225.GEO 80
*** ERROR: T2020343205225.GEO is empty!
*** Validation test failed for geolocation file T2020343205225.GEO.

modis_GEO.csh: ERROR: MODIS geolocation processing failed.
Please ensure utcpole.dat and leapsec.dat are up-to-date in
/san/modis/programmi/modisl1db1.7/run/var/modis"

Thanks
- By teodosiolacava Date 2020-12-09 13:32
Thanks
As already written,
I also updated the de200.eos file under .../modis/static/ following the indication at the link you provided,
without fixing the problem.

After updating such a file, the error changed a little bit:

"Creating MODIS geolocation file...
/san/modis/programmi/modisl1db1.7/run/bin/geogen_modis
GEO version: 5.0.14 built on Dec 23 2010 (12:16:59)
scan: 0 out of 432 Wed Dec  9 10:04:38 2020
Errore di accesso al segmento di memoria (creato file core)
geogen_modis exit status: 139

Running validation test on geolocation file...
/san/modis/programmi/modisl1db1.7/run/scripts/modis_geocheck.csh T2020343205225.GEO 80
*** ERROR: T2020343205225.GEO is empty!
*** Validation test failed for geolocation file T2020343205225.GEO.

modis_GEO.csh: ERROR: MODIS geolocation processing failed.
Please ensure utcpole.dat and leapsec.dat are up-to-date in
/san/modis/programmi/modisl1db1.7/run/var/modis"

Thanks
- By seanbailey Date 2020-12-09 14:09
geogen_modis exit status: 139 is a segfault, so something is definitely not happy.   The code writes to several log files, one of these may contain some helpful information (LogStatus.<basename>.GEO, LogReport.<basename>.GEO and LogUser.<basename>.GEO).  You may find the information cryptic, if so, you can attach them to a reply post.

Sean
- By teodosiolacava Date 2020-12-09 15:39
thanks,
here there are

more LogReport.A2020344010604.GEO

****************************************
BEGIN_PGE: Wed Dec  9 16:34:33 2020
MSG_TAG: 11
FILE: /san/modis/programmi/l0_to_l1/elaborazione_temporanea/Aqua_215/LogReport.A2020344010604.GEO
LOGGING: status message logging enabled
TRACE_LEVEL: tracing disabled
PID_LOGGING: disabled
DISABLED_LEVELS: none
DISABLED_SEEDS: none
DISABLED_CODES: PGSCSC_W_PREDICTED_UT1 PGSDEM_M_FILLVALUE_INCLUDED
THREAD-SAFE MODE:  disabled
TOOLKIT_VERSION: SCF  TK5.2.17
****************************************

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!                   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).    !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[user@ws2016 Aqua_215]$ more LogStatus.A2020344010604.GEO

****************************************
BEGIN_PGE: Wed Dec  9 16:34:33 2020
MSG_TAG: 11
FILE: /san/modis/programmi/l0_to_l1/elaborazione_temporanea/Aqua_215/LogStatus.A2020344010604.GEO
LOGGING: status message logging enabled
TRACE_LEVEL: tracing disabled
PID_LOGGING: disabled
DISABLED_LEVELS: none
DISABLED_SEEDS: none
DISABLED_CODES: PGSCSC_W_PREDICTED_UT1 PGSDEM_M_FILLVALUE_INCLUDED
THREAD-SAFE MODE:  disabled
TOOLKIT_VERSION: SCF  TK5.2.17
****************************************

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!                   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).    !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

GEO_location_main.c, main():MODIS_U_GEO_BEGIN:288778295
Wed Dec  9 16:34:33 2020
Seed file: 5.5 Running MOD_PR03 MODIS Geolocation main() 5.2 compiled on Dec 23 2010 at 12:16:59 using makefile 1.1

PGS_TD_timeCheck():PGSTD_M_ASCII_TIME_FMT_B:26112
the time string passed in is in proper CCSDS ASCII Time Format B

PGS_TD_timeCheck():PGSTD_M_ASCII_TIME_FMT_B - 290 additional occurrences

getMODISfileinfo():PGS_E_UNIX:3848
the time string passed in is in proper CCSDS ASCII Time Format B

[user@ws2016 Aqua_215]$ more LogUser.A2020344010604.GEO

****************************************
BEGIN_PGE: Wed Dec  9 16:34:33 2020
MSG_TAG: 11
FILE: /san/modis/programmi/l0_to_l1/elaborazione_temporanea/Aqua_215/LogUser.A2020344010604.GEO
LOGGING: status message logging enabled
TRACE_LEVEL: tracing disabled
PID_LOGGING: disabled
DISABLED_LEVELS: none
DISABLED_SEEDS: none
DISABLED_CODES: PGSCSC_W_PREDICTED_UT1 PGSDEM_M_FILLVALUE_INCLUDED
THREAD-SAFE MODE:  disabled
TOOLKIT_VERSION: SCF  TK5.2.17
****************************************

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!                   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).    !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

GEO_location_main.c, main():MODIS_U_GEO_BEGIN:288778295
Wed Dec  9 16:34:33 2020
Seed file: 5.5 Running MOD_PR03 MODIS Geolocation main() 5.2 compiled on Dec 23 2010 at 12:16:59 using makefile 1.1
- By seanbailey Date 2020-12-09 15:56
You are using a very old version:

Seed file: 5.5 Running MOD_PR03 MODIS Geolocation main() 5.2 compiled on Dec 23 2010 at 12:16:59 using makefile 1.1


What version of SeaDAS are you running?  What platform are you running it on?

Sean
- By teodosiolacava Date 2020-12-10 10:39
Effectively we were using the 1.7 version of modisl1db on a Linux 2.6.32-504.8.1.el6.x86_64 x86_64.
I fixed using an updated  32bit version of de200.eos

Thanks for the precious support
Up Topic SeaDAS / MODIS Direct Broadcast Support / leapsec.dat failure