<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)">
<base href="x-msg://28/">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle21
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 lang=EN-US link=blue vlink=purple style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Luca,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks for the review. Please see my comments below:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>>></span> Please see previous email about the very latest
convention on the dataset version: instead of "v1" it needs to be
something like "vYYYYMMDD"<span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sure, we will use this convention for the dataset version<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>>></span>cmip5/observations/doe/arm/cmbe/1hr/atmos/ps/c1p1/vYYYYMMDD/ps_cfSites_arm_cmbe_c1p1barrow_2001010100-2010010100.nc<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sure, I am OK with adding location information as part of </span><processing
level and product version> <span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>field, but</span> <span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>we may need to consider adding a
delimiter so that publishing script can parse these values correctly (example: c1p1-barrow)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks!<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Giri<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Cinquini, Luca
(3880) [mailto:Luca.Cinquini@jpl.nasa.gov] <br>
<b>Sent:</b> Thursday, January 27, 2011 11:53 AM<br>
<b>To:</b> Palanisamy, Giri<br>
<b>Cc:</b> Renata McCoy; climate-obs; go-essp-tech@ucar.edu; Bob Drach; Dean
Williams; Karl Taylor; Christensen, Sigurd W.<br>
<b>Subject:</b> Re: Extending the DRS syntax to observations<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Giri,<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=apple-tab-span> </span>thanks
for taking a stab at this...<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>o Please see previous email about the very latest convention
on the dataset version: instead of "v1" it needs to be something like
"vYYYYMMDD"<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>o I am not ware of any convention about case in DRS (anybody
knows?), but I'd say we should try to establish one at least for observations:
either always go with lower case, or have everything in lower case except
possibly for AGENCY, MISSION and INSTRUMENT (as you have done). Someone needs
to make an authoritative decision (PMDI?)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>o I think the DRS spec mandates the <mission or
project> field to be the same in the directory and filename, and I think we
should follow that if we want to avoid future trouble. If you want to
differentiate files from different sites, maybe "barrow" could be
made part of the last field... In another words, the wiki now proposes that the
model field <ensemble> in the file names is used as <processing level
and product version> for observations, but maybe its meaning could be
expanded to take into account anything that the data provider wants to encode
to differentiate files. Maybe something like <product type>, which is
encoded according to project-specific nomenclature ?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>So your full example could be something like this:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>cmip5/observations/doe/arm/cmbe/1hr/atmos/ps/c1p1/vYYYYMMDD/</span><span
class=apple-style-span><span style='font-size:11.5pt;font-family:"Calibri","sans-serif";
color:#1F497D'>ps_cfSites_arm_cmbe_c1p1barrow_2001010100-2010010100.nc</span></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:11.5pt;
font-family:"Calibri","sans-serif";color:#1F497D'>(minus the case...)</span></span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>BTW, the files still contain one single variable per file,
right ?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I started to collect these proposed examples on the wiki,
and I will modify them as consensus is reached...<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>thanks again,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Luca<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Jan 27, 2011, at 9:16 AM, Palanisamy, Giri wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Luca…</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Some of us from ORNL with the help of Renata have defined the
naming and file name structure for the ARM CMBE files, following the draft
suggestions in Data and Metadata Requirements for CMIP5 Observational Datasets
(<a
href="http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets">http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets</a>).
Please see the details below. We would like to have the group review this
structure and provide us feedback. We highlight two particular questions
after the details are shown.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For the directory structure:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> cmip5/observations/DOE/ARM/CMBE/1hr/atmos/ps/c1p1/v1/</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> <span class=apple-converted-space> </span><i>We used
this directory structure naming convention:</i></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><activity>:</span></b></em><span
class=apple-converted-space><b><i><span style='font-size:10.0pt'> </span></i></b></span><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>cmip5</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><product>:</span></b></em><span
class=apple-converted-space><b><i><span style='font-size:10.0pt'> </span></i></b></span><i><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>observations</span></i><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><agency>:</span></b></em><span
class=apple-converted-space><b><i><span style='font-size:10.0pt'> </span></i></b></span><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>DOE</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><mission or
project>:</span></b></em><span class=apple-converted-space><b><i><span
style='font-size:10.0pt'> </span></i></b></span><i><span style='font-size:
10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ARM</span></i><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><instrument>:</span></b></em><span
class=apple-converted-space><b><i><span style='font-size:10.0pt'> </span></i></b></span><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>CMBE</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><frequency>:</span></b></em><i><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>1hr</span></i><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><observational
realm>:</span></b></em><span class=apple-converted-space><b><i><span
style='font-size:10.0pt'> </span></i></b></span><span style='font-size:
10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>atmos</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><variable name>:</span></b></em><span
class=apple-converted-space><b><i><span style='font-size:10.0pt'> </span></i></b></span><i><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ps</span></i><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><processing level
and product version>:</span></b></em><span class=apple-converted-space><b><i><span
style='font-size:10.0pt'> </span></i></b></span><span style='font-size:
10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>c1p1</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt'><dataset version
number>:</span></b></em><span class=apple-converted-space><b><i><span
style='font-size:10.0pt'> </span></i></b></span><i><span style='font-size:
10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>v1</span></i><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>for file naming:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> ps_cfSites_arm-barrow_cmbe_c1p1_2001010100-2010010100.nc</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><span style='color:#333333;font-style:normal'> </span></em><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt;color:#333333'>we used
the following file naming convention:</span></b></em><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em><b><span style='font-size:10.0pt;color:#333333'><variable
name></span></b></em><b><span style='font-size:10.0pt;color:#333333'>_<<em>variable
table</em></span></b><span style='font-size:10.0pt;color:#333333'>>_<em><</em>mission
or project><em>_<</em>instrument><em>_<<b>processing level and
product version</b>>_</em><<em>temporal subset</em>>.nc</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt;color:#333333'> </span></b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;color:#333333'>Two questions:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;color:#333333'> </span><o:p></o:p></p>
</div>
<div style='margin-left:20.25pt'>
<p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.0pt;
color:#333333'>(1)</span><span style='font-size:7.0pt;color:#333333'> <span
class=apple-converted-space> </span></span><span style='font-size:10.0pt;
color:#333333'>For the <mission or project> field, we are using<span
class=apple-converted-space><b> </b></span><b><</b></span><i><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ARM</span></i><span
style='font-size:10.0pt;color:#333333'>> in the directory structure, but for
this field in the file name structure, we are using<span
class=apple-converted-space> </span><b><</b></span><span
class=apple-converted-space><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span></span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>arm-barrow>. T</span><span
style='font-size:10.0pt;color:#333333'>his is mainly to consolidate the files
from various ARM locations in one final directory (one place). Do you
think this will cause any issues in the publishing script, in the discovery
process, or in CMIP5 tools using the data once they are found?</span><o:p></o:p></p>
</div>
<div style='margin-left:20.25pt'>
<p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.0pt;
color:#333333'>(2)</span><span style='font-size:7.0pt;color:#333333'> <span
class=apple-converted-space> </span></span><span style='font-size:10.0pt;
color:#333333'>We sometimes use upper case where it seemed appropriate.
Is there a standard for case, especially as it applies to major projects,
programs, etc.? </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks!</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Giri</span><o:p></o:p></p>
</div>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;
border-width:initial;border-color:initial'>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
class=apple-converted-space><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span></span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Renata McCoy
[mailto:mccoy20@llnl.gov]<span class=apple-converted-space> </span><br>
<b>Sent:</b><span class=apple-converted-space> </span>Wednesday, January
26, 2011 6:51 PM<br>
<b>To:</b><span class=apple-converted-space> </span>Cinquini, Luca (3880)<br>
<b>Cc:</b><span class=apple-converted-space> </span>Renata McCoy;
climate-obs;<span class=apple-converted-space> </span><a
href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>; Bob Drach; Dean
Williams; Karl Taylor<br>
<b>Subject:</b><span class=apple-converted-space> </span>Re: Extending the
DRS syntax to observations</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>Hi Luca,<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>I was experimenting with setting up a publishing script for
the ARM cmbe observational data following the proposal below. I see few issues:<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>I understand (I am cc-ing Bob Drach to check on that) the
publisher needs at least those 3 fields for the "CMIP5' project:<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>project (which is 'CMIP5'), experiment (that could be
specified as 'none' in command options, but maybe should be 'observations' ?),
and model <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>A 'model' is an important field and I was trying to set it
up so as 'cmbe' would be my 'model', which seems to be equivalent to 'airs' for
NASA AIRS data<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>The other problem is that we need a specific table (CMOR
table) to establish the controlled variable list and data frequency that is obs
specific.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>We (with ORNL team) are trying to create an obsCfSites
table, that would be mostly a copy of cfSites table with obs specific time
definition (for cmbe it's 1 hour average, for CDIAC data - 30 min average, and
for 3D data with vertical axis - we would like to specify that any pressure
level could be reported). I think it would be good if we could encompass all
the observational data needs in one observational table. <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>I did not try to test publish the data yet, I am working on
rewriting the data with the appropriate metadata first, so I am not sure what
other problems may pop up.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>Greetings,<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>Renata<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>------------------------------------------------------------<br>
Renata B. McCoy, Ph.D<br>
Program for Climate Model Diagnosis and Intercomparison(L-103)<br>
Lawrence Livermore National Laboratory<br>
P.O. Box 808<br>
Livermore, CA 94551<br>
<br>
(925) 424-5237 (voice)<br>
(925) 422-7675 (fax)<br>
<a href="mailto:mccoy20@llnl.gov">mccoy20@llnl.gov</a><br>
------------------------------------------------------------</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal>On Jan 26, 2011, at 2:50 PM, Cinquini, Luca (3880) wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal><br>
<br>
<br>
<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>Hi all,<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span class=apple-tab-span> </span><span
class=apple-converted-space> </span>apologies for cross-posting...<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><br>
I'd like to start a discussion on how the DRS specification for CMIP5
model output (<a
href="http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_syntax.pdf">http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_syntax.pdf</a>)<br>
can be applied to observational datasets that will be made part of the
same archive. A proposal based on recent workshops with PCMDI is
detailed on this wiki page:<br>
<br>
<u><span style='color:#144FAE'><a
href="http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets">http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets</a></span></u><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal><u><span style='color:#144FAE'><br>
</span></u>As an example, the directory structure for the NASA AIRS dataset
would look like this:<br>
<br>
<root
directory>/cmip5/observations/nasa/aqua/airs/mon/atmos/ta/l3/vYYYYMMDD/<files><br>
<br>
where:<br>
<br>
"observations"=<product>, same as DRS "output1" or
"output2"<br>
"nasa"=<agency>, same as DRS "institute"<br>
"aqua"=<mission>, replaces DRS "model"<br>
"airs"=<instrument>, replaces DRS "experiment"<br>
"l3"=<processing level>, replaces DRS "ensemble
member"<br>
vYYYYMMDD=the dated version, same as specified by the DRS<br>
<br>
The values for the various fields <agency>, <mission>,
<instrument> and <processing level> would need to be selected
from a controlled vocabulary similar to the one established for models.<br>
<br>
Any comment or insight on the matter is appreciated.... The idea is to try
to finalize the specification relatively quickly, let's say a couple of
weeks, so that we can start preparing<br>
and publishing these observations into the CMIP5 archive.<br>
<br>
thanks in advance,<br>
<br>
Luca<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>