<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I'm changing the subject so we get back on course :-)<br>
<br>
Indeed URL *will* change, *but* they contain more information that
the filename and you can easily get to the subset of filename +
checksum (just use basename on the url from any UNIX machine).<br>
<br>
Furthermore you could *know* from which server you got the data (a
replica, the original, etc).<br>
<br>
That's why I think the simples is to store just the script or
whatever url list the user got.<br>
As I said, the checksum is enough to identify the file, but people
might also want to find what happened with it... and the extra
information might provide the required clues.<br>
<br>
But yes, as Stephen pointed out there are multiple use cases, I was
thinking about the user. From the server side you could indeed have
"dataset + set(file_name, file_checksum)" as a representation of
that dataset that will be the same for all replicas. I'm missing the
point though, why would you want to do that? Citation? Storage? a
notification service? The URL *should* be:<br>
https?://<host_name>/<service_root>/*DRS_PATH*/*DRS_filename*<br>
<br>
so DRS_PATH (=dataset + version) + DRS_filename + checksum is what
you are proposing. I do think it's enough.<br>
<br>
Regards,<br>
Estani<br>
<br>
<br>
<br>
Am 15.02.2012 15:45, schrieb Kettleborough, Jamie:
<blockquote
cite="mid:E51EDFEBF10BE44BB4BDAF5FC2F024B90FB7FB56@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">
<!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<style>@font-face {
font-family: Helvetica;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; COLOR: black; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
FONT-FAMILY: "Times New Roman","serif"; COLOR: black; MARGIN-LEFT: 0cm; FONT-SIZE: 12pt; MARGIN-RIGHT: 0cm; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
PRE {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Courier New"; COLOR: black; FONT-SIZE: 10pt; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: Consolas; COLOR: black; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.apple-style-span {
mso-style-name: apple-style-span
}
SPAN.EmailStyle20 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle22 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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]-->
<div dir="ltr" align="left"><font color="#0000ff" face="Arial"
size="2"><span class="521404114-15022012">minor point - but
we've seen URLs change too - e.g. pcmdi moved their threeds
from one server to another, and others seem to sometimes do
some sort of data management that means the earlier parts of
the paths in the URL change.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial"
size="2"><span class="521404114-15022012"></span></font> </div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial"
size="2"><span class="521404114-15022012">Jamie</span></font></div>
<br>
<blockquote style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT:
5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<div dir="ltr" class="OutlookMessageHeader" align="left"
lang="en-us">
<hr tabindex="-1"> <font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a> [<a class="moz-txt-link-freetext" href="mailto:stephen.pascoe@stfc.ac.uk">mailto:stephen.pascoe@stfc.ac.uk</a>]
<br>
<b>Sent:</b> 15 February 2012 14:00<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gonzalez@dkrz.de">gonzalez@dkrz.de</a><br>
<b>Cc:</b> Kettleborough, Jamie; <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>
<div class="WordSection1">
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">This
thread is now officially off-topic but, just to pick
Eastani up on one point<o:p></o:p></span></p>
<p class="MsoNormal">> I would say URL + checksum is enough
information (that's more than the filename). The filename
alone it's ok, but you will have to look for the <o:p></o:p></p>
<p class="MsoNormal">> dataset version...<br>
<br>
<span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR:
#1f497d; FONT-SIZE: 11pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I
think we are talking about different use-cases. I'm
imagining a manifest that describes the dataset's contents
at a particular version, independent of it's location and
the name we've given the version. URL + checksum contains
the dataset's location as well as it's contents, in the
case of DRS it also contains the version. Think of the
analogy of a git tree object -- it just contains the names
and hashes of everything in the tree. The URLs will be
different for each replica and I was talking about a
manifest that was the same for all replicas.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">This
is an idea for the future really.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Stephen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">Stephen Pascoe +44
(0)1235 445980<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">Centre of
Environmental Data Archival<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">STFC Rutherford
Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium
none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm;
PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-FAMILY:
'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE:
10pt" lang="EN-US">From:</span></b><span
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR:
windowtext; FONT-SIZE: 10pt" lang="EN-US"> Estanislao
Gonzalez [<a class="moz-txt-link-freetext" href="mailto:gonzalez@dkrz.de">mailto:gonzalez@dkrz.de</a>] <br>
<b>Sent:</b> 15 February 2012 13:04<br>
<b>To:</b> Pascoe, Stephen (STFC,RAL,RALSP)<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:jamie.kettleborough@metoffice.gov.uk">jamie.kettleborough@metoffice.gov.uk</a>;
<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?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi,<br>
<br>
the Tracking_id is generated by cmor, so if the files are
re-concatenated using any other tool (e.g. cdo) then it
should be left as is. This has the benefit of not altering
the checksum and thus marking the file as it is. So
basically a renaming should trigger a new version but should
not alter the files in any other way (i.e. same checksum).<br>
<br>
And indeed Stephen, the checksums alone are "enough" but
it's not practical for any other purposes (until we have a
service to reverse search to files).<br>
I would say URL + checksum is enough information (that's
more than the filename). The filename alone it's ok, but you
will have to look for the dataset version...<br>
<br>
So either dataset_id + version + file_name + checksum or url
+ checksum, which is the general case of the former.<br>
<br>
Url + checksum is already being stored in the wget script,
so that file would be the key for citing/finding files.<br>
My advice: store it together with the data (which I know
most people are doing already). <br>
<br>
...I'm already changing the subject of this thread... sorry
for that.<br>
<br>
Thanks,<br>
Estani<br>
Am 15.02.2012 11:44, schrieb <a moz-do-not-send="true"
href="mailto:stephen.pascoe@stfc.ac.uk:">stephen.pascoe@stfc.ac.uk:</a>
<o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Hi
all,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">This
subject is full of gray areas :-(. I would say keeping
the tracking_id the same is ok as it is an indication that
the contents of the NetCDF hasn't changed.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Practical
matters for CMIP5 aside, I've been thinking about how we
could create an unambiguous manifest of a
dataset-version. I.e. containing enough information to
uniquely identify it's contents without any extraneous
information that might change with dataset location,
available services, etc. . I came to the conclusion
there are 2 possible solutions: either a it's a sorted
list of (filename, checksum) pairs or it's just a sorted
list of checksums. The difference is whether filenames
are "part of the dataset". My instinct is that you can't
decouple filenames from the dataset. Users expect
filenames to be meaningful and in some contexts
information inside files could refer to filenames within
the dataset (e.g. gridspec files). This is how every
other contents-based versioning/packaging system I know of
works: git, BagIt, BitTorrent</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">So,
that's a long way of saying a new version would be
necessary, on theoretical grounds as well as pragmatic
ones.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Cheers,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Stephen.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">---</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">Stephen Pascoe +44
(0)1235 445980</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">Centre of
Environmental Data Archival</span><o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY: Consolas;
COLOR: #1f497d; FONT-SIZE: 10.5pt">STFC Rutherford
Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"> </span><o:p></o:p></p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium
none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm;
PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-FAMILY:
'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE:
10pt" lang="EN-US">From:</span></b><span
style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR:
windowtext; FONT-SIZE: 10pt" lang="EN-US"> <a
moz-do-not-send="true"
href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a moz-do-not-send="true"
href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>]
<b>On Behalf Of </b>Kettleborough, Jamie<br>
<b>Sent:</b> 15 February 2012 10:20<br>
<b>To:</b> Estanislao Gonzalez; <a
moz-do-not-send="true"
href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Subject:</b> Re: [Go-essp-tech] Incorrect file
names?</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Thanks
Estani,</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">do you
have any thoughts on the tracking_id? Should this be left
as is (I think what you say below implies it should).</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Jamie</span><o:p></o:p></p>
<blockquote style="BORDER-BOTTOM: medium none; BORDER-LEFT:
blue 1.5pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt
3.75pt; PADDING-LEFT: 4pt; PADDING-RIGHT: 0cm; BORDER-TOP:
medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<p class="MsoNormal"> <o:p></o:p></p>
<div style="TEXT-ALIGN: center" class="MsoNormal"
align="center"><span lang="EN-US">
<hr align="center" size="2" width="100%"> </span></div>
<p style="MARGIN-BOTTOM: 12pt" class="MsoNormal"><b><span
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE:
10pt" lang="EN-US">From:</span></b><span
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE:
10pt" lang="EN-US"> <a moz-do-not-send="true"
href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a moz-do-not-send="true"
href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>]
<b>On Behalf Of </b>Estanislao Gonzalez<br>
<b>Sent:</b> 15 February 2012 10:06<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Subject:</b> Re: [Go-essp-tech] Incorrect file names?</span><o:p></o:p></p>
<p class="MsoNormal">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: <o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Hello,</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">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.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt">Jamie</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="TEXT-ALIGN: center" class="MsoNormal"
align="center">
<hr align="center" size="2" width="100%"> </div>
<p style="MARGIN-BOTTOM: 12pt" class="MsoNormal"><b><span
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE:
10pt">From:</span></b><span style="FONT-FAMILY:
'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <a
moz-do-not-send="true"
href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Subject:</b> Re: [Go-essp-tech] Incorrect file names?</span><o:p></o:p></p>
<blockquote style="BORDER-BOTTOM: medium none; BORDER-LEFT:
blue 1.5pt solid; PADDING-BOTTOM: 0cm; MARGIN: 5pt 0cm 5pt
3.75pt; PADDING-LEFT: 4pt; PADDING-RIGHT: 0cm; BORDER-TOP:
medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<p class="MsoNormal"><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: <o:p></o:p></p>
<p class="MsoNormal">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.
<o:p></o:p></p>
<div>
<p class="MsoNormal">--Jennifer<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Feb 14, 2012, at 1:29
PM, Laura Carriere wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><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: <o:p></o:p></p>
<p class="MsoNormal">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>
<br>
On 2/13/12 9:30 AM, Jennifer Adams wrote: <o:p></o:p></p>
<div>
<p class="MsoNormal">Dear Experts, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Here is a dataset:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://pcmdi3.llnl.gov/esgcet/dataset/cmip5.output1.NASA-GMAO.GEOS-5.decadal1960.mon.atmos.Amon.r1i1p1.html">http://pcmdi3.llnl.gov/esgcet/dataset/cmip5.output1.NASA-GMAO.GEOS-5.decadal1960.mon.atmos.Amon.r1i1p1.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">And here is the file name
template for all the variables in this
dataset: <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><varname>_Amon_GEOS-5_decadal1960_r1i1p1_19610116-19701216.nc <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">My script to generate a
GrADS descriptor for this file barked
because the MONTHLY data file has time
stamps in the YYYYMMDD format. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">If I have read the DRS
document correctly, this a not a correct
file name. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Shouldn't I be able to
assume that monthly files will have only
YYYYMM date strings? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">--Jennifer<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt">--</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt">Jennifer M.
Adams</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt">IGES/COLA</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt">4041 Powder
Mill Road, Suite 302</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt">Calverton, MD
20705</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt"><a
moz-do-not-send="true"
href="mailto:jma@cola.iges.org">jma@cola.iges.org</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="FONT-SIZE: 9pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> Laura Carriere, SAIC <a moz-do-not-send="true" href="mailto:laura.carriere@nasa.gov">laura.carriere@nasa.gov</a><o:p></o:p></pre>
<pre> NCCS, Code 606.2 301 614-5064<o:p></o:p></pre>
</div>
<p class="MsoNormal">_______________________________________________<br>
GO-ESSP-TECH mailing list<br>
<a moz-do-not-send="true"
href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><br>
<a moz-do-not-send="true"
href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt">--</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt">Jennifer
M. Adams</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt">IGES/COLA</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt">4041
Powder Mill Road, Suite 302</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt">Calverton,
MD 20705</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt"><a
moz-do-not-send="true"
href="mailto:jma@cola.iges.org">jma@cola.iges.org</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Helvetica','sans-serif'; FONT-SIZE: 9pt"><br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> Laura Carriere, SAIC <a moz-do-not-send="true" href="mailto:laura.carriere@nasa.gov">laura.carriere@nasa.gov</a><o:p></o:p></pre>
<pre> NCCS, Code 606.2 301 614-5064<o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" 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>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Estanislao Gonzalez<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Max-Planck-Institut für Meteorologie (MPI-M)<o:p></o:p></pre>
<pre>Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre<o:p></o:p></pre>
<pre>Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Phone: +49 (40) 46 00 94-126<o:p></o:p></pre>
<pre>E-Mail: <a moz-do-not-send="true" href="mailto:gonzalez@dkrz.de">gonzalez@dkrz.de</a> <o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
<p>-- <br>
Scanned by iCritical. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Estanislao Gonzalez<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Max-Planck-Institut für Meteorologie (MPI-M)<o:p></o:p></pre>
<pre>Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre<o:p></o:p></pre>
<pre>Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Phone: +49 (40) 46 00 94-126<o:p></o:p></pre>
<pre>E-Mail: <a moz-do-not-send="true" href="mailto:gonzalez@dkrz.de">gonzalez@dkrz.de</a> <o:p></o:p></pre>
</div>
<br>
<p>-- <br>
Scanned by iCritical. </p>
<br>
</blockquote>
</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>