1 09/2003 Processing Library Update CF Checker – Script made available as a web based form on the BADC site - – Links available on the PRISM and CF convention websites – Encouraging feedback has been received – Successfully passed model output data from PRISM IO library thru checker – Shortly to release version which validates the standard_name attribute

2 09/2003 Progress with Coco Development Coco has now been integrated into cdms. First release of coco was lodged in the PRISM cvs server in June. Re-write of standard_deviation and variance to use genutils package, part of the CDAT utilities. – CDMS version 3.3 is now required in order to run coco. Implementation of covariance and correlation. Extension of the genutils package to allow a tolerance for missing data to be specified.

3 09/2003 Progress with Coco Development cont... Validation of standard_names against the standard name table. Integration of udunits. Several changes made to the underlying methods for accessing the variable attributes. Currently working on processing the metadata for the binary operations. (E.g validating the input units, calculating the units of the result, etc.) This is an extension to the MV module.

4 09/2003 Progress against Work Plan

5 09/2003 Plans - Next Period End September 2003: Lodge next release of Coco - to include… – Correlation / covariance and tolerance to missing data option. – Units validation using udunits. – Validation of standard_names attribute. – Binary operations, with metadata adjusted and validated accordingly. Try processing model output produced from PRISM IO library. End November 2003: – Separation of the id and standard_name attributes (Bug Fix) – Fix to the getAlias() routine to allow netcdf files without the axis attribute to be processed. – Conversion to new Grid. – Collaborate with Stephanie re: option to run output from all models thru the CF checker. – Check that output from Coco is written to netcdf file correctly.

6 09/2003 Plans - Next Period cont... Dec - Jan 2004 – Collapsing down multiple axes. E.g. lat-lon – Further testing using output files produced from PRISM models. – Begin testing installation/Coco on other platforms