ocssw/processing error getting ancillary data after 2022/179 00:00 Z

Use this Forum to find information on, or ask a question about, NASA Earth Science data.
jay_cable
Posts: 20
Joined: Wed Feb 01, 2017 4:22 pm America/New_York
Answers: 0

ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by jay_cable » Tue Jun 28, 2022 2:07 am America/New_York

Since 2022/179 00:00 Z we have been getting errors with our aqua and terra processing of direct broadcast data, with what appears to be an issue with the ancillary data fetching. Are we doing something wrong, or is there something broken on whatever serves the ancillary data?

modis_GEO is failing like so:

modis_GEO -v --threshold=80 T2022179043003.L1A_LAC
Searching database: /opt/modis/ocssw/var/ancillary_data.db
Input file: T2022179043003.L1A_LAC
Sensor : modist
Start time: 2022179043003
End time : 2022179043500

OBPG session started

Downloading T2022179043003.anc.server ( 0.00 MBs)

[==================================================]...Done

ERROR: display_ancillary_files.cgi script returned blank entry for att0. Exiting.

Failed to identify/retrieve attitude/ephemeris required to geolocate T2022179043003.L1A_LAC; exiting.

When I run "modis_atteph" by hand, anything after 20221790000000 fails:

[processing@nrt-seadas-prod-0001 ~]$ modis_atteph -m terra -v -s 2022178212351 -e 2022178232351
ancillary_data.db
Searching database: /opt/modis/ocssw/var/ancillary_data.db

Input file: None
Sensor : terra
Start time: 2022178212351
End time : 2022178232351

OBPG session started

Downloading 2022178212351.anc.server ( 0.00 MBs)
[==================================================]...Done
Found: /opt/modis/ocssw/var/anc/2022/178/AM1ATTN0.A2022178.2000.002
Found: /opt/modis/ocssw/var/anc/2022/178/AM1ATTN0.A2022178.2200.002
Found: /opt/modis/ocssw/var/anc/2022/178/AM1EPHN0.A2022178.2000.002
Found: /opt/modis/ocssw/var/anc/2022/178/AM1EPHN0.A2022178.2200.002
All required attitude and ephemeris files successfully determined and downloaded.
att1=/opt/modis/ocssw/var/anc/2022/178/AM1ATTN0.A2022178.2000.002
att2=/opt/modis/ocssw/var/anc/2022/178/AM1ATTN0.A2022178.2200.002
eph1=/opt/modis/ocssw/var/anc/2022/178/AM1EPHN0.A2022178.2000.002
eph2=/opt/modis/ocssw/var/anc/2022/178/AM1EPHN0.A2022178.2200.002


- All optimal ancillary data files were determined and downloaded. -

[processing@nrt-seadas-prod-0001 ~]$ modis_atteph -m terra -v -s 2022178232351 -e 2022179012351
ancillary_data.db
Searching database: /opt/modis/ocssw/var/ancillary_data.db

Input file: None
Sensor : terra
Start time: 2022178232351
End time : 2022179012351

OBPG session started
Downloading 2022178232351.anc.server ( 0.00 MBs)
[==================================================]...Done
ERROR: display_ancillary_files.cgi script returned blank entry for att0. Exiting.

Tags:

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 644
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 1 time

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by OB SeaDAS - xuanyang02 » Tue Jun 28, 2022 11:25 am America/New_York

modis_atteph -m terra -v -s 2022178212351 -e 2022178232351 works now

Bing

jay_cable
Posts: 20
Joined: Wed Feb 01, 2017 4:22 pm America/New_York
Answers: 0

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by jay_cable » Tue Jun 28, 2022 2:05 pm America/New_York

While that works now, we are still having issues with newer data - did something change?
About 2 hours ago we were having the same issue with a newer pass, but it is working now.

modis_GEO\ -v\ --threshold\=80\ T2022179092439.L1A_LAC ----

Determining required attitude and ephemeris files...
ancillary_data.db
Searching database: /opt/modis/ocssw/var/ancillary_data.db
Input file: T2022179092439.L1A_LAC
Sensor : modist
Start time: 2022179092439
End time : 2022179093000
OBPG session started
Downloading T2022179092439.anc.server ( 0.00 MBs)
[==================================================]...Done
ERROR: display_ancillary_files.cgi script returned blank entry for att0. Exiting.
Failed to identify/retrieve attitude/ephemeris required to geolocate T2022179092439.L1A_LAC; exiting.

As of a few minutes ago though "modis_atteph" worked though:

[processing@nrt-seadas-prod-0001 ~]$ modis_atteph -m terra -v -s 2022179092439 -e 2022179093000
ancillary_data.db
Searching database: /opt/modis/ocssw/var/ancillary_data.db

Input file: None
Sensor : terra
Start time: 2022179092439
End time : 2022179093000

OBPG session started
Downloading 2022179092439.anc.server ( 0.00 MBs)
[==================================================]...Done
Downloading 'AM1ATTN0.A2022179.0800.002' to /opt/modis/ocssw/var/anc/2022/179
Downloading AM1ATTN0.A2022179.0800.002 ( 0.43 MBs)
[==================================================]...Done
Downloading 'AM1EPHN0.A2022179.0800.002' to /opt/modis/ocssw/var/anc/2022/179
Downloading AM1EPHN0.A2022179.0800.002 ( 0.43 MBs)
[==================================================]...Done
All required attitude and ephemeris files successfully determined and downloaded.
att1=/opt/modis/ocssw/var/anc/2022/179/AM1ATTN0.A2022179.0800.002
eph1=/opt/modis/ocssw/var/anc/2022/179/AM1EPHN0.A2022179.0800.002


- All optimal ancillary data files were determined and downloaded. -

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 644
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 1 time

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by OB SeaDAS - xuanyang02 » Tue Jun 28, 2022 4:49 pm America/New_York

The unavailability of att/eph files is related to an issue with a distribution server upstream from us. That issue is resolved.

We did make some changes to the api "anc", which modis_atteph calls (OCSSW V2021.2). It changes the return status of modis_atteph, but it should not affect the files it returns.

Bing

jay_cable
Posts: 20
Joined: Wed Feb 01, 2017 4:22 pm America/New_York
Answers: 0

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by jay_cable » Tue Jun 28, 2022 8:32 pm America/New_York

Hmm, well it is still failing for me for new data. After the data is over 12 or so hours old we can process it, and the modis_atteph requests work. With direct broadcast data this is a problem. Are we doing something wrong? Should it be working at this point?

It is still failing for me for new data as of now:
modis_GEO -v --threshold=80 T2022179224554.L1A_LAC

STDOUT: Determining required attitude and ephemeris files...

ancillary_data.db

Searching database: /opt/modis/ocssw/var/ancillary_data.db

Input file: T2022179224554.L1A_LAC

Sensor : modist

Start time: 2022179224554

End time : 2022179225500

OBPG session started

Downloading T2022179224554.anc.server ( 0.00 MBs)

[==================================================]...Done

ERROR: display_ancillary_files.cgi script returned blank entry for att0. Exiting.

[processing@nrt-seadas-prod-0001 ~]$ modis_atteph -m terra -v -s 2022179224554 -e 2022179225500
ancillary_data.db
Searching database: /opt/modis/ocssw/var/ancillary_data.db

Input file: None
Sensor : terra
Start time: 2022179224554
End time : 2022179225500

OBPG session started
Downloading 2022179224554.anc.server ( 0.00 MBs)
[==================================================]...Done
ERROR: display_ancillary_files.cgi script returned blank entry for att0. Exiting.

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 644
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 1 time

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by OB SeaDAS - xuanyang02 » Tue Jun 28, 2022 8:45 pm America/New_York

Unfortunately, anc_data_api is not returning att/eph files for your start/stop time.
https://oceandata.sci.gsfc.nasa.gov/api/anc_data_api/?&m=8&s=2022-06-28T22:45:54&e=2022-06-28T22:55:50

At this moment, att/eph is not available after 2022-06-28T18:00:00
https://oceandata.sci.gsfc.nasa.gov/api/anc_data_api/?&m=8&s=2022-06-28T17:50:00&e=2022-06-28T18:00:00

Bing

jay_cable
Posts: 20
Joined: Wed Feb 01, 2017 4:22 pm America/New_York
Answers: 0

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by jay_cable » Tue Jun 28, 2022 8:51 pm America/New_York

So who maintains that "anc_data_api" thing you are referencing? That stop and start time is over 2 hours ago, in the past att/eph files were available in that window.
Thanks,
-Jay

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 644
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 1 time

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by OB SeaDAS - xuanyang02 » Wed Jun 29, 2022 11:53 am America/New_York

Our team maintains anc_data_api. We are looking into the issue why the availability of att/eph for terra is delayed.

Bing

jay_cable
Posts: 20
Joined: Wed Feb 01, 2017 4:22 pm America/New_York
Answers: 0

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by jay_cable » Wed Jun 29, 2022 1:04 pm America/New_York

Thanks!

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 644
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 1 time

Re: ocssw/processing error getting ancillary data after 2022/179 00:00 Z

by OB SeaDAS - xuanyang02 » Wed Jun 29, 2022 4:01 pm America/New_York

It seems that the average latency for terra att/eph has increased about 100 minutes from 7-10 hours to 9-11 hours since mid June. We are sorry to say that it's beyond our control.

It's 19:46 utc now,
the latest available L0 on our site is 2022180.1855 https://oceandata.sci.gsfc.nasa.gov/directdataaccess/Level-0/Terra-MODIS/2022/180/,
the latest L1 is 2022180115000
https://oceandata.sci.gsfc.nasa.gov/directdataaccess/Level-1A/Terra-MODIS/2022/180/
You can get att/eph with start time not too later than 2022180115000
https://oceandata.sci.gsfc.nasa.gov/api/atteph/T/2022180115000/2022180115500/

Aqua is different -- You can get att/eph NRT files within the two hour window --
https://oceandata.sci.gsfc.nasa.gov/api/atteph/A/2022180180000/2022180180500/

Bing

Post Reply