<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
it's required a new version to be published, so that its publication
will signal that something has changed. If not, then it won't be
picked up by other services, e.g. replica services, as it would
assume the data hasn't been changed at all.<br>
In our particular case (DKRZ) we will see files haven't been
changed, provided that the checksums are properly published, and
will just link them to the older ones, allowing users to get both
versions (i.e. users that are already downloading files will be able
to keep downloading them, and not have to start everything anew
because of this renaming)<br>
(I can't see if the checksums are there because the node is not
accessible at this time)<br>
<br>
We could use that information to infer what happened and display it
under the history information.<br>
<br>
Maintaining the same version provides no benefit for the publisher
at all and creates the same confusion to the user (which will see
that files are missing).<br>
<br>
Just my 2c,<br>
Estani<br>
<br>
Am 15.02.2012 10:29, schrieb Kettleborough, Jamie:
<blockquote
cite="mid:E51EDFEBF10BE44BB4BDAF5FC2F024B90FB7FB46@EXXMAIL02.desktop.frd.metoffice.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19170">
<div dir="ltr" align="left"><span class="920511609-15022012"><font
color="#0000ff" face="Arial" size="2">Hello,</font></span></div>
<div dir="ltr" align="left"><span class="920511609-15022012"></span> </div>
<div dir="ltr" align="left"><span class="920511609-15022012"><font
color="#0000ff" face="Arial" size="2">sorry, a but of a side
track, but maybe useful. I know this is an unusual case -
but it is another example of an understandable slip that can
be made when producing data. When Laura republishes these
should it be under a new publication data set version or
not? I think the only thing that is changing is the
filename - is that right? I don't think this warrants a new
publication data set version, but could be wrong.</font></span></div>
<div dir="ltr" align="left"><span class="920511609-15022012"></span> </div>
<div dir="ltr" align="left"><span class="920511609-15022012"><font
color="#0000ff" face="Arial" size="2">Jamie</font></span></div>
<div dir="ltr" align="left"><span class="920511609-15022012"></span> </div>
<div dir="ltr" align="left">
<hr tabindex="-1">
</div>
<div dir="ltr" align="left"><font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a class="moz-txt-link-freetext" href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>] <b>On Behalf Of </b>Laura
Carriere<br>
<b>Sent:</b> 14 February 2012 19:43<br>
<b>To:</b> Jennifer Adams<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Subject:</b> Re: [Go-essp-tech] Incorrect file names?<br>
</font><br>
</div>
<blockquote style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT:
5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px" dir="ltr"> <br>
Ah, now I see your reply. Since you have a solution to your
immediate problem, I will not rush the republish but will have
it done as soon as it's convenient. Thanks.<br>
<br>
Laura.<br>
<br>
On 2/14/2012 2:32 PM, Jennifer Adams wrote:
<blockquote
cite="mid:703D7639-7DC2-4B2D-BB10-1B677EFD5046@cola.iges.org"
type="cite">Oh dear. Rather than renaming the files, I used a
set of symlinks to solve my immediate problem, but I still
find this a bit troubling. I will have to check all GEOS-5
data files I grab from now on. I asked Larry Marx to check if
any of COLA's CMIP5 data at NASA have 8-digit date stamps, and
he found everything to be correct with only YYYYMM date
strings.
<div>--Jennifer</div>
<div><br>
<div>
<div><br>
<div>
<div>On Feb 14, 2012, at 1:29 PM, Laura Carriere
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000"><br>
Quick answer on my way to a meeting - CMOR2 was
used for this and at least one other dataset that
we have (from COLA) that also has the yyyymmdd
format. I'll ask a few other questions after my
meeting but that's the short answer.<br>
<br>
Laura.<br>
<br>
On 2/14/2012 1:21 PM, Karl Taylor wrote:
<blockquote cite="mid:4F3AA614.7070509@llnl.gov"
type="cite"><font face="Times New Roman">Dear
Novice (with clearly more knowledge than most
so-called experts),<br>
<br>
I'm copying a contact for the GEOS-5 model who
may be able to provide some information on
this. I can't explain why the monthly file
names are inconsistent with what CMOR2 puts
out. Maybe CMOR2 wasn't used. The DRS
document doesn't absolutely forbid including
more precision than necessary in specifying
the time-periods, so I don't think we can
force them to rename their files. That being
said, my hope was everyone would use CMOR, so
the file names would all follow the same
template.<br>
<br>
Karl<br>
</font><br>
On 2/13/12 9:30 AM, Jennifer Adams wrote:
<blockquote
cite="mid:142906E8-DE5A-4F87-A140-E1F95BC8392A@cola.iges.org"
type="cite">
<div>Dear Experts, </div>
<div><br>
</div>
<div>Here is a dataset:</div>
<div><a
href="http://pcmdi3.llnl.gov/esgcet/dataset/cmip5.output1.NASA-GMAO.GEOS-5.decadal1960.mon.atmos.Amon.r1i1p1.html"
moz-do-not-send="true">http://pcmdi3.llnl.gov/esgcet/dataset/cmip5.output1.NASA-GMAO.GEOS-5.decadal1960.mon.atmos.Amon.r1i1p1.html</a></div>
<div><br>
</div>
<div>And here is the file name template for
all the variables in this dataset: </div>
<div>
<div><varname>_Amon_GEOS-5_decadal1960_r1i1p1_19610116-19701216.nc </div>
<div><br>
</div>
<div>My script to generate a GrADS
descriptor for this file barked because
the MONTHLY data file has time stamps in
the YYYYMMDD format. </div>
<div>If I have read the DRS document
correctly, this a not a correct file
name. </div>
<div>Shouldn't I be able to assume that
monthly files will have only YYYYMM date
strings? </div>
<div><br>
</div>
<div>--Jennifer</div>
<div><br>
</div>
<div><br>
</div>
<div apple-content-edited="true"><span
style="FONT-SIZE: 12px"
class="Apple-style-span">
<div>--</div>
<div>Jennifer M. Adams</div>
<div>IGES/COLA</div>
<div>4041 Powder Mill Road, Suite 302</div>
<div>Calverton, MD 20705</div>
<div><a href="mailto:jma@cola.iges.org"
moz-do-not-send="true">jma@cola.iges.org</a></div>
<div><br class="khtml-block-placeholder">
</div>
<br class="Apple-interchange-newline">
</span></div>
<br>
</div>
</blockquote>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Laura Carriere, SAIC <a class="moz-txt-link-abbreviated" href="mailto:laura.carriere@nasa.gov" moz-do-not-send="true">laura.carriere@nasa.gov</a>
NCCS, Code 606.2 301 614-5064</pre>
</div>
_______________________________________________<br>
GO-ESSP-TECH mailing list<br>
<a href="mailto:GO-ESSP-TECH@ucar.edu"
moz-do-not-send="true">GO-ESSP-TECH@ucar.edu</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><br>
</blockquote>
</div>
<br>
<div apple-content-edited="true"><span style="WIDOWS: 2;
TEXT-TRANSFORM: none; TEXT-INDENT: 0px;
BORDER-SPACING: 0px; BORDER-COLLAPSE: separate;
FONT: 12px Helvetica; WHITE-SPACE: normal; ORPHANS:
2; LETTER-SPACING: normal; COLOR: rgb(0,0,0);
WORD-SPACING: 0px" class="Apple-style-span"><span
style="WIDOWS: 2; TEXT-TRANSFORM: none;
TEXT-INDENT: 0px; BORDER-SPACING: 0px;
BORDER-COLLAPSE: separate; FONT: 12px Helvetica;
WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING:
normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px"
class="Apple-style-span"><span style="WIDOWS: 2;
TEXT-TRANSFORM: none; TEXT-INDENT: 0px;
BORDER-SPACING: 0px; BORDER-COLLAPSE: separate;
FONT: 12px Helvetica; WHITE-SPACE: normal;
ORPHANS: 2; LETTER-SPACING: normal; COLOR:
rgb(0,0,0); WORD-SPACING: 0px"
class="Apple-style-span">
<div>--</div>
<div>Jennifer M. Adams</div>
<div>IGES/COLA</div>
<div>4041 Powder Mill Road, Suite 302</div>
<div>Calverton, MD 20705</div>
<div><a href="mailto:jma@cola.iges.org"
moz-do-not-send="true">jma@cola.iges.org</a></div>
<div><br class="khtml-block-placeholder">
</div>
<br class="Apple-interchange-newline">
</span></span></span></div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Laura Carriere, SAIC <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:laura.carriere@nasa.gov">laura.carriere@nasa.gov</a>
NCCS, Code 606.2 301 614-5064</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Estanislao Gonzalez
Max-Planck-Institut für Meteorologie (MPI-M)
Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre
Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany
Phone: +49 (40) 46 00 94-126
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:gonzalez@dkrz.de">gonzalez@dkrz.de</a> </pre>
</body>
</html>