I am trying to understand how modis_atteph.py works. I have an example below. When I enter a date/time close to the current time, it gives such an error. Is there a URL or a manual that explain the algorithm or at the very least the exit codes? Especially when the increase in latency causes problem with the processing.
spike.seadas% date -u ; date -u +%j
Sat Jul 2 01:44:13 UTC 2022
spike.seadas% /usr/local/seadas/7.5/scripts/modis_atteph.py -f -m terra -s 2022182160500 -e 2022182161000; echo $?
spike.seadas% /usr/local/seadas/7.5/scripts/modis_atteph.py -f -m terra -s 2022183000000 -e 2022183050000; echo $?
Traceback (most recent call last):
File "/usr/local/seadas/7.5/scripts/modis_atteph.py", line 125, in <module>
File "/usr/local/seadas/7.5/scripts/modules/anc_utils.py", line 439, in findweb
self.files[str(f).lower()] = str(f)
IndexError: string index out of range
I tried modis_atteph.py as follow:
/usr/local/seadas/7.5/scripts/modis_atteph.py --mission=terra --start=2022183160135 --stop=2022183161735
The att & eph files cover only 14:00 to 16:00 hours which is outside the stop/start given. Does this mean I would have to verify the range covered by the returned att/eph to make sure it includes the entire given period? Am I missing something?
- Subject Matter Expert
- Posts: 351
- Joined: Tue Feb 09, 2021 5:42 pm America/New_York
For SeaDAS 7.5, modis_atteph used to return
0 - all is well in the world
1 - predicted attitude selected
2 - predicted ephemeris selected
4 - no attitude found
8 - no ephemeris found
We recently changed the api which modis_atteph called to retrieve ancillary data, and the return status was changed to
0 all is well
1 att/eph files are not optimal
2 att/eph files missing
Unfortunately, SeaDAS 7.5 users have to live with it.
We are working to resume the return status for modis_attpeh for future tags of ocssw.
I ran modis_attepeh (ocssw_v2021.2) as the following, which should behave similar as modis_attph.py in SeaDAS 7.5
$ modis_atteph --mission=terra --start=2022183160135 --stop=2022183161735
Running debug binaries...
The reason you did't get
is that they were not available at the moment.