<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Martin,<div>just to clarify, the CMIP5 output from the CSIRO-Mk3-6-0 AOGCM is not restricted to our modelling group (CSIRO-QCCCE) but available to anyone who registers at the NCI ESG.</div><div><br></div><div>Quite a bit of data has been there since the middle of May, and we have published the amip and 3 historical attribution runs a few weeks ago.</div><div><br></div><div>In the next week or so we should be able to publish the historical and remaining attribution runs at the 3-4 RCP experiments out to 2100. The experiments out to 2300 will take a couple of more months to finish and publish.</div><div><br></div><div>All of our published data has been scrutinised by the QCWrapper, it has been quite beneficial to our efforts and we are using it as a tool to help diagnose experimental design setup with the ACCESS1.0 ESM (my fun is already starting with the post-processing requirements of this late model submission).</div><div><br></div><div>Our specialists at the NCI ESG have experienced difficulty (mostly beyond their control) getting the data accurately published and they expect that some of the issues will be resolved with a future release of the ESG software stack. We are keen to try and replicate our data at PCMDI for data security as well as ensuring that people have easy access to it. We would encourage people to assist our ESG specialists here in Australia as our remoteness often works against us (tyranny of distance even in this "connected" world), for example, no one from Australia was able to attend the recent GO-ESSP meeting in the U.S. to register these challenges.</div><div><br></div><div>Once again, people can obtain CSIRO-Mk3-6-0 data from the NCI ESG <a href="http://esg.nci.org.au/esgcet/home.htm">http://esg.nci.org.au/esgcet/home.htm</a> after a quick registration process.</div><div><br></div><div>Best wishes,</div><div>Mark.<br><div><div>On 14/07/2011, at 7:27 PM, <a href="mailto:go-essp-tech-request@ucar.edu">go-essp-tech-request@ucar.edu</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Send GO-ESSP-TECH mailing list submissions to<br> <a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:go-essp-tech-request@ucar.edu">go-essp-tech-request@ucar.edu</a><br><br>You can reach the person managing the list at<br> <a href="mailto:go-essp-tech-owner@ucar.edu">go-essp-tech-owner@ucar.edu</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of GO-ESSP-TECH digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Searching on forcings in the ESG Gateway (Sylvia Murphy)<br> 2. Re: Update Nodes & Gateways Web Page (<a href="mailto:martin.juckes@stfc.ac.uk">martin.juckes@stfc.ac.uk</a>)<br> 3. Re: Update Nodes & Gateways Web Page (Estanislao Gonzalez)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 13 Jul 2011 13:35:07 -0600<br>From: Sylvia Murphy <<a href="mailto:Sylvia.Murphy@noaa.gov">Sylvia.Murphy@noaa.gov</a>><br>Subject: Re: [Go-essp-tech] Searching on forcings in the ESG Gateway<br>To: "Schmidt, Gavin A. (GISS-6110)" <<a href="mailto:gavin.a.schmidt@nasa.gov">gavin.a.schmidt@nasa.gov</a>><br>Cc: Metafor List <<a href="mailto:metafor@lists.enes.org">metafor@lists.enes.org</a>>, "<a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>"<br> <<a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>><br>Message-ID: <<a href="mailto:7A1A8113-D47D-46F9-8022-D502AAB459CB@noaa.gov">7A1A8113-D47D-46F9-8022-D502AAB459CB@noaa.gov</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>Hi Gavin,<br>You pose some interesting questions here. Alas, some of the people who are best suited to answer them are unavailable this week. I just did not want you to think we were ignoring you. You'll hear from me again once I can get you a coordinated response.<br>Cheers,<br>Sylvia<br>On Jul 8, 2011, at 3:04 PM, Schmidt, Gavin A. (GISS-6110) wrote:<br><br><blockquote type="cite">Hi Sylvia, a couple of thoughts.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">1) are the input variable names part of the controlled vocabulary? If not, there may be some confusion - though this might be mitigated if the search was over the full text and was case-insenstive etc.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2) The reason to search on the forcings is to a) establish whether any specific forcing was used in a specific experiment across the groups. Which 'historical' simulations used ozone depletion? Which RCPs had continuations of solar cycle variability? and b) what experiments can be usefully compared to each other - ie different models' 'historicalMisc' runs with similar forcing sets, or same models' experiments that differ in some small detail in the forcings (i.e. identifying runs with and without indirect aerosol effects).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">3) Forcings can differ within the same experiment even with the same model ('historicalMisc' is the obvious case, but may also occur with other simulations - i.e. we have one set of model runs that include an irrigation component but are otherwise identical). GIven the current set up the only indication of this is through the metafor name of the simulation and the 'forcings' attribute in the netcdf file - neither of which are visible via ESG. This is the biggest issue.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">4) I'm not really sure how well your proposed solution would work in practice though. Perhaps you could work though the cases in points 2 + 3 and demonstrate that it would be clear?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">5) Can we name the button 'Forcings' ? (and make the direct link to the 'forcings' attribute in the netcdf files.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">gavin<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 8, 2011, at 2:49 PM, Sylvia Murphy wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hi Gavin,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">It was a pleasure meeting you at the CCSM workshop a few weeks ago and getting your feedback on the model metadata display within the ESG Gateway. Cecelia and I have been thinking about your comment on being able to search on forcings and would like to bounce off the following with you to ensure we correctly understand your requirement. To do so, I have attached two screen shots. The first screen shot shows the current search interface and the "facets" on the left-hand side that allow the user to narrow a search. The second screen shot shows the current inputs (initial conditions, boundary conditions etc) for a sample CMIP5 simulation.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Would your requirement be met if we added a facet to the search (see figure 1) called Input or Input Condition (let us know if you have a preference) and then listed all of the variables names you see in screen shot 2 as the options to select from in the search itself?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thanks again for your feedback. It is invaluable to us.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Cheers,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Sylvia<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><search.tiff><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><inputs.tiff><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">***********************************<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Sylvia Murphy<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">NESII/CIRES/NOAA Earth System Research Laboratory<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">325 Broadway, Boulder CO 80305<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Email: <a href="mailto:sylvia.murphy@noaa.gov">sylvia.murphy@noaa.gov</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Phone: 303-497-7753<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Fax: 303-497-7649<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">==========<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Gavin Schmidt<br></blockquote><blockquote type="cite">NASA Goddard Institute for Space Studies<br></blockquote><blockquote type="cite">2880 Broadway<br></blockquote><blockquote type="cite">New York, NY 10025<br></blockquote><blockquote type="cite">Tel: 212 678 5627<br></blockquote><blockquote type="cite">Email: <a href="mailto:Gavin.A.Schmidt@nasa.gov">Gavin.A.Schmidt@nasa.gov</a><br></blockquote><blockquote type="cite">URL: <a href="http://www.giss.nasa.gov/staff/gschmidt.html">http://www.giss.nasa.gov/staff/gschmidt.html</a><br></blockquote><blockquote type="cite"><br></blockquote><br>***********************************<br>Sylvia Murphy<br>NESII/CIRES/NOAA Earth System Research Laboratory<br>325 Broadway, Boulder CO 80305<br>Email: <a href="mailto:sylvia.murphy@noaa.gov">sylvia.murphy@noaa.gov</a><br>Phone: 303-497-7753<br>Fax: 303-497-7649<br><br><br><br><br><br><br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 14 Jul 2011 08:17:10 +0000<br>From: <<a href="mailto:martin.juckes@stfc.ac.uk">martin.juckes@stfc.ac.uk</a>><br>Subject: Re: [Go-essp-tech] Update Nodes & Gateways Web Page<br>To: <<a href="mailto:gonzalez@dkrz.de">gonzalez@dkrz.de</a>>, <<a href="mailto:sebastien.denvil@ipsl.jussieu.fr">sebastien.denvil@ipsl.jussieu.fr</a>><br>Cc: <a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>Message-ID:<br> <<a href="mailto:E21FBC3F00D7304687CB46529F9676D7141C98@EXCHMBX01.fed.cclrc.ac.uk">E21FBC3F00D7304687CB46529F9676D7141C98@EXCHMBX01.fed.cclrc.ac.uk</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Hi Estani,<br><br>The short answer to the first question is that is the way that they were set up and some groups don't have resources to carry out regular updates - work in progress.<br><br>Concerning not accepting PKI vs. not generating PKI scripts in the gateway: CCCMA, NCC and CNRM data nodes accept PKI certificates but are published through the PCMDI gateway, so that users are presented with tokenised wget scripts by the gateway. GISS, BCC and PCMDI nodes do not accept PKI scripts.<br><br>There is, incidentally, a data node in Australia as well, with CMIP5 data publuished - but access to data there is still restricted to the modelling group.<br><br>Cheers,<br>Martin<br><br>From: go-essp-tech-bounces@ucar.edu [<a href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>] On Behalf Of Estanislao Gonzalez<br>Sent: 13 July 2011 15:43<br>To: S?bastien Denvil<br>Cc: <a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>Subject: Re: [Go-essp-tech] Update Nodes & Gateways Web Page<br><br>Hi Sebastien,<br><br>I still can't understand why there are data nodes not accepting PKI access. I've asked around but never got any answer.<br><br>What we can do is mark the data node we know has no PKI in place in the list as such. Non marked one are supposed to be working.<br><br>Furthermore I'm not sure if it's really the data node not accepting PKI access or the gateways not configured to provide them while generating the wget script.<br><br>By the way, I'm still not sure which version is around... The latest I've built used the checksums to assure the files were downloaded correctly, are all Gateways using that one?<br><br>Now regarding <a href="http://esgf.org/wiki/Cmip5Status/ArchiveView">http://esgf.org/wiki/Cmip5Status/ArchiveView</a> I've created that page just recently (glad you've found it out ;-). It's a prototype so I might have to tune it a little bit.<br>The main idea is to harvest known Gateways/top level collections for new datasets and building that summary you see (plus the DB we have).<br>Sadly the Gateway API prior to 1.3.1 together with the non conformance to DRS structures make it "unstable" so there are some data nodes that I just can't get information from.<br><br>I'll try to keep evolving it as time permits.<br><br>Thanks,<br>Estani<br><br><br>Am 13.07.2011 16:32, schrieb S?bastien Denvil:<br>Dear all,<br><br>from this page <a href="http://esgf.org/wiki/Cmip5Status">http://esgf.org/wiki/Cmip5Status</a> the <a href="http://esgf.org/wiki/Cmip5Status/ArchiveView">http://esgf.org/wiki/Cmip5Status/ArchiveView</a> page is very useful. Thanks.<br><br>I'm sure it's in the pipeline and I mention it in case it's not:<br>- it would be great if we can have for each datanode a PKI access (yes/no) flag we could refer to.<br><br>All the best.<br>S?bastien<br><br>On 12/07/2011 21:35, Williams, Dean N. wrote:<br>Thanks Bob, Eric, and everyone else for updating the information on the website. We will have network connectivity listed on this site soon.<br><br>Best regards,<br> Dean<br><br><br>Bob Drach On 7/12/11 11:55 AM, "Bob Drach" <<a href="mailto:drach1@llnl.gov">drach1@llnl.gov</a>> wrote:<br>OK, done for the PCMDI nodes. --Bob<br><br><br>On 7/12/11 6:45 AM, "Williams, Dean N." <<a href="mailto:williams13@llnl.gov">williams13@llnl.gov</a>> wrote:<br>Dear Administrators,<br><br> Please update the Nodes & Gateways web page found at: <a href="http://esgf.org/wiki/Cmip5Status">http://esgf.org/wiki/Cmip5Status</a> . For example, if you have updated your test gateway to 1.3.0, please indicate it.<br><br><br>Thanks,<br> Dean<br><br><br><br><br>_______________________________________________<br><br>GO-ESSP-TECH mailing list<br><br>GO-ESSP-TECH@ucar.edu<<a href="mailto:GO-ESSP-TECH@ucar.edu">mailto:GO-ESSP-TECH@ucar.edu</a>><br><br><a href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><br><br><br><br><br>--<br><br>S?bastien Denvil<br><br>IPSL, P?le de mod?lisation du climat<br><br>UPMC, Case 101, 4 place Jussieu,<br><br>75252 Paris Cedex 5<br><br><br><br>Tour 45-55 2?me ?tage Bureau 209<br><br>Tel: 33 1 44 27 21 10<br><br>Fax: 33 1 44 27 39 02<br><br><br><br><br><br>_______________________________________________<br><br>GO-ESSP-TECH mailing list<br><br>GO-ESSP-TECH@ucar.edu<mailto:GO-ESSP-TECH@ucar.edu><br><br>http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br><br><br><br><br>--<br><br>Estanislao Gonzalez<br><br><br><br>Max-Planck-Institut f?r Meteorologie (MPI-M)<br><br>Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre<br><br>Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany<br><br><br><br>Phone: +49 (40) 46 00 94-126<br><br>E-Mail: gonzalez@dkrz.de<mailto:gonzalez@dkrz.de><br><br>--<br>Scanned by iCritical.<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20110714/85c42c15/attachment-0001.html<br><br>------------------------------<br><br>Message: 3<br>Date: Thu, 14 Jul 2011 11:27:28 +0200<br>From: Estanislao Gonzalez <gonzalez@dkrz.de><br>Subject: Re: [Go-essp-tech] Update Nodes & Gateways Web Page<br>To: Eric Nienhouse <ejn@ucar.edu><br>Cc: go-essp-tech@ucar.edu<br>Message-ID: <4E1EB680.5090901@dkrz.de><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>Hi Eric,<br><br>I've sent the script again to gateway-dev. We now have a contrib repo in<br>esgf for "miscellaneous" (And the applause goes to Gavin :-) Thank you<br>very much for this) where I added that file too (under estani/gateway).<br>The repo is in esgf.org/esgf-contrib.git<br><br>I think we should move towards a script that provides both<br>functionalities. Or, better yet, let the gateway store the configured<br>access for every data node that published data to it and use this to set<br>up the script (i.e. add the token to the urls from datanodes that have<br>no PKI in place). The gateway can collect this data "on demand", i.e.<br>when the data node redirect to one of the attribute service. This could<br>also be in the registry, but it will take longer to get there and it<br>currently makes no sense, since those data nodes won't be upgraded to a<br>node-manager version that provides such functionality. Of course the<br>"fall back" solution should be token based, as it is now.<br><br>It does sound "simple" enough to me, but I might have missed something...<br><br>Thanks,<br>Estani<br><br><br>Am 13.07.2011 19:10, schrieb Eric Nienhouse:<br><blockquote type="cite">Hi Estani, All,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Estanislao Gonzalez wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Hi Sebastien,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I still can't understand why there are data nodes not accepting PKI<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">access. I've asked around but never got any answer.<br></blockquote></blockquote><blockquote type="cite">Certain data nodes do not have the "tokenless" (ie. PKI certificate)<br></blockquote><blockquote type="cite">access configured yet. It may simply be a matter of time for these<br></blockquote><blockquote type="cite">data nodes to update. Long ago we all planned to remove token support<br></blockquote><blockquote type="cite">once we had consensus amongst the node data managers to do so.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Now is a good time to revive this discussion IMO.<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">What we can do is mark the data node we know has no PKI in place in<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the list as such. Non marked one are supposed to be working.<br></blockquote></blockquote><blockquote type="cite">Sounds like a good idea to me.<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Furthermore I'm not sure if it's really the data node not accepting<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">PKI access or the gateways not configured to provide them while<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">generating the wget script.<br></blockquote></blockquote><blockquote type="cite">Gateways may be configured to generate WGet scripts with tokens per<br></blockquote><blockquote type="cite">data node service via the Admin UI. This capability is in place to<br></blockquote><blockquote type="cite">allow migration of nodes off the token based auth-z.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">As you know these are short lived tokens and only work for the<br></blockquote><blockquote type="cite">originating gateway's nodes. Though they are simple to use, they are<br></blockquote><blockquote type="cite">limited in capability and will eventually be phased out.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Some gateways are still configured to generate tokens for downloads<br></blockquote><blockquote type="cite">(wget and direct gateway UI download link access). NCAR is currently<br></blockquote><blockquote type="cite">configured in this way even though the NCAR data node also accepts PKI<br></blockquote><blockquote type="cite">certs. We chose to do this to support our current users who are<br></blockquote><blockquote type="cite">familiar with token based access and are primarily accessing CMIP3<br></blockquote><blockquote type="cite">datasets. We're expecting CMIP5 data publication soon, so we're<br></blockquote><blockquote type="cite">reviewing when it would be best to convert fully to PKI based access.<br></blockquote><blockquote type="cite">We'll update the CMIP5 wiki page when we do :-)<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">By the way, I'm still not sure which version is around... The latest<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I've built used the checksums to assure the files were downloaded<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">correctly, are all Gateways using that one?<br></blockquote></blockquote><blockquote type="cite">I don't think all gateways are using this latest script. Could you<br></blockquote><blockquote type="cite">provide it? (Especially in the FreeMarker template format it you have<br></blockquote><blockquote type="cite">it?) Thank you!<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Now regarding http://esgf.org/wiki/Cmip5Status/ArchiveView I've<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">created that page just recently (glad you've found it out ;-). It's a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">prototype so I might have to tune it a little bit.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The main idea is to harvest known Gateways/top level collections for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">new datasets and building that summary you see (plus the DB we have).<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Sadly the Gateway API prior to 1.3.1 together with the non<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">conformance to DRS structures make it "unstable" so there are some<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">data nodes that I just can't get information from.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I'll try to keep evolving it as time permits.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thanks,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Estani<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Am 13.07.2011 16:32, schrieb S?bastien Denvil:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Dear all,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">from this page http://esgf.org/wiki/Cmip5Status the<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">http://esgf.org/wiki/Cmip5Status/ArchiveView page is very useful.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I'm sure it's in the pipeline and I mention it in case it's not:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">- it would be great if we can have for each datanode a PKI access<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">(yes/no) flag we could refer to.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">All the best.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">S?bastien<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On 12/07/2011 21:35, Williams, Dean N. wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks Bob, Eric, and everyone else for updating the information on<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">the website. We will have network connectivity listed on this site<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">soon.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Best regards,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Dean<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Bob Drach On 7/12/11 11:55 AM, "Bob Drach" <drach1@llnl.gov> wrote:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> OK, done for the PCMDI nodes. --Bob<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> On 7/12/11 6:45 AM, "Williams, Dean N." <williams13@llnl.gov><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">wrote:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Dear Administrators,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Please update the Nodes & Gateways web page found at:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> _http://esgf.org/wiki/Cmip5Status_ . For example, if you<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> have updated your test gateway to 1.3.0, please indicate it.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Thanks,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Dean<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH mailing list<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH@ucar.edu<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">S?bastien Denvil<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">IPSL, P?le de mod?lisation du climat<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">UPMC, Case 101, 4 place Jussieu,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">75252 Paris Cedex 5<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Tour 45-55 2?me ?tage Bureau 209<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Tel: 33 1 44 27 21 10<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Fax: 33 1 44 27 39 02<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH mailing list<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH@ucar.edu<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Estanislao Gonzalez<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Max-Planck-Institut f?r Meteorologie (MPI-M)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Phone: +49 (40) 46 00 94-126<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">E-Mail: gonzalez@dkrz.de<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">------------------------------------------------------------------------<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">GO-ESSP-TECH@ucar.edu<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><br><br>--<br>Estanislao Gonzalez<br><br>Max-Planck-Institut f?r Meteorologie (MPI-M)<br>Deutsches Klimarechenzentrum (DKRZ) - German Climate Computing Centre<br>Room 108 - Bundesstrasse 45a, D-20146 Hamburg, Germany<br><br>Phone: +49 (40) 46 00 94-126<br>E-Mail: gonzalez@dkrz.de<br><br><br><br>------------------------------<br><br>_______________________________________________<br>GO-ESSP-TECH mailing list<br>GO-ESSP-TECH@ucar.edu<br>http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br><br><br>End of GO-ESSP-TECH Digest, Vol 29, Issue 30<br>********************************************<br></div></blockquote></div><br></div></body></html>