-
Notifications
You must be signed in to change notification settings - Fork 63
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
C-iTRACE tracer pointing to NetCDF4 files #230
base: master
Are you sure you want to change the base?
C-iTRACE tracer pointing to NetCDF4 files #230
Conversation
@cisaacstern I seem to be incapable of producing an immaculate pair of files. Is this something I should try to fix or is this a case for your magic wand? [I rewrote these files as netcdf4 files which should fix our netcdf3 block.] |
@jordanplanders in your local development environment, you should be able to:
and then, from the root of your clone of the
then, each time you make a For more on this: https://pre-commit.com/ |
For work that has not been running
which will bring all files up to spec with formatting. |
@cisaacstern Done! Now with a clean bill of health! Fantastic! |
/run citrace_tracer |
The test failed, but I'm sure we can find out why! Pangeo Forge maintainers are working diligently to provide public logs for contributors. |
@cisaacstern Oy. Failed. Ok, I'm not sure what went wrong, but I'll get out my fine (and coarse) toothed comb and go on a hunt. |
@jordanplanders... I'll pull the logs now... (Getting these public by default is one of my top priorities...) |
Looks like the issue is the undefined variable |
@cisaacstern I confess that I'm a bit puzzled. I just ran it locally with the |
Also, we could test the recipe with just the small file before setting it loose on the full canon. |
@jordanplanders, oh sorry didn't realize that This is a known issue with deploying these recipes to Google Cloud Dataflow (where we run them in the cloud): variables defined outside function scopes are often (always?) not available within the function. This has to do with how Dataflow serializes the components of the recipe, but the specific mechanisms are a bit beyond my current level of understanding. Anyway, for a case like this where the variable (It gets a little stylistically questionable when the same variable is reused in multiple functional scopes, but luckily we don't appear to have that issue here.) |
@cisaacstern Makes sense. Like putting import statements in the preprocessing function. Great do have clarification. Would it be better to give it a test run with only two of the files? Maybe the little one and one of the others? Or just go for broke? |
No worries about the full variable scope. The cache from this test will be reused for the production run anyway, so we're just getting ahead on data transfer. I'll re-trigger the test now. |
/run citrace_tracer |
The test failed, but I'm sure we can find out why! Pangeo Forge maintainers are working diligently to provide public logs for contributors. |
Seeing two different errors on backend now:
and
Do both of the URLs which appear in these two errors definitely exist? And if so, do they permit unauthenticated download? |
@cisaacstern I find this mysterious... I ran up against this issue when I ran this snippet
which triggered an error like the one you see, but when I run it this way, no problem:
|
@cisaacstern I didn't properly answer your question earlier. If I navigate to each of those links in a browser, a download begins. Any leads on what might be afoot here? |
@jordanplanders thanks for the follow up. The PR which had been blocking your original feedstock was merged this week. So it's possible we won't need this workaround after all. I've opened pangeo-forge/C-iTRACE-feedstock#5 to see if the original feedstock is indeed unblocked. |
@cisaacstern I came across a version of this issue (I think), which was improved by appending '#mode=bytes' to the url. We're really hoping to be able to make either the C-iTRACE output or possibly the full res iTRACE output available for a few events this spring. If the dev cycle isn't in our favor, I'll get creative about temporary workarounds though! |
Now points to netcdf4 files hosted on figshare, hopefully sidestepping the netcdf3 issue