<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffcc">
Stephen, et. al.<br>
<br>
First things first.<br>
<br>
And the first of the first things is introducing the system on
Tuesday.<br>
We can than peruse the matrix.<br>
We move forward by outlining the next steps.<br>
We get the system in front of more eyes and collect feedback, etc...
<br>
Begin utilizing the channels of communication.<br>
i.e. Posting information, etc...<br>
...<br>
Grow the system.<br>
Make CMIP5 a huge success!!!!!!!! :-)<br>
<br>
The matrix you, Stephen, have come up with is a good starting point
for a discussion, though it is not the whole story nor the sole
metric to be used as we move forward, I am sure this was the
intention. No system is perfect but a good foundation is key.<br>
<br>
(rest of response below)<br>
<br>
On 1/21/12 5:31 AM, <a class="moz-txt-link-abbreviated" href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a> wrote:
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Briefly getting back to the Agenda for Tuesday.
I can make an extended 2 hour telco but the order we do
things in will depend on who can attend 9-10 PTD. That is
6-7pm CET so people from DKRZ, IPSL, SMI etc. may not be
able to make it. As well as the requirements matrix I'd
like to cover setting up a scientific feedback panel as
suggested by Cecelia and supported by Balaji.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Inline comments follow, reordered for relevance.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<pre>> 2. Have the metrics discussion from 9-10.<o:p></o:p></pre>
<p class="MsoNormal">> What kind of metrics?<span
style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">I think Cecelia means the requirements matrix aka
spreadsheet I circulated<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
</div>
</blockquote>
oh... ok<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<pre>> Bonus points:<o:p></o:p></pre>
<pre>> 8. Get together a management body with key stakeholders so that decisions are backed up and can be <o:p></o:p></pre>
<pre>> communicated more easily.<o:p></o:p></pre>
<pre>><o:p> </o:p></pre>
<p class="MsoNormal">> Nod, the governance structure will be
formalized and posted.... among other things<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Gavin, who are the stakeholders going to be?
This decision should be the result of a dialog under the
auspices of GO-ESSP not just "posted".<o:p></o:p></span></p>
</div>
</blockquote>
Dean is the GO-ESSP P.I. he is where that process starts.<br>
And ultimately... yes, at this stage, things get initially,
"posted". <br>
Refinement is another story.<br>
(I am waving my hands on the details since Dean is running point on
that)<br>
more later....<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<pre>> 3. Start putting together a list of users whose input you think would be useful. This is a good idea even <o:p></o:p></pre>
<pre>> if they only ever end up reviewing the p2p system.<o:p></o:p></pre>
<p class="MsoNormal">> Here at PCMDI we have had a handful of
key scientists looking at, using and critiquing the P2P system
we are participating in
<o:p></o:p></p>
<p class="MsoNormal">> building. The feedback they provided
has been driving most of the changes that have been made and
the overall direction of the
<o:p></o:p></p>
<p class="MsoNormal">> development, as they should. They
continue to review and give feedback that we triage and
address.<br>
<span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Well, clearly some "key" CMIP5 scientists are
feeling left out of this process. I think Cecelia's idea is
excellent and we should act on it. The requirements matrix
has had input from the UK Met Office and I'm confident they
would like to be involved in something like a feedback
panel.<o:p></o:p></span></p>
</div>
</blockquote>
Everyone can play... the ultimate goal is to get it in front of
*everybody*. The resources I mentioned at PCMDI are just an example
as they are my "local" resources, but certainly it is not limited to
just them.<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">We should give credit to the P2P team that they
are putting together plenty of documentation on the ESGF
wiki and the bug tracker is working well for developers -- I
doubt many users know about it though! Gavin is right that
keeping the federation status up to date manually is
difficult and arduous. The P2P status system will make a
big difference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
</div>
</blockquote>
There indeed will be an education campaign to let folks know about
the system. But first we must birth this system that we have been
pregnant with for the last 18 months! :-).<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">However the content on esgf.org is developer
focussed. Scientists and data managers at the CMIP5
modelling centres are having to struggle with the current
system and feel the ground shifting under their feet without
any say in what's going on. If PCMDI want to deploy the P2P
system within weeks then the wider CMIP5 users, not just
those at PCMDI, need to be involved. Their work is
critically dependent on what system we put in place.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
</div>
</blockquote>
Yes, esgf.org is developer centric as it is a site about the ESGF
P2P System, nothing more. There are other sites for CMIP directly
that will address scientists' concerns more directly (Ex:
<a class="moz-txt-link-freetext" href="http://www-pcmdi.llnl.gov/">http://www-pcmdi.llnl.gov/</a>).<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<pre>> 4. Update the PCMDI gateway so that it is at least to 1.3.4<o:p></o:p></pre>
<pre>> and is in the best shape it can be given the circumstances.<o:p></o:p></pre>
<p class="MsoNormal">> I think this has been done.<br>
<span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">I thought it had too but it says "1.3.2" on
pcmdi3 right now.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
</div>
</blockquote>
Hmmm... I don't know the details on that effort...<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal">> We will also be using the website,
our blog, twitter page (I know... I know...), and RSS feed
notification as conduits for
<o:p></o:p></p>
<p class="MsoNormal">> disseminating information (news,
updates, etc.) to the community.
<br>
<span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">What Gavin is hinting at here is that the ESGF
blog has been a shell since the beginning. It's been there
some 2 years but never had more than a couple of posts on
it. I know where he's coming from here: for developers it's
a lot more fun to setup a blog than keep it current and
Gavin has a lot on his shoulders. I think this illustrates
that organising ESGF should involve a broader range of
people than the core developers. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"> </span></p>
</div>
</blockquote>
Certainly.... The blog and these other conduits have had a dearth
of information (except the wiki) because we have not yet been
introduced to the larger community, so there really isn't any
audience for them yet. It is the small community on this list, etc
that make up the initial group this project is born from. Indeed
the entire idea is for this project to grow flourish. I don't
intend to be the only content provider for this project. Clearly,
as we have seen with the wiki, many people contribute and the idea
is for many more to do so. The more folks join and *participate*
the more time I or others would have to add to a blog, etc....<br>
<br>
All things in due time. First things, first.<br>
<br>
P.S. Setting up a blog or any of this support infrastructure is not
what I call "fun", at times it is a down right drag, but it has
gotta get done. There is a bit more infrastructure 'stuff' that
will be put in place shortly to round out all the necessary
apparatus to support development and collaboration and growth.<br>
<blockquote
cite="mid:4C353E6E4A08AE4792B350DAA392B5211C980313@EXCHMBX01.fed.cclrc.ac.uk"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Thanks for your attention,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Stephen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">Stephen
Pascoe +44 (0)1235 445980<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">Centre of
Environmental Data Archival<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Consolas; color: rgb(31, 73, 125);">STFC
Rutherford Appleton Laboratory, Harwell Oxford, Didcot
OX11 0QX, UK<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0cm 0cm;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;" lang="EN-US">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;" lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech-bounces@ucar.edu">go-essp-tech-bounces@ucar.edu</a>
[<a class="moz-txt-link-freetext" href="mailto:go-essp-tech-bounces@ucar.edu">mailto:go-essp-tech-bounces@ucar.edu</a>] <b>On Behalf Of
</b>Gavin M. Bell<br>
<b>Sent:</b> 21 January 2012 09:00<br>
<b>To:</b> Cecelia DeLuca<br>
<b>Cc:</b> Cinquini, Luca (3880); <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Subject:</b> Re: [Go-essp-tech] Plan<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Cecilia et. al.<br>
<br>
On 1/20/12 1:56 PM, Cecelia DeLuca wrote: <o:p></o:p></p>
<pre>Thanks Luca.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Here is a plan. I recognize that it is stupid and probably<o:p></o:p></pre>
<pre>counterproductive to continue making suggestions. Unfortunately<o:p></o:p></pre>
<pre>that does not seem to stop me. I think these things should<o:p></o:p></pre>
<pre>not be put off and would not take very long.<o:p></o:p></pre>
<p class="MsoNormal">No no no... not at all... certainly it is
never stupid and not counterproductive (especially coming from
you).<br>
Your plan is clearly cogent and sound - the devil is in the
details. I <i>tried</i> to not mince too finely on points in
the interleaved response below. Many of the items in this
plan are well underway and others are burgeoning. It is
always good to have a plan. :-)<br>
<br>
<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre>1. Do the ESGF demo next Tues from 8-9.<o:p></o:p></pre>
<p class="MsoNormal">nod<br>
<br>
<o:p></o:p></p>
<pre>2. Have the metrics discussion from 9-10.<o:p></o:p></pre>
<p class="MsoNormal">What kind of metrics? (pardon if this is a
silly question - just want clarification "metrics" means many
things to many people)<br>
Or, do you mean matrix?<br>
<br>
<o:p></o:p></p>
<pre>3. Start putting together a list of users whose input<o:p></o:p></pre>
<pre>you think would be useful. This is a good idea even if they<o:p></o:p></pre>
<pre>only ever end up reviewing the p2p system.<o:p></o:p></pre>
<p class="MsoNormal">Here at PCMDI we have had a handful of key
scientists looking at, using and critiquing the P2P system we
are participating in building. The feedback they provided has
been driving most of the changes that have been made and the
overall direction of the development, as they should. They
continue to review and give feedback that we triage and
address.<br>
<br>
<o:p></o:p></p>
<pre>4. Update the PCMDI gateway so that it is at least to 1.3.4<o:p></o:p></pre>
<pre>and is in the best shape it can be given the circumstances.<o:p></o:p></pre>
<p class="MsoNormal">I think this has been done.<br>
<br>
<o:p></o:p></p>
<pre>5. Update the wiki on the ESGF site so that the<o:p></o:p></pre>
<pre>status of all gateways and nodes is current.<o:p></o:p></pre>
<p class="MsoNormal">Yes, we should have a way to view the
overall federation status, but I am not convinced that the
manual task of updating a wiki is quite the best use of
resources and time. In terms of the P2P system, the mechanics
of the system itself would obviate this kind of manual
reporting. Not to mince things too finely... yes, indeed
having this information would be useful.<br>
<br>
<o:p></o:p></p>
<pre>6. Identify people and a schedule for periodically testing the<o:p></o:p></pre>
<pre>status of the federation and keeping that status on the<o:p></o:p></pre>
<pre>wiki up to date. Create a minimum set of federation-level<o:p></o:p></pre>
<pre>tests and post them. This can be really minimal but it<o:p></o:p></pre>
<pre>is important to start and create a routine. Useful both<o:p></o:p></pre>
<pre>now and later.<o:p></o:p></pre>
<p class="MsoNormal">As mentioned, there is a small group of
testers, both programmers and scientists - certainly we can
and
<b>will</b> expand the group of test (vanguard) users. Luca
has put together documentation on the minimal set of
federation tests as you mentioned. Also, there will be a
series of automated tests that should provide a baseline for
the system mechanics. John has been emphasizing testing and
is establishing a testing working group to focus on addressing
this issue.<br>
<br>
The idea is that everyone should use the system and post bugs
when they find them. And even better yet fix them ;-). IMHO
- First things first... it is key to have a core from which to
grow. This core is what has been established and to be
demonstrated (the ESGF P2P Node Stack).<br>
<br>
<o:p></o:p></p>
<pre>7. Create a website where known bugs of the production system<o:p></o:p></pre>
<pre>that affect users are listed, in terms that users<o:p></o:p></pre>
<pre>can understand. Make users aware of it.<o:p></o:p></pre>
<p class="MsoNormal">nod<br>
Currently we are using our bug tracking system (<a
moz-do-not-send="true" href="http://esgf.org/bugzilla/">http://esgf.org/bugzilla/</a>)
and mailing lists (esgf-node-dev, esgf-node-user) to get
feedback from users.<br>
We will also be using the website, our blog, twitter page (I
know... I know...), and RSS feed notification as conduits for
disseminating information (news, updates, etc.) to the
community.
<br>
<br>
<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre>Bonus points:<o:p></o:p></pre>
<pre>8. Get together a management body with key stakeholders so<o:p></o:p></pre>
<pre>that decisions are backed up and can be communicated more<o:p></o:p></pre>
<pre>easily.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<p class="MsoNormal">Nod, the governance structure will be
formalized and posted.... among other things.<br>
<br>
<o:p></o:p></p>
<pre>Maybe some of this is already done. (Going to hide now.)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<p class="MsoNormal">nod<br>
<br>
<o:p></o:p></p>
<pre>Cecelia<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>ps. I looked up polemicize and tried not to.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<p class="MsoNormal">:-)<br>
I personally don't eschew polemics, such engagements can lead
to quite fruitful ends - though they do require a thick skin.<br>
<br>
As I mentioned... first things first... and that is to meet on
Tuesday and introduce the P2P system to the go-essp community
(again).... then we go from there. IMHO<br>
<br>
<o:p></o:p></p>
<pre>On 1/20/2012 11:37 AM, Cinquini, Luca (3880) wrote:<o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Hi Cecilia,<o:p></o:p></pre>
<pre> certainly, as we discussed many times, feedback from users if of the outmost important, and being responsive to the that feedback is even more important:)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This can take the form of scientists that use the system and offer their suggestions freely, or of a formal users review board for ESGF. We probably need both. And off course developers<o:p></o:p></pre>
<pre>need to estimate what is possible and what's not, and in which time frame. So we should devote some of the future GO-ESSP calls to put something like this in place. Looks like a busy few months ahead..<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>thanks, Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 20, 2012, at 11:26 AM, Cecelia DeLuca wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Luca, maybe I'm wrong but this list seems overwhelmingly populated by<o:p></o:p></pre>
<pre>developers,<o:p></o:p></pre>
<pre>not by scientist users.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>It would be good to get an "external" scientist user group together.<o:p></o:p></pre>
<pre>Jennifer and<o:p></o:p></pre>
<pre>Gary are a start, but it also seems important to include some scientists<o:p></o:p></pre>
<pre>who are not as<o:p></o:p></pre>
<pre>closely tied to infrastructure as the folks who would normally show up here.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I do think that, as tough as it might be, Stephen's list also needs to<o:p></o:p></pre>
<pre>be reviewed by<o:p></o:p></pre>
<pre>developers. That discussion must be concerned with not just the current<o:p></o:p></pre>
<pre>state of the system, which<o:p></o:p></pre>
<pre>is what users see, but also the future of the system, and developers are<o:p></o:p></pre>
<pre>best positioned<o:p></o:p></pre>
<pre>to comment on that.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-- Cecelia<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On 1/20/2012 10:12 AM, Cinquini, Luca (3880) wrote:<o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Hi Gary,<o:p></o:p></pre>
<pre> I think everybody on this list is invited - just like it happened for the previous one. I hope you can be there :).<o:p></o:p></pre>
<pre>thanks, Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 20, 2012, at 9:58 AM, Gary Strand wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>How many users of the overall system, outside of the developers, have been invited to these demos?<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Fri Jan 20, 2012, at 9:57 AM, Sylvia Murphy wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre>Hi Everyone,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>It seems to me that this decsion is not going to be made through demos, but by a careful analysis of the criteria for CMIP5 and how each software stack stands up to that criteria.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>We need an evaluation and testing strategy, preferably involving key stakeholders who can safely examine both packages.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Deciding on how to do this, the timelines etc seems to me to be our highest priority.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>2 cents<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Sylvia<o:p></o:p></pre>
<pre>On Fri, Jan 20, 2012 at 9:49 AM, Cinquini, Luca (3880)<a moz-do-not-send="true" href="mailto:Luca.Cinquini@jpl.nasa.gov"><Luca.Cinquini@jpl.nasa.gov></a> wrote:<o:p></o:p></pre>
<pre>Hi Stephen,<o:p></o:p></pre>
<pre> I think it will be extremely important to give P2P and Gateway 2.0 the exact same amount of time to showcase their capabilities, otherwise how is CMIP5 going to make an informed decision ?<o:p></o:p></pre>
<pre>Yes, P2P has been demonstrated one time before, but the gateway has been demoed many more times. So I beg to disagree with you... off course, ultimately the decision of what the agenda should be lies with the GO-ESSP PIs.<o:p></o:p></pre>
<pre>thanks, Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 20, 2012, at 9:41 AM,<a moz-do-not-send="true" href="mailto:stephen.pascoe@stfc.ac.uk"><stephen.pascoe@stfc.ac.uk></a> wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom:
5pt;">
<pre>Hi Luca,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I really don't think this is a good use of time. I know P2P is improving all the time but I've seen a number of demos now. It would be more effective to go through the matrix and you describe how P2P meets the requirements or how you plan to meet them.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Depending on who's on the call, we may be in a position to discuss the GW2/P2P deployment strategy for CMIP5 in more detail. Therefore, I wouldn't want to schedule something that is likely to take up most of the hour.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Stephen.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>---<o:p></o:p></pre>
<pre>Stephen Pascoe +44 (0)1235 445980<o:p></o:p></pre>
<pre>Centre of Environmental Data Archival<o:p></o:p></pre>
<pre>STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: Cinquini, Luca (3880) [<a moz-do-not-send="true" href="mailto:Luca.Cinquini@jpl.nasa.gov">mailto:Luca.Cinquini@jpl.nasa.gov</a>]<o:p></o:p></pre>
<pre>Sent: 20 January 2012 14:29<o:p></o:p></pre>
<pre>To: Eric Nienhouse<o:p></o:p></pre>
<pre>Cc: Pascoe, Stephen (STFC,RAL,RALSP); <a moz-do-not-send="true" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><o:p></o:p></pre>
<pre>Subject: Re: [Go-essp-tech] CMIP5 Web interface requirements matrix<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Hi Stephen,<o:p></o:p></pre>
<pre> thanks for the matrix...<o:p></o:p></pre>
<pre>I would like to suggest that we start with a full demo of the P2P system on Tuesday. The gateway 2.0 demo took a full hour - we will try to make the P2P demo shorter, but if it ends up taking a full hour, we can always discuss the matrix at the next call.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>thanks, Luca<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Jan 20, 2012, at 7:23 AM, Eric Nienhouse wrote:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom:
5pt;">
<pre>Hi Stephen,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thank you for this latest version of the matrix. It will be good to<o:p></o:p></pre>
<pre>discuss it further on Tuesday. I would like to understand the ranking<o:p></o:p></pre>
<pre>numbers and planned evaluation process and hope this is something we can<o:p></o:p></pre>
<pre>address on the call.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Attached is an update to the previous version I was just about to send<o:p></o:p></pre>
<pre>as your recent email arrived. Please note 4 highlighted rows. (2 fall<o:p></o:p></pre>
<pre>in the non-functional category.) I trust they can be incorporated and<o:p></o:p></pre>
<pre>discussed.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Indeed the CMIP5 system(s) are under continued development and<o:p></o:p></pre>
<pre>enhancement and the matrix inherently has some relation to the<o:p></o:p></pre>
<pre>architectural choices up to this point. Sticking with the current<o:p></o:p></pre>
<pre>replication section for the time being seems appropriate.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-Eric<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a> wrote:<o:p></o:p></pre>
<blockquote style="margin-top: 5pt; margin-bottom:
5pt;">
<pre>Dear all,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I have merged Luca's suggestions into the CMIP5 GUI requirements<o:p></o:p></pre>
<pre>matrix and reorganised it substantially. Apart from those items that<o:p></o:p></pre>
<pre>are architecture-specific I include most of them, sometimes under a<o:p></o:p></pre>
<pre>different section.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I'm aware there are some architectural assumptions embedded in this<o:p></o:p></pre>
<pre>sheet. For instance, there has been a recent discussion about whether<o:p></o:p></pre>
<pre>master/replica is the right model for depicting replicas. It's a pity<o:p></o:p></pre>
<pre>we're having this discussion now! For the moment I've kept the<o:p></o:p></pre>
<pre>replication section as-is.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>All scores are my opinion based on variable information. Sometimes<o:p></o:p></pre>
<pre>I've assumed something works or is planned in P2P without verifying<o:p></o:p></pre>
<pre>it, sometimes I've assumed it doesn't after a quick test. Where there<o:p></o:p></pre>
<pre>is a "?" anywhere it would be really useful for the developers to<o:p></o:p></pre>
<pre>contribute. To this end I'd like to go through the sheet on Tuesday,<o:p></o:p></pre>
<pre>or make a start at least, so that I can clarify what some items mean.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I know a lot of water has flowed under the bridge since I started this<o:p></o:p></pre>
<pre>process. No matter what strategic decisions the CMIP5 cores centres<o:p></o:p></pre>
<pre>take on our future deployments I hope this matrix will be useful in<o:p></o:p></pre>
<pre>focusing on the core CMIP5 requirements.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Stephen.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>---<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Stephen Pascoe +44 (0)1235 445980<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Centre of Environmental Data Archival<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>*From:* Pascoe, Stephen (STFC,RAL,RALSP)<o:p></o:p></pre>
<pre>*Sent:* 10 January 2012 14:32<o:p></o:p></pre>
<pre>*To:* <a moz-do-not-send="true" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><o:p></o:p></pre>
<pre>*Subject:* CMIP5 Web interface requirements matrix<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Dear all,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>To help the CMIP5 centres plan our upgrade to the next major release<o:p></o:p></pre>
<pre>of the CMIP5 archive system BADC has been collating a<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>spreadsheet of web interface requirements with input from PCMDI, DKRZ<o:p></o:p></pre>
<pre>and MOHC (see attached). We hope to use this sheet as a tool to plan<o:p></o:p></pre>
<pre>migration of the CMIP5 web interface at the main CMIP5 centres: PCMDI,<o:p></o:p></pre>
<pre>BADC and DKRZ.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The sheet is still work in progress and there is lots to discuss and<o:p></o:p></pre>
<pre>clarify. I have begun to suggest scores for the three systems being<o:p></o:p></pre>
<pre>considered, Gateway 1.3.4, Gateway 2.0 and P2P, but these are<o:p></o:p></pre>
<pre>speculative at this stage, particularly for the P2P system with which<o:p></o:p></pre>
<pre>I have the least experience.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>If there is time I'd like to briefly introduce the sheet at the<o:p></o:p></pre>
<pre>GO-ESSP telco today and schedule a time for a more thorough discussion.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Cheers,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Stephen.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>---<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Stephen Pascoe +44 (0)1235 445980<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Centre of Environmental Data Archival<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Scanned by iCritical.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>------------------------------------------------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
</blockquote>
<pre><CMIP5_GUI_Requirements_v20120110_ejn.xlsx>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
</blockquote>
<pre>--<o:p></o:p></pre>
<pre>Scanned by iCritical.<o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>******************************************<o:p></o:p></pre>
<pre>Sylvia Murphy<o:p></o:p></pre>
<pre>NESII/CIRES/NOAA Earth System Research Laboratory<o:p></o:p></pre>
<pre>325 Broadway, Boulder CO 80305<o:p></o:p></pre>
<pre>Time Zone: U.S. Mountain<o:p></o:p></pre>
<pre>Web: <a moz-do-not-send="true" href="http://www.esrl.noaa.gov/nesii/">http://www.esrl.noaa.gov/nesii/</a><o:p></o:p></pre>
<pre>Email: <a moz-do-not-send="true" href="mailto:sylvia.murphy@noaa.gov">sylvia.murphy@noaa.gov</a><o:p></o:p></pre>
<pre>Phone: 303-497-7753<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
</blockquote>
<pre>Gary Strand<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:strandwg@ucar.edu">strandwg@ucar.edu</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
</blockquote>
</blockquote>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>GO-ESSP-TECH mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a><o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Gavin M. Bell<o:p></o:p></pre>
<pre>--<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre> "Never mistake a clear view for a short distance."<o:p></o:p></pre>
<pre> -Paul Saffo<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</div>
<br>
<p>-- <br>
Scanned by iCritical.
</p>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gavin M. Bell
--
"Never mistake a clear view for a short distance."
-Paul Saffo
</pre>
</body>
</html>