-
Notifications
You must be signed in to change notification settings - Fork 6
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
Adding recipe for GODAS #21
Conversation
Well I hadnt seen this before... @cisaacstern |
I almost got the example to run, but I am getting this error:
indicating to me that this is still not properly concatenting/merging the individual datasets? @cisaacstern does this look familiar to you? |
@jbusecke apologies for missing this notification. Yes, this seems to be the same issue as pangeo-forge/pangeo-forge-recipes#517, which I am working on a fix for in pangeo-forge/pangeo-forge-recipes#521. Let's remember to retry this once that fix goes in. |
Also, the rate limit error above is presumably due to these lines in the action: We could resolve this issue if there was a way to rework the action so that it does not need to call back into the GitHub API, and instead relies only on injected environment variables for the necessary context. As of this moment, I'm not sure if/how we might accomplish that. I'll open an issue on the action for that. |
Co-authored-by: Charles Stern <62192187+cisaacstern@users.noreply.github.com>
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
@cisaacstern if you have a minute, could you look into this error:
Wondering if this is related to pangeo-forge/pangeo-forge-recipes#527 and if there is an easy way for me to circumvent this? Maybe just getting pgf-recipes from the beam-refactor branch is the solution? |
Yes that's correct. And it also reflects that we should have a better plan for integration testing of recipes + runner. I'll take a closer look at a fix this afternoon. Thanks for raising this, Julius! |
Opened pangeo-forge/pangeo-forge-runner#76 to track the issue above. Turns out I won't have time to work up a PR today, but can look at it next week. |
@jbusecke, following merge of pangeo-forge/pangeo-forge-runner#77, the issue above should be fixed. Can you try re-deploying the test? (I just checked if I could, but I think I don't have permissions to do so on this repo.) |
Rerunning now. Let me also make a dev team here and give you permissions. |
Yay! The deployment worked. Could you try to rerun the test, just to confirm that the 'maintain' role (via new |
Yep! I can now add/remove labels! Thanks Julius! |
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
Looking promising! 😄 |
Deployment was successful, but there is an issue with combining the surface and depth resolved datasets. Debugging that rn. |
Hmm this looks like some sort of bug in the recipe to me. This particular dataset contains surface variables like this: When merging this I would expect it to just work, and in the manual case it does: import fsspec
import xarray as xr
def make_full_path(variable, time):
return f'https://downloads.psl.noaa.gov/Datasets/godas/{variable}.{time}.nc'
with fsspec.open(make_full_path('vcur', 1980)) as f:
with fsspec.open(make_full_path('sshg', 1980)) as f_surf:
ds = xr.open_mfdataset([f, f_surf])
ds but from the dataflow logs I am getting an error message like this:
This indicates to me that somwhere in the aggregation code the surface variables either get promoted to have a scalar @cisaacstern I think we should add this sort of pattern to the PGF-recipes tests? |
This is a leftover from our old mono-feedstock. Can we migrate this into a separate feedstock? |
meta.yaml