Problems with missing attitude and ephemeris files

Please enter here to ask a question about any NASA Science related topics!
Post Reply
woodbri
Posts: 52
Joined: Thu Jun 04, 2015 10:50 am America/New_York

Problems with missing attitude and ephemeris files

by woodbri » Thu Dec 05, 2019 5:22 pm America/New_York

I running a process-seadas perl script and it has been running without an issue for months. Today when it runs I'm getting errors:

modis_atteph.py -v MOD00.P2019339.1545_1.PDS.L1A --refreshDB
Aqua
Searching database: /u/oceandata/var/ancillary_data.db
Determining pass start and end times...
Aqua
()
Input file: MOD00.P2019339.1545_1.PDS.L1A
Sensor    : aqua
Start time: 2019339154500
End time  : 2019339155000
()
All required attitude and ephemeris files successfully determined and downloaded.
()
- All optimal ancillary data files were determined and downloaded. -
Command exited with non-zero status 12
real 1.90
user 0.12
sys 0.05

modis_GEO.py MOD00.P2019339.1545_1.PDS.L1A -o MOD00.P2019339.1545_1.PDS.GEO
Missing attitude files!
Missing ephemeris files!
Cannot create geolocation from MOD00.P2019339.1545_1.PDS.L1A; exiting.
Command exited with non-zero status 31
real 1.93
user 0.10
sys 0.02

getanc.py --refreshDB MOD00.P2019339.1545_1.PDS.L1A
Aqua
icefile=/u/oceandata/var/anc/2019/337/N201933700_SEAICE_NSIDC_24h.hdf
sstfile=/u/oceandata/var/anc/2019/335/N2019335_SST_OIV2AV_24h.nc
()
*** WARNING: The following ancillary data types were missing or are not optimal:  MET OZONE
*** Beware that certain MET and OZONE files just chosen by this program are not optimal.
*** For near real-time processing the remaining files may become available soon.
Command exited with non-zero status 3
real 0.42
user 0.13
sys 0.02

And if I look into /u/oceandata/var/anc/2019/ I do not have a directory for day 339, all prior days are there.

-Steve

Tags:

OB.DAAC - SeanBailey
User Services
User Services
Posts: 1219
Joined: Wed Sep 18, 2019 6:15 pm America/New_York
Answers: 1

Problems with missing attitude and ephemeris files

by OB.DAAC - SeanBailey » Thu Dec 05, 2019 6:32 pm America/New_York

Steve,
A long-ish story that can be summed up as: a dying RAID led to a massive DB update that led to another DB getting hammered.  That DB is currently about 18hours behind (but slowly catching up).
Until it has caught up, you may continue to see issues "missing" data. 

Please bear with us while Irv finishes his clean up on aisle seven...

Sean

Post Reply