<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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;}
@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 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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Dear all,<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 your responses. I concur that it is very important to agree when the QC manager might be able to “relax” the criteria for passing QC-L2. As long
as we document the guidelines and they are clear to QC managers and data providers then I think we are safe. I look forward to hearing the outcomes of the GO-ESSP discussions on this topic.<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">Ag
<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"> go-essp-tech-bounces@ucar.edu
[mailto:go-essp-tech-bounces@ucar.edu] <b>On Behalf Of </b>Karl Taylor<br>
<b>Sent:</b> 29 April 2011 21:53<br>
<b>To:</b> Michael Lautenschlager<br>
<b>Cc:</b> go-essp-tech@ucar.edu<br>
<b>Subject:</b> Re: [Go-essp-tech] Handling missing data in the CMIP5 archive<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Michael,<br>
<br>
I agree we should decide the criteria, and we'll have an opportunity for this at the GO-ESSP meeting.<br>
<br>
Have a good weekend,<br>
Karl<br>
<br>
On 4/29/11 3:10 AM, Michael Lautenschlager wrote: <o:p></o:p></p>
<pre>Hi Karl et al.,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>yes, I agree that we cannot expect all variables from all models and all <o:p></o:p></pre>
<pre>centres. We have to deal with differing completeness for DOI published <o:p></o:p></pre>
<pre>data entities. This is not a problem for DOI data publication because <o:p></o:p></pre>
<pre>each individual DOI points to the description and to the complete list a <o:p></o:p></pre>
<pre>data which is hind this entity.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>But what we should discuss and decide on are the criteria for <o:p></o:p></pre>
<pre>completeness and for the "QC-L2 passed" flag (see Frank's earlier <o:p></o:p></pre>
<pre>response) for accepting data entities in the CMIP5/IPCC-AR5 reference <o:p></o:p></pre>
<pre>data archive and for DOI data publication. This is exactly on of the <o:p></o:p></pre>
<pre>topics I would like to discuss at the ESGF day and during the GO-ESSP <o:p></o:p></pre>
<pre>meeting.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Ag's request rise the question from a theoretical to a practical level <o:p></o:p></pre>
<pre>and we have to agree on a common procedure in order to guarantee <o:p></o:p></pre>
<pre>consistency across archives in QC level assignment and in completeness <o:p></o:p></pre>
<pre>of data entities.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> Best wishes, Michael<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Am 28.04.2011 19:38, schrieb Karl Taylor:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Dear Ag,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>There is another possible way of handling the "missing data" issue. <o:p></o:p></pre>
<pre>I'm not sure that a dataset should be be required to be complete <o:p></o:p></pre>
<pre>(i.e., required to include all time slices) to be considered eligible <o:p></o:p></pre>
<pre>for DOI assignment. That is, we could relax the criteria. Note that <o:p></o:p></pre>
<pre>I don't think we require *all* variables requested within a single <o:p></o:p></pre>
<pre>dataset to be present, so some datasets will indeed be incomplete but <o:p></o:p></pre>
<pre>be eligible for a DOI. I think the QC procedure should be to check <o:p></o:p></pre>
<pre>with the modeling group, and if they can't supply the missing <o:p></o:p></pre>
<pre>time-slices, then we somehow note this flaw in the dataset <o:p></o:p></pre>
<pre>documentation and if other QC checks are passed, assign it a DOI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The criteria for getting a DOI should be that there are no known <o:p></o:p></pre>
<pre>errors in the data itself, and that there are no major problems with <o:p></o:p></pre>
<pre>the metadata. In this case the data will be reliable, and analysts <o:p></o:p></pre>
<pre>will be welcome to use it and publish results, so I think it should be <o:p></o:p></pre>
<pre>assigned a DOI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>What do others think?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre>Karl<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On 4/28/11 3:12 AM, <a href="mailto:ag.stephens@stfc.ac.uk">ag.stephens@stfc.ac.uk</a> wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Dear all,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>At BADC we have come across our first "missing data" issue in the CMIP5 datasets we are ingesting. We have an example of some missing months for a particular set of variables that was revealed when running the QC code from DKRZ.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>It would be very useful for the CMIP5 archive managers to make an authoritative statement about how we should handle missing data time steps in the archive.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I propose the following response when a Data Node receives a dataset in which time steps are missing:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> 1. QC manager (i.e. whoever runs the QC code) informs Data Provider that there is missing data in a dataset (specifying full DRS structure and date range missing).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> 2a. If Data Provider says "no, cannot provide this data" then the affected datasets cannot get a DOI and cannot be part of the "crystallised archive". STOP<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> 2b. Data Provider re-generates files, data is re-ingested, new version is generated, QC is re-run, all is good. STOP<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> 2c. Data Provider cannot re-generate but wants to pass QC - so needs to create the required files full of missing data.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> 3. Data Provider creates missing data files and sends, data re-ingested, new version is generated, QC re-run, all good. STOP<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In cases 2a and 2c it would also be very useful if the dataset is annotated to inform the user which dates have been FILLED with missing data. This would, I believe, be in the QC logs but we might want a more prominent record of this if possible.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Cheers,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Ag<o:p></o:p></pre>
<pre>BADC--<o:p></o:p></pre>
<pre>Scanned by iCritical.<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
</blockquote>
</div>
<br><p>--
<BR>Scanned by iCritical.
</p>
<br></body>
</html>