[Go-essp-tech] ESGF Telco today 2010/09/07

[Drach, Bob]

All,

I'm happy with adding cmor_table as another DRS field. This is a cleaner
solution, and easier to implement in the publisher than combining variable
and table.

As far as ordering goes, I would suggest that cmor_table follow realm, since
in every case but one (6hrLev | 6hrPlev) the cmor_table can be inferred from
the combination of frequency and realm. This would make the ordering:

cmip5/<product>/<institution>/<model>/<experiment>/<frequency>/<realm>/<cmor
_table>/<ensemble>/<version>/<variable>/<file>

Regards,

Bob


On 9/8/10 10:55 PM, "Martina Stockhause" <martina.stockhause at zmaw.de> wrote:

> Dear Karl, dear all,
> 
> the last suggestion was Gavin's in the discussion. We will implement
> that in the QCWrapper unless anyone has objections against it.
> 
> cmip5/<product>/<institution>/<model>/<experiment>/<frequency>/<realm>/<ensemb
> le>/<version>/<variable>/<cmor2_table>/<file>
> 
> Thanks for the clarification !
> 
> Best wishes,
> Martina
> 
> 
> Karl Taylor wrote:
>>  Dear all,
>> 
>> We probably shouldn't spend any more time on this.   Either proposed
>> solution seems to solve the probelm, so maybe we go with "group
>> think", unless someone can point out some practical implication that
>> that choice will make more work for someone (especially the users of
>> the archive).
>> 
>> best regards,
>> Karl
>> 
>> On 9/8/10 10:34 AM, Gavin M. Bell wrote:
>>> Suggestion....
>>> 
>>> Hi Stephen,
>>> 
>>> Can you please make the second to last token, namely:
>>> <variable>_<table>, be like the other tokens in the taxonomy.
>>> Specifically make it <variable>/<table>.  When parsing this, it makes
>>> it a bit difficult to look for this new delimiter.  It complicates
>>> things a bit.  Does it also mean that "_" are not allowed as a
>>> character in any of the other bits of the taxonomy.  The regex
>>> becomes a real pain and "regular" parsing is even worse.  It would
>>> make everything quite a bit simpler if it was like the others. i.e.
>>> 
>>> cmip5/<product>/<institution>/<model>/<experiment>/<frequency>/<realm>/<ense
>>> mble>/<version>/<variable>/<table>/<file>
>>> 
>>> Furthermore, is this structure saying that we are always going to be
>>> using "cmip5" as the root of this taxonomy?
>>> 
>>> Please let me know your thoughts.  If you can accommodate this it
>>> would be great!
>>> 
>>> On 9/7/10 3:17 AM, stephen.pascoe at stfc.ac.uk wrote:
>>>> Today we plan to discuss the DRS directory structure and
>>>> prerequisites for starting replication tests between DKRZ and BADC.
>>>> I am putting together an agenda at the link below, it's still
>>>> evolving but comments welcome.  Telephone details are also below.
>>>> Thanks,
>>>> Stephen
>>>> *Agenda:
>>>> *http://***proj.badc.rl.ac.uk/go-essp/wiki/CMIP5/Meetings/telco100907
>>>> *Telco details:*
>>>> 16:00 BST, 17:00 CEST, 8:00 PDT, 9:00 MDT, 11:00 EDT.
>>>> +01 (925) 424-8105 access code 305757#
>>>> ---
>>>> Stephen Pascoe  +44 (0)1235 445980
>>>> British Atmospheric Data Centre
>>>> Rutherford Appleton Laboratory
>>>> 
>>>> -- 
>>>> Scanned by iCritical.
>>>> 
>>>> 
>>> 
>>> -- 
>>> Gavin M. Bell
>>> Lawrence Livermore National Labs
>>> -- 
>>> 
>>>   "Never mistake a clear view for a short distance."
>>>                    -Paul Saffo
>>> 
>>> (GPG Key -http://**rainbow.llnl.gov/dist/keys/gavin.asc)
>>> 
>>>   A796 CE39 9C31 68A4 52A7  1F6B 66B7 B250 21D5 6D3E
>> 
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> GO-ESSP-TECH mailing list
>> GO-ESSP-TECH at ucar.edu
>> http://*mailman.ucar.edu/mailman/listinfo/go-essp-tech
>>