Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONUS NRT V3 Schedule Jobs are Failing #111

Open
1 task
ranchodeluxe opened this issue Aug 1, 2024 · 9 comments
Open
1 task

CONUS NRT V3 Schedule Jobs are Failing #111

ranchodeluxe opened this issue Aug 1, 2024 · 9 comments

Comments

@ranchodeluxe
Copy link
Contributor

Problem

CONUS NRT V3 scheduled jobs are failing.

GH Actions showing which job ids are failing and here's are the docs to walk through to debug

Action Items

  • figure out what's wrong and try to come up with a fix
@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

Love the write up!

seems like they are failing because pre-processed timesteps are missing. ie job 412d9f87-0ec3-438a-9315-fe5e45276a33

"FileNotFoundError('maap-ops-workspace/shared/gsfc_landslides/FEDSpreprocessed/NOAA20/20240323_AM.txt')

it looks like we do have a gap in our daily files at doy 83 - skipping from J1_VIIRS_C2_Global_VJ114IMGTDL_NRT_2024079.txt to J1_VIIRS_C2_Global_VJ114IMGTDL_NRT_2024085.txt

@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

As far as I can tell, the "daily" files are all released through the place we are querying from -- I can only see them going back a certain about of time, to June 3rd. https://nrt4.modaps.eosdis.nasa.gov/api/v2/content/archives/FIRMS/noaa-20-viirs-c2/Global/

Seems like they only distribute the last 60 days worth.

@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

The firms API seems to only be the last 10 days.

@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

Looks like it wasn't a data outage: https://ladsweb.modaps.eosdis.nasa.gov/alerts-and-issues/

@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

For a fix: I don't know. It seems like either we need to structure the code to be ok with "skipping" a few days OR we need to figure out how to derive our own .txt files from the data that we can get more reliably. Or both.

@ranchodeluxe
Copy link
Contributor Author

ranchodeluxe commented Aug 2, 2024

For a fix: I don't know. It seems like either we need to structure the code to be ok with "skipping" a few days OR we need to figure out how to derive our own .txt files from the data that we can get more reliably. Or both.

Maybe it's acceptable for now (and 2024) to start our NRT runs on 2024-03-25 instead of 2024-01-01?

Then we'll be forced to deal with this during archival runs but that would be another data source

@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

Yeah as a temporary fix it's not the worst. We may run into other data holes, but I guess we can cross that bridge if we come to it.

@mccabete
Copy link
Contributor

mccabete commented Aug 2, 2024

If this happens later in the season though (may onward) it will probably be chopping up real fires though.

@mccabete
Copy link
Contributor

mccabete commented Aug 7, 2024

@ranchodeluxe is there any chance that V3 restarts every time there is a data gap?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants