-
Notifications
You must be signed in to change notification settings - Fork 18
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
CDF fixes #219
Conversation
…ut netcdf format files, however a -60 error code is sometimes returned by nc_put_var1_long
I just tested the netCDF conversion tool and
|
I'm getting a -2005 error code:
Same thing for another fitacf file, which I've attached since it is smaller: 20180624.0601.00.hkw.fitacf.gz Did I just do something stupid? I'm running out of time for debugging today, so I'm just reporting what I have. By the way, the NCAR link posted above is unreachable for me. NASA has documentation here: https://cdf.gsfc.nasa.gov/html/cdf_docs.html The C reference manual is probably helpful. Looking at Chapter 8, it looks like we can make debugging easier by printing the CDF status message when there's an error. Finally, the scope of this PR is fixing CDF problems, but I did check which binaries the
|
As noted in #211 and in the description of this pull request, I haven't been able to sort out the |
Good to know. I didn't see -2005 referenced anywhere, so I didn't know it was the same |
So, @egthomas, any thoughts on why the -60 error code is now popping up? Is this a bug with the rst code or an error with the test file you're using? Can you describe a little more on the bug that you did fix in the |
@egthomas, bump here on thoughts at why the -60 error code is now happening? |
What is the status on this PR? |
I'm thinking this PR has a bit of scope creep to it getting into the error codes that we're seeing. @egthomas, do you remember the original bug that you fixed with this code? Can we test that at least that bug is fixed and save looking into the error codes another day? |
Fixing those error codes was the original goal of #211 and this pull request, but after more than a year it has still not been accomplished.
As stated in the previous messages, these are the changes made by this pull request:
To summarize, the |
@egthomas Is there anything we can do to test the particular bug fixes in this PR, or do you recommend that we just merge it without any further testing? I realise testing might be difficult since the |
Unfortunately I can't think of any tests for For Note that because the |
To fully fix CDF stuff, open another PR. It's going to take someone sitting down and going through the CDF API in detail. |
This pull request is a partial attempt at addressing the issues raised in #211 by adding the
--version
option to several additional binaries, cleaning up spacing in thedmaptocdf
code, and fixing a bug present in bothdmaptocdf
anddmaptoncdf
. The original problem with handlingltab
arrays still remains to be fixed.