<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=iso-8859-1">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Karl, Sebastien <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'>My understanding was that ESG publisher would be told which
version to assign when drslib is used to construct the directory structure.
Unless esgpublish is adapted to run drslib underneath I don't see how else it
can be done. Surely there is no need to have 2 versions for a dataset.<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'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Stephen.<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 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
owner-cmor@lists.llnl.gov [mailto:owner-cmor@lists.llnl.gov] <b>On Behalf Of </b>Sébastien
Denvil<br>
<b>Sent:</b> 10 November 2010 23:25<br>
<b>To:</b> cmor@lists.llnl.gov; go-essp-tech@ucar.edu<br>
<b>Subject:</b> Re: DRS v1.0 and CMOR2.x<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks all for the prompt answer and clarification.<br>
<br>
<br>
Le 10/11/2010 20:59, Karl Taylor a écrit : <o:p></o:p></p>
<p class=MsoNormal>Dear all,<br>
<br>
The filenames called for by the DRS and output by CMOR2 (recent versions) are
the same and unchanged. Right?<br>
<br>
I'm not absolutely certain that the quoted section of the DRS is
accurate. My latest understanding is that the "ESG version will
usually be assigned by the ESG publisher, and it cannot be guaranteed that it
always will be consistent with version number appearing in the ESGF data node
directory structure for the data being published. In many cases the
directory structure will be generated some days prior to ESG publication, so
the dates may differ."<br>
<br>
Does anyone disagree with this? <o:p></o:p></p>
<p class=MsoNormal><br>
That's clearer. So the DRS needs some adaptation concerning the version number
"issuer" ; the publisher is the real driver. It implies that if we
publish a simulation in several streams so at different dates (many reason to
support that) they will have different version number. I think loudly just to
put myself in situation.<br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>In any case I think it's much too late to change the
directory structure created by CMOR2 (which, by the way, is optional).<o:p></o:p></p>
<p class=MsoNormal><br>
Ok. <br>
<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>Note that drslib has functionality to transform from any
directory structure whatsoever to the ESGF data node directory structure called
for by the DRS. Also note that the ESG publisher doesn't rely on the
directory structure being consistent with DRS, although we think it is
important that it be so.<o:p></o:p></p>
<p class=MsoNormal><br>
Yes we think as well it's important that at the filesystem level we stick to
the ESG-F datanode DRS. To organize multi model / multi experiment analysis by
AR5 author and by institute researcher this is important for every group. We
will use drslib in the production system then.<br>
<br>
I still have questions for Martin about the different "derived product
class" and their link with "raw" CMIP5 output. I will discuss
that first with Martin "offline" and may get back "online"
to enhance my understanding.<br>
<br>
Regards.<br>
Sébastien<br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>regards,<br>
Karl<br>
<br>
On 11/10/10 6:51 AM, Sébastien Denvil wrote: <o:p></o:p></p>
<pre>Dear all,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I have seen that version v1.0 of the DRS has been released <o:p></o:p></pre><pre><a
href="http://BLOCKEDBLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#req_format">http://BLOCKEDBLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#req_format</a> <o:p></o:p></pre><pre>which is very good.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Reading it, it's clear that CMOR2.x will output files to a directory <o:p></o:p></pre><pre>structure (but not a filename encoding) mapping the old DRS version <o:p></o:p></pre><pre>(v0.27).<o:p></o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<pre>My question is, what is the strong rational behind that fact? Can't <o:p></o:p></pre><pre>CMOR2.x follow the version v1.0 DRS and be natively compatible with the <o:p></o:p></pre><pre>ESGF data node directory structure?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The version number is apparently the reason.<o:p></o:p></pre><pre><activity>/<product>/<institute>/<model>/<experiment>/<frequency>/<modeling <o:p></o:p></pre><pre>realm>/<MIP table>/<ensemble member>/<version number>/<variable name>/ <o:p></o:p></pre><pre><CMOR filename>.nc<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>But quoting the DRS:<o:p></o:p></pre><pre>"Note that the version number assigned to the dataset by ESG is supposed <o:p></o:p></pre><pre>to reflect the date of ESG publication, but the version will usually be <o:p></o:p></pre><pre>assigned by the user so this cannot generally be guaranteed. The user <o:p></o:p></pre><pre>will be instructed to provide ESG with the date that appears in the ESGF <o:p></o:p></pre><pre>data node directory structure for the dataset being published. In many <o:p></o:p></pre><pre>cases the directory structure will be generated some days prior to <o:p></o:p></pre><pre>publication, so the date will not in fact reflect the date of <o:p></o:p></pre><pre>publication, but the date that the directory structure was created."<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>In fine, the user will decide/provide the version number. So I think the <o:p></o:p></pre><pre>user should do that via CMOR2.x.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>CMOR2.x could use the current date as a version number. Or preferably, <o:p></o:p></pre><pre>because cmor post-processing can last few days for a MIP_TABLE, be <o:p></o:p></pre><pre>assigned to CMOR2.x via an option by the user. This would guarantee that <o:p></o:p></pre><pre>all variables belonging to the same "stream" belongs to the same version <o:p></o:p></pre><pre>number.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>As we all hold the presses waiting for the CMOR2.5 release to continue <o:p></o:p></pre><pre>the production, it could be a good timing to have CMOR2.x compatible <o:p></o:p></pre><pre>with DRS v1.0. Depending on the CMIP5 data distribution system "big <o:p></o:p></pre><pre>opening day" I'm willing to rewrite now what we have to be from the <o:p></o:p></pre><pre>beginning in line with CMOR2.x, DRS v1.0 and publication aspect.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Regards.<o:p></o:p></pre><pre>Sébastien<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal><br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre><pre>Sébastien Denvil<o:p></o:p></pre><pre>IPSL, Pôle de modélisation du climat<o:p></o:p></pre><pre>UPMC, Case 101, 4 place Jussieu,<o:p></o:p></pre><pre>75252 Paris Cedex 5<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Tour 45-55 2ème étage Bureau 209<o:p></o:p></pre><pre>Tel: 33 1 44 27 21 10<o:p></o:p></pre><pre>Fax: 33 1 44 27 39 02<o:p></o:p></pre></div>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></body>
</html>