[Go-essp-tech] model names

[stephen.pascoe at stfc.ac.uk]

Hi Karl,

To rephrase your query: I think you are saying that some, but not all, of the data with " CSIRO-Mk3-6-0" in the filename has "CSIRO-Mk3.6.0" in the NetCDF attributes.  This could be a problem is in the ESG publisher.  Bob should provide the definitive answer but a quick read of the code suggests the published model name is read from the NetCDF attributes.  It may be possible to override this in the publisher config file but the semantics are  quite complex so I'm not sure.  Otherwise someone would need to update the publisher source.  This would be a couple of line fix to deploy at the NCI datanode.


Cheers,
Stephen.

---
Stephen Pascoe  +44 (0)1235 445980
Centre of Environmental Data Archival
STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK

From: go-essp-tech-bounces at ucar.edu [mailto:go-essp-tech-bounces at ucar.edu] On Behalf Of Karl Taylor
Sent: 26 July 2011 01:03
To: go-essp-tech at ucar.edu; Lawrence, Bryan (STFC,RAL,RALSP); Eric Guilyardi; Pascoe, Charlotte (STFC,RAL,RALSP)
Subject: [Go-essp-tech] model names

Hi all,

Bob Drach is on vacation, so I'll ask my question to this list.

There is a model_id stored as a global attribute in the CMIP5 netCDF files.  This name is (typically) passed to CMOR which simply writes it to the files.  The name is also used by CMOR to construct filenames and directory names, but it first removes characters forbidden by the CMIP5 specs.  For example, the model_id=BCC-CSM1.1 is changed to BCC-CSM1-1 in file and directory names.

My question is: If a group published a bunch of data with model_id=CSIRO-Mk3-6-0 and then published additional data with CSIRO-Mk3.6.0, would the ESG publisher or related software get confused?  Note that the model name appearing in filenames and directory structures is not changed in going from 3-6-0 to 3.6.0.

Best regards,
Karl

-- 
Scanned by iCritical.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20110727/d14725f5/attachment-0001.html