<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18939"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>Hi Karl,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>A somewhat belated follow-up question in connection with this
proposal (and with some slight overlap with Jamie's email which crossed on the
ether)...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>As things stand the files named in the 'associated_files'
attribute appear thus (using our RCP 4.5 simulation as an
example):</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>"... gridspecFile: gridspec_fx_HadGEM2-ES_rcp45_r0i0p0.nc
areacella: areacella_fx_HadGEM2-ES_rcp45_r0i0p0.nc"</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>Are the <expt_id>_<rip> parts (i.e.
'rcp45_r0i0p0.nc' ) actually required? AFAIK, our gridspec/cellarea files will
not change from one simulation to the next using the same model (HadGEM2-ES in
this case).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>Since, like most centers, we will be running large
numbers of simulations using the same model, it looks like we would need to
create numerous duplicates of the gridspec/cellarea files - or lots of symlinks
- in order to for these references to make sense. Unless you are planning to
manage that on our behalf somehow...?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>I think our 4 gridspec files for the HadGEM2 atm grids are
likely to be called something like...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>gridspec_fx_HadGEM2-ES_atm_pgrid.nc
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>gridspec_fx_HadGEM2-ES_atm_ugrid.nc </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>gridspec_fx_HadGEM2-ES_atm_vgrid.nc </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>gridspec_fx_HadGEM2-ES_atm_uvgrid.nc </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>So without any simulation-specific info. (There
would also be files for the ocean grids)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>As it happens the gridspec files contain grid cell areas, so
I'm now wondering if we'd even supply both?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>I'd be interested to hear your thoughts on this. I may be
mis-understanding something/everything :-)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>Regards</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma>Phil</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=216420714-22102010><FONT color=#0000ff
size=2 face=Tahoma></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Karl Taylor [mailto:taylor13@llnl.gov]
<BR><B>Sent:</B> 19 October 2010 18:36<BR><B>To:</B>
martin.juckes@stfc.ac.uk<BR><B>Cc:</B> Bentley, Philip; Doutriaux, Charles;
Kettleborough, Jamie; Bryan Lawrence; cmor@lists.llnl.gov;
go-essp-tech@ucar.edu; Kyle.Olivo@noaa.gov<BR><B>Subject:</B> CMOR and
cell_measures issues<BR></FONT><BR></DIV>
<DIV></DIV><FONT face="Times New Roman">Dear CMOR users,</FONT><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><BR></BLOCKQUOTE></BODY></HTML>