[Go-essp-tech] Forcings on Historical

[Estanislao Gonzalez]

Hi,

although this is feasible I wouldn't suggest using such a work around. 
We have enough exceptions already if you ask me.

I think the most appropriate path would be for NCI to merge the 
directories together, this could be harder, rename the dataset ids in 
the esgcet DB, which is trivial, and republish from the DB (meaning no 
files will be re-scanned), this should be pretty fast.

I think that mapping the names is possible, but will probably cause more 
problems if the mapping is not done thoroughly (There are other 
historicalXXX experiments that are legal and should not be mapped to 
historicalMisc, etc).

But that's just my opinion,
Estani

Am 30.03.2012 18:46, schrieb Cinquini, Luca (3880):
> Hi Karl,
> Yes we can change them while harvesting... I'll have the patch today 
> or tomorrow, then Gavin will need to reharvest.
> Thanks, Luca
>
>
>
>
> On Mar 30, 2012, at 9:15 AM, "Karl Taylor" <taylor13 at llnl.gov 
> <mailto:taylor13 at llnl.gov>> wrote:
>
>> Hi Estani,
>>
>> Yes, the official name for all of these is historicalMisc, and the 
>> different runs should have been identified by a different "p" value 
>> in the "rip", which distinguishes among members of an ensemble.  The 
>> DRS document describes this in more detail.
>>
>> I *think* these datasets may have been generated prior to the DRS 
>> controlled vocabulary being fully settled, so I haven't raised a 
>> stink about this.  I note that they show up in the old gateway1.3.4 
>> search, but not in the new p2p search.
>>
>> Is there some way that the non-conforming experiment names could be 
>> changed, so that users can find these experiments under historicalMisc?
>>
>> Best regards,
>> Karl
>>
>>
>> On 3/30/12 3:19 AM, Estanislao Gonzalez wrote:
>>> Hi,
>>>
>>> I'm trying to replicate data from CSIRO-QCCCE and I see the following
>>> experiments names:
>>> historicalNoOz
>>> historicalNoAA
>>> historicalAntNoAA
>>> historicalAnt
>>> historicalAA
>>>
>>> These are used as the dataset id, e.g.
>>> cmip5.output1.CSIRO-QCCCE.CSIRO-Mk3-6-0.historicalAA.fx.atmos.fx.r0i0p0
>>>
>>> Shouldn't those be historicalMisc and the forcings detailed within the
>>> global attributes?
>>>
>>> By the way, we are also missing the contact data for CSIRO data node in
>>> the CMIP5 Status Page.
>>>
>>> Thanks,
>>> Estani
>>>
>>>
>> _______________________________________________
>> GO-ESSP-TECH mailing list
>> GO-ESSP-TECH at ucar.edu <mailto:GO-ESSP-TECH at ucar.edu>
>> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech


-- 
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:  gonzalez at dkrz.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20120330/7b60f0e3/attachment.html