DOI-USGS / lake-temperature-model-prep

Pipeline #1
Other
6 stars 13 forks source link

Updating data for rerun of Cannonsville and Pepacton reservoir models #295

Closed limnoliver closed 2 years ago

limnoliver commented 2 years ago

We need to update our DRB reservoir (Cannonsville and Pepacton) models through 2021. This requires updates to data in this repository as well as in delaware-model-prep. In order for Hayley to rerun GLM on these reservoirs, we need to update:

Lauren and Sam will work on updating the national flow and temperature dataset, as well as the PRMS-SNTemp runs (after Margaux has DRB GridMET in hand). Margaux will begin building a data release for this year's forecasts such that Hayley will be able to point to ScienceBase to grab all required reservoir data to run GLM (similar to last time).

lindsayplatt commented 2 years ago

Just to clarify, for observed stream inflows and modeled inflow temperatures, the actual updating is being completed by you and Lauren? So the steps here are just saying to make sure to use/gather these updated data outputs?

limnoliver commented 2 years ago

Yep, I updated the text above to be clearer about which groups will do which pieces. Mostly wanted to put them here because Hayley will need all of these things to rerun GLM.

padilla410 commented 2 years ago

FYI - @jread-usgs is going to run code necessary to complete the NLDAS update for the Lakes Team. It's a low level of effort process on his machine and it is completed locally because the machine needs to be authenticated to NASA. Further details on why the workflow needs to be done this way are documented in issue #1.

jordansread commented 2 years ago

For the DRB footprint for NLDAS, this requires updating these two parts of 6_drivers_fetch.yml to

  replete_time_range:
    command: c(t0=I(0), t1 = I(377900))

  feature_NLDAS_cells:
    command: cells_all(NLDAS_grid, x_range = I(c(387, 408)), y_range = I(c(107, 144)))

and then running scmake('7_drivers_munge/out/7_drivers_munge_tasks.ind') t1 is the last timestep of NLDAS data we're interested in and the x_range and y_range are the cell indices of the cube extent we're pulling (sketch available in #1). I found t1 by going to https://hydro1.gesdisc.eosdis.nasa.gov/dods/NLDAS_FORA0125_H.002

jordansread commented 2 years ago

NLDAS_time[0.377900]_x[401]_y[136].csv NLDAS_time[0.377900]_x[397]_y[136].csv

☝️ these files go to 2022-02-09 @padilla410

padilla410 commented 2 years ago

@limnoliver Task 5 involves work in delaware-model-prep. I have successfully cloned the repo, but does this use a shared cache like lake-temperature-model-prep? Will I have google drive access issues?

limnoliver commented 2 years ago

Sorry for not stating that one clearer, you can just do the NWIS repull that's linked in lake-temp-model-prep, so no need to interact with the other budget data (and yes, you would have run into access issues).

padilla410 commented 2 years ago

@limnoliver, thanks for the clarification. I rebuilt both of the targets in 6_nwis_fetch as part of the work done to complete Task 1 (PR #306). Does that mean I have also completed Task 5?

limnoliver commented 2 years ago

I think so! This is making me think, since we are still dependent on flow observations, that we could have you repull the national flow data (instead of temperature as we discussed yesterday). That repo is pretty clean and already on HPC...I'll reach out via chat to discuss.

padilla410 commented 2 years ago

Howdy folks, looks like Hayley and I have wrapped up all the tasks under this issue. If I can get a 👍 from @limnoliver I will close this.

hcorson-dosch-usgs commented 2 years ago

I didn't contribute to all that data gathering work (thank you all for pulling the data together), but I do now have all the data I need for the reservoir models

limnoliver commented 2 years ago

Yep, we're good. Let's close it!