[Go-essp-tech] Status of Gateway 2.0 (another use case)

[Estanislao Gonzalez]

Hi Jennifer,

I'm still not sure how is Lucas change in the API going to help you 
Jennifer. But perhaps it would help me to fully understand your 
requirement as well as your use of wget when using the FTP  protocol.

I presume what you want is to crawl the archive and get file from a 
specific directory structure?
Maybe it would be better if you just describe briefly the procedure 
you've been using for getting the CMIP3 data so we can see what could be 
done for CMIP5.

How did you find out which data was interesting?
How did you find out which files were required to be downloaded?
How did you tell wget to download those files?

We might have already some way of achieving what you want, if we knew 
exactly what that is.

I guess my proposal of issuing:
bash <(wget 
http://p2pnode/wget?experiment=decadal1960&realm=atmos&time_frequency=month&variable=clt 
-qO - | grep -v HadCM3)

was not acceptable to you. But I still don't know exactly why.
It would really help to know what you meant by "elegant use of wget".

Thanks,
Estani


Am 14.12.2011 18:44, schrieb Cinquini, Luca (3880):
> So Jennifer, would having the capability of doing negative searches 
> (model=!CCSM), and generate the corresponding wget scripts, help you ?
> thanks, Luca
>
> On Dec 14, 2011, at 10:38 AM, Jennifer Adams wrote:
>
>> Well, after working from the client side to get CMIP3 and CMIP5 
>> data, I can say that wget is a fine tool to rely on at the core of 
>> the workflow. Unfortunately, the step up in complexity from CMIP3 to 
>> CMIP5 and the switch from FTP to HTTP trashed the elegant use of 
>> wget. No amount of customized wrapper software, browser interfaces, 
>> or pre-packaged tools like DML fixes that problem.
>>
>> At the moment, the burden on the user is embarrassingly high. It's so 
>> easy to suggest that the user should "filter to remove what is not 
>> required" from a downloaded script, but the actual pratice of doing 
>> that in a timely and automated and distributed way is NOT simple! And 
>> if the solution to my problem of filling in the gaps in my incomplete 
>> collection is to go back to clicking in my browser and do the whole 
>> thing over again but make my filters smarter by looking for what's 
>> already been acquired or what has a new version number ... this is 
>> unacceptable. The filtering must be a server-side responsibility and 
>> the interface must be accessible by automated scripts. Make it so!
>>
>> By the way, the version number is a piece of metadata that is not in 
>> the downloaded files or the gateway's search criteria. It appears in 
>> the wget script as part of the path in the file's http location, but 
>> the path is not preserved after the wget is complete, so it is 
>> effectively lost after the download is done. I guess the file's date 
>> stamp would be the only way to know if the version number of the data 
>> file in question has been changed, but I'm not going to write that 
>> check into my filtering scripts.
>>
>> --Jennifer
>>
>>
>> --
>> Jennifer M. Adams
>> IGES/COLA
>> 4041 Powder Mill Road, Suite 302
>> Calverton, MD 20705
>> jma at cola.iges.org <mailto:jma at cola.iges.org>
>>
>>
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> GO-ESSP-TECH mailing list
> 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/20111215/fe9e2e17/attachment-0001.html