-
Notifications
You must be signed in to change notification settings - Fork 33
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
CFchecker does not find a coordinate variable #37
Comments
Hmmm. I've tried your snippet above and it works ok for me. Could you send me the header of your netcdf file please ( |
Here it is. The file is small, I send it separately.
|
The file you sent me works absolutely fine through the head of master. I will leave this issue open for the moment so that once I've got a release candidate available for community testing you can confirm that it is ok for you. Whilst testing this I did find one non-related bug - where the checker fell over due to not liking the one dimensional character array for sector. This has been fixed. |
Thanks |
@RosalynHatcher we're also getting |
@durack1 @RobertPincus @taylor13 |
@RosalynHatcher : I've just come across this. The problem may be that @senesis is using a version of the checker which defaults to CF-1.6 and doesn't support CF-1.7. In any case, the output above says that it is using CF-1.6, and in CF-1.6 the |
Here's an ncdump of the file: // global attributes: |
@RosalynHatcher I'd note that for the global_attribute |
I hadn't seen integer values expressed as 1LL. Is this o.k.? what does "LL" mean in this context? |
Once I'd removed the LL's Karl mentions above in order to generate the netcdf. (I've not come across this either.) The file is read absolutely fine by cf-checker-3.1.0. The CF Checker doesn't care about the sub-index of anything in the Conventions global attribute other than CF-. Can you please confirm that you were using the latest version of the checker? |
@RosalynHatcher I am using the web interface at http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl. I've just confirmed that the checker doesn't seem to be parsing the Conventions attribute correctly: |
@taylor13 Might LL refer to long ints? These are set as part of a Python dictionary and written using netcdf4: |
certainly possible. But @RosalynHatcher thinks that's causing problems with the checker. Rosalyn, does the checker accept long ints? |
certainly possible. But @RosalynHatcher<https://github.com/RosalynHatcher> thinks that's causing problems with the checker. Rosalyn, does the checker accept long ints?
That seems like a red herring - the checker appears to be failing to parse the Conventions attribute, no? Not these other attributes.
|
The version you are using is an old version that only goes up to CF-1.6. As Martin said "CF-1.6 CMIP-6.0" was invalid at CF-1.6, hence the failure. Your file contains CF-1.7 data so you should be using the latest checker on our test server: http://pumatest.nerc.ac.uk/cgi-bin/cf-checker.pl Please try running it through this version. I don't know whether it will handle the LL though, I suspect not. The reason I had to remove them from the CDL you posted was because The current puma.nerc.ac.uk server will be retired in the next couple of months sorry for the confusion, it's taken us much longer than anticipated to move across. If you still have problems running it through the CF-1.7 version of the checker, can you please create a new issue as this isn't related to the original poster's one. Thanks. |
Not sure if edits of messages get communicated out, but I just updated my mistake in the above that it isn't a bug rather that "CF-1.7 CMIP-6.0" is not valid at CF-1.6. |
@RoslynHatcher Thanks very much, using the newer on-line compliance checker shows that the file does indeed follow standards and conventions.
Sorry for any confusion I caused using the outdated server (though I might not be the only one).
The version you are using is an old version that only goes up to CF-1.6. As Martin said this had a bug in it that causes failure parsing the conventions attribute. Your file contains CF-1.7 data so you should be using the latest checker on our test server: http://pumatest.nerc.ac.uk/cgi-bin/cf-checker.pl
Please try running it through this version. I don't know whether it will handle the LL though, I suspect not. The reason I had to remove them from the CDL you posted was because ncgen was giving me syntax errors because of it and I thus couldn't generate the netCDF file with LL in it.
The current puma.nerc.ac.uk<http://puma.nerc.ac.uk> server will be retired in the next couple of months sorry for the confusion, it's taken us much longer than anticipated to move across.
If you still have problems running it through the CF-1.7 version of the checker, can you please create a new issue as this isn't related to the original poster's one. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#37 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALRriFqS1JEevb_JC-8VzS40L6-T2o2zks5vKpQGgaJpZM4SWS2e>.
|
If the "LL" is still included next to integers, I would try to remove them. It's not good if ncgen doesn't know how to handle them. That would lead me to believe that they are not standard netCDF. (Even if the CF-checker doesn't object.) |
@RobertPincus what software are you using to write these files? |
I am quite newcomer to CFChecker, so please forgive me for possible irrelevance of this issue
When provided with a file showing this structure (here abridged), CFchecker produces the output reported further below, which seems to be a misbehaviour
Output :
this is also true when the main variable has more (space) dimensions
The text was updated successfully, but these errors were encountered: