[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050513: doubt with filenames



>From:  Gerry Creager n5jxs <address@hidden>
>Organization:  AATLT, Texas A&M University
>Keywords:  200505132137.j4DLbRP3013071 LDM file matching pattern

Hi Gerry,

re:

>Yes, I think so...

The 8th pattern in parenthesis should be '(gz)$' not '(gz$)' (i.e.,
don't include the end of line indicator in the pattern).  Then again,
you could simply list the 'gz' suffix in the FILE value:

        FILE  WMM5v\1-TAM_\2T\3_\4T\5_\6T\7_gz

Also, given your example:

WMM5v370-TAM_yyyymmddThhmm_yyy1m1d1Th100_yyy2m2d2Th200_DOMAIN1_Z.bin.gz

I think you mean to have:

        FILE  WMM5v\1-TAM_\2T\3_\4T\5_\6T\7.gz

or

        FILE  WMM5v\1-TAM_\2T\3_\4T\5_\6T\7.\8

re:
>Date: Fri, 13 May 2005 16:43:01 -0500
>From: "Smith, Matt" <address@hidden>
>To: "Gerry Creager n5jxs" <address@hidden>
>Cc: "Tom Yoksas" <address@hidden>

>I don't really care if it's something shorter.  As long as it's within
>the 9 allowed LDM "variables".  I've never seen an example of using the
>"$".  Will it accomplish my goal in this case?

What exactly is your goal?  The '$' character is special in regular
expressions, it means the end of the string.

Cheers,

Tom

>You're thinking I should not send it as the complete SCOOP filename but 
>with something shorter?  If I understood better how to do arithmatic 
>operations in pqact, I could possibly send the original filename with a 
>product name in pqinsert:-)
>
>the 'normal' MM5 output name would be something like MMOUT_DOMAIN1_04
>
>Tom, I'm thinkin' I'm getting out of my depth on pqact.  If you've 
>comments, let me know, please!
>
>gerry
>
>          $1                            $2                           $3
>^WMM5v|(...)|-TAM_|([1-2][0-9][0-9][0-9][0-1][0-9][0-3][0-9])||([0-2][0-9])|_|(
>                    $4                          $5                    $6
>[0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])||([0-2][0-9])|_|([0-9][0-9][0-9][0
>                                $7         $8
>-9][0-1][0-9][0-3][0-9])||([0-2][0-9])|_|(gz$)|
>
>Smith, Matt wrote:
>> Gerry,
>>     quick question-
>> 
>> Would LDM handle the MM5 SCOOPname like so?
>> 
>> EXP 
>> ^WMM5v(...)-TAM_([1-2][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9])_([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9])_([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9])_(gz$)
>> FILE  WMM5v\1-TAM_\2T\3_\4T\5_\6T\7_\8
>> WMM5v370-TAM_yyyymmddThhmm_yyy1m1d1Th100_yyy2m2d2Th200_DOMAIN1_Z.bin.gz
>> 
>> I know it's a jumble - but the question is about field #8.  Will it find
>> the string ending in "gz" and define it as field #8 (\8) equal to
>> "DOMAIN1_Z.bin.gz"?
>> 
>> Thanks,
>> Matt
>> 
>> Matt Smith 
>> Information Technology & Systems Center 
>> University of Alabama in Huntsville 
>> at the National Space Science and Technology Center 
>> 320 Sparkman Dr. 
>> Huntsville, AL 35805 
>> ph 256-961-7809     fax 256-961-7859 
>> e-mail address@hidden 
>> 
>> 
>> 
>> 
>>>-----Original Message-----
>>>From: Gerry Creager n5jxs [mailto:address@hidden 
>>>Sent: Friday, May 13, 2005 1:57 PM
>>>To: Smith, Matt
>>>Cc: address@hidden
>>>Subject: Re: doubt with filenames
>>>
>>>
>>>.lv2 is still better for the radar displays to differentiate them as 
>>>Level II volume scan data, in my opinion.
>>>
>>>.bin for the MM5 data, at least 'til I start moving it all to 
>>>netCDF...
>>>
>>>I'll make the change
>>>gerry
>>>
>>>Smith, Matt wrote:
>>>
>>>>Yes, good catch.  It needs to have a format type attached.  We 
>>>>mentioned it in the Wed. telecon - and ".lv2" came up - but 
>>>
>>>we didn't 
>>>
>>>>settle anything about it.  I think ".bin" is much better 
>>>
>>>than ".lv2".  
>>>
>>>>".lv2" is descriptive, but not a "format".
>>>>
>>>>Agreed?
>>>>
>>>>If so, I'll change the spreadsheet.
>>>>Matt
>>>>
>>>>Matt Smith
>>>>Information Technology & Systems Center 
>>>>University of Alabama in Huntsville 
>>>>at the National Space Science and Technology Center 
>>>>320 Sparkman Dr. 
>>>>Huntsville, AL 35805 
>>>>ph 256-961-7809     fax 256-961-7859 
>>>>e-mail address@hidden 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: Gerry Creager n5jxs [mailto:address@hidden
>>>>>Sent: Friday, May 13, 2005 1:33 PM
>>>>>To: address@hidden
>>>>>Cc: Smith, Matt
>>>>>Subject: Re: doubt with filenames
>>>>>
>>>>>
>>>>>That filename is in error.  We've been evolving to the right names,
>>>>>which are now like:
>>>>>
>>>>>WMM5v37-TAM_20050511T00_20050511T00_20050511T00_Z_DOMAIN1.gz
>>>>>I'm not putting in the format... but perhaps I have to.  Let
>>>>>me ask Matt 
>>>>>and we will add it as 'bin' if we need to.
>>>>>
>>>>>Thanks! Good catch!
>>>>>gerry
>>>>>
>>>>>Kaustav Ghoshal wrote:
>>>>>
>>>>>
>>>>>>Gerry,
>>>>>>  I found some files in /data1/ldm/SCOOP/TAMU.The names
>>>>>
>>>>>are more or
>>>>>
>>>>>
>>>>>>less like
>>>>>>WMM5-TAM_20050509T0000_20050510T1200_20050510T1600_Z_DOMAIN1.gz
>>>>>>
>>>>>>I see that the ancilliary description field in these atmospheric
>>>>>>forcing model files is missing.Is this an optional 
>>>>>
>>>>>field?From what I
>>>>>
>>>>>
>>>>>>get from the Naming convention writeup,this is a required field.Can
>>>>>>you please clarify.
>>>>>>
>>>>>>~kay
>>>>>>
>>>>>
>>>>>--
>>>>>Gerry Creager -- address@hidden
>>>>>Texas Mesonet -- AATLT, Texas A&M University       
>>>>>Cell: 979.229.5301 Office: 979.458.4020
>>>>>FAX:  979.847.8578 Pager:  979.228.0173
>>>>>Office: 903A Eller Bldg, TAMU, College Station, TX 77843
>>>>>
>>>>
>>>>
>>>-- 
>>>Gerry Creager -- address@hidden
>>>Texas Mesonet -- AATLT, Texas A&M University 
>>>Cell: 979.229.5301 Office: 979.458.4020
>>>FAX:  979.847.8578 Pager:  979.228.0173
>>>Office: 903A Eller Bldg, TAMU, College Station, TX 77843
>>>
>> 
>> 
>
>-- 
>Gerry Creager -- address@hidden
>Texas Mesonet -- AATLT, Texas A&M University   
>Cell: 979.229.5301 Office: 979.458.4020
>FAX:  979.847.8578 Pager:  979.228.0173
>Office: 903A Eller Bldg, TAMU, College Station, TX 77843
Cheers,

Tom
--
+-----------------------------------------------------------------------------+
* Tom Yoksas                                             UCAR Unidata Program *
* (303) 497-8642 (last resort)                                  P.O. Box 3000 *
* address@hidden                                   Boulder, CO 80307 *
* Unidata WWW Service                             http://www.unidata.ucar.edu/*
+-----------------------------------------------------------------------------+


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.