<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-GB link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hello
Karl,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks
for clearing this up,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Martin<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><font size=2 color=black face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;
font-weight:bold'>From:</span></font></b><font size=2 color=black face=Tahoma><span
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'> Karl Taylor [mailto:taylor13@llnl.gov] <br>
<b><span style='font-weight:bold'>Sent:</span></b> 19 October 2010 18:36<br>
<b><span style='font-weight:bold'>To:</span></b> Juckes, Martin (STFC,RAL,SSTD)<br>
<b><span style='font-weight:bold'>Cc:</span></b> philip.bentley@metoffice.gov.uk;
Doutriaux, Charles; jamie.kettleborough@metoffice.gov.uk; Lawrence, Bryan
(STFC,RAL,SSTD); cmor@lists.llnl.gov; go-essp-tech@ucar.edu;
Kyle.Olivo@noaa.gov<br>
<b><span style='font-weight:bold'>Subject:</span></b> CMOR and cell_measures
issues<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'>Dear CMOR users,<br>
<br>
It has been brought to our attention that the CF checker (which is different
from the CMOR checker) traps an error in CMOR-produced files indicating
non-compliance with the CF conventions. The error is that the
cell_measures attribute is defined, but the area and/or volume data is not
contained in the file. [We have included a non-CF attribute called
"associated_files" that points to the files containing
area/volume.] Still, in order to not confuse CF-compliant software we
plan to immediately release a new version of CMOR in which the
"cell_measures" attribute is replaced by a non-CF attribute named
"ext_cell_measures" (indicating that the area/volume data is
externally available).<br>
<br>
Also, some groups have reported that not all their variables are carried on the
same grid. (For example, sometimes the u and v fields are staggered
relative to T.) In this case it would be necessary to have more than one
set of areas associated with the model, and this is not currently possible
since only areacella, areacello, and volcello are defined in the CMIP5 request
for model output. We have therefore decided to include an option for CMOR
users to suppress writing of the ext_cell_measures attribute when it would
point to areacella or areacello incorrectly. The user would in effect be
allowed one set of areas to be associated with the atmospheric model and one
set of areas/volumes to be associated with the ocean models. The user
would suppress the ext_cell_measures attribute (and areacella, areacello,
volcello would not appear in the "associated_files" attribute) for
any variables where these areas/volumes would be incorrect.<br>
<br>
We hope this is acceptable.<br>
<br>
Best regards,<br>
Karl and Charles<br>
<br>
<o:p></o:p></span></font></p>
</div>
</div>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></body>
</html>