Thanks for getting back to me so quickly Rosalyn. I spotted the problem because I am working on creating a data standard for another project, and I am basing it heavily on the CF 1.4 standard. That project needs a compliance checker, but the one you have needs python and the linux-only (it seems) cdat library to run, so I am porting the cfchecks.py script to java. The new java code will be used in both a checker integrated into other data handling programs and as a java applet that runs on a website. The applet solves the problem that the python script currently has of having to upload an entire NetCDF file to check it, which is a problem for some large data files our users have (several GB). I would be happy to contribute the java code back to you when the project is finished if you think it would be useful.
Thanks, Joshua. On Tue, Aug 24, 2010 at 8:27 AM, Rosalyn Hatcher <[email protected]> wrote: > Hi Joshua, > > From my quick look, I think the 2 commented out lines (921-922) should have > been moved to inside the "if self.coards:" block. > > I'll commit this to the trunk in a little while. > > As for your other question, the cf-checker code is open source, so if you > want to take a copy and install it locally you are free to do so. > If you make any changes/improvements to the code that you think would be > useful generally, I'd be grateful if you could send them to me and I'll > consider feeding them into the main development. I suppose I should also > add a license file to this at some stage. > > Cheers, > Ros. > > Joshua wrote: >> >> Hi list, >> I'm not sure if this is the right place to ask this question, so if >> its not someone please point me to the right place. >> >> I was looking at the cf checker script, and there seems to be an error >> on line 971 of the cfchecks.py script in trunk. It checks to see if >> something is in the list validTrailing, but the only other lines >> referring to vaildTrailing are commented out on lines 920-922 with a >> comment "## Commented out for CRM #022". I have an account on the cf >> trac, but I didn't want to make a new ticket until I was sure there >> wasn't something I was missing. Can anyone weigh in on this, or >> should I just make a ticket on trac? >> >> On a related note, does anyone know the license on the cfchecks.py >> file. There is no license information in the header. >> >> Thanks, >> Joshua. >> _______________________________________________ >> CF-metadata mailing list >> [email protected] >> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata >> > > > -- > ------------------------------------------------------------------------ > Rosalyn Hatcher > NCAS Computational Modelling Services > Dept. of Meteorology, University of Reading, Earley Gate, Reading. RG6 6BB > Email: [email protected] Tel: +44 (0) 118 378 6016 > > _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
