[Go-essp-tech] Incorrect file names?

[Kettleborough, Jamie]

Hello,
 
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.
 
Jamie
 
________________________________

From: go-essp-tech-bounces at ucar.edu
[mailto:go-essp-tech-bounces at ucar.edu] On Behalf Of Laura Carriere
Sent: 14 February 2012 19:43
To: Jennifer Adams
Cc: go-essp-tech at ucar.edu
Subject: Re: [Go-essp-tech] Incorrect file names?




	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.
	
	  Laura.
	
	On 2/14/2012 2:32 PM, Jennifer Adams wrote: 

		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.  
		--Jennifer


		On Feb 14, 2012, at 1:29 PM, Laura Carriere wrote:



			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.
			
			  Laura.
			
			On 2/14/2012 1:21 PM, Karl Taylor wrote: 

				Dear Novice (with clearly more knowledge
than most so-called experts),
				
				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.
				
				Karl
				
				On 2/13/12 9:30 AM, Jennifer Adams
wrote: 

				Dear Experts, 

				Here is a dataset:
	
http://pcmdi3.llnl.gov/esgcet/dataset/cmip5.output1.NASA-GMAO.GEOS-5.dec
adal1960.mon.atmos.Amon.r1i1p1.html

				And here is the file name template for
all the variables in this dataset: 
	
<varname>_Amon_GEOS-5_decadal1960_r1i1p1_19610116-19701216.nc 

				My script to generate a GrADS descriptor
for this file barked because the MONTHLY data file has time stamps in
the YYYYMMDD format. 
				If I have read the DRS document
correctly, this a not a correct file name. 
				Shouldn't I be able to assume that
monthly files will have only YYYYMM date strings? 

				--Jennifer


				
				--
				Jennifer M. Adams
				IGES/COLA
				4041 Powder Mill Road, Suite 302
				Calverton, MD 20705
				jma at cola.iges.org






			-- 
			
			  Laura Carriere, SAIC
laura.carriere at nasa.gov
			  NCCS, Code 606.2		       301
614-5064
			_______________________________________________
			GO-ESSP-TECH mailing list
			GO-ESSP-TECH at ucar.edu
	
http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
			


		
		--
		Jennifer M. Adams
		IGES/COLA
		4041 Powder Mill Road, Suite 302
		Calverton, MD 20705
		jma at cola.iges.org






	-- 
	
	  Laura Carriere, SAIC                 laura.carriere at nasa.gov
	  NCCS, Code 606.2		       301 614-5064

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20120215/46d53a1f/attachment.html