<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Times New Roman">Bryan & Balaji,<br>
<br>
I'm all for what's straightforward. I'm also for putting
together a summary of this information sooner, rather than later.
I think the IPCC authors already put together a table for the
normal "historical" runs. Couldn't we just download one file from
each of the historicalMisc runs, and write a script to read what's
in the global "forcing" attribute? We'd create a 3-column table
with model name, p-value, and the list of forcings. This would
take someone a few hours, of course, and would assume folks had
correctly recorded the forcings in the attribute, but we could do
this now, and not wait for everyone to complete the metafor
questionnaire. <br>
<br>
On the other hand, perhaps the documentation will become available
soon enough not to warrant the extra work. what do you think?<br>
<br>
thanks,<br>
Karl<br>
</font><br>
On 2/17/12 8:21 AM, V Balaji wrote:
<blockquote
cite="mid:CAL3m8D8OWkoZ7mQOBhoM6VdP+++FXb5+dKJ=g8KRJ74b8XcFkw@mail.gmail.com"
type="cite">
<pre wrap="">Agreed!
I think the effort Karl is proposing to undertake (to tabulate the
forcings associated with each p-value for each model) is a monumental
one without CIM metadata, and reasonably straightforward using the
CIM.
On Fri, Feb 17, 2012 at 3:32 AM, Bryan Lawrence
<a class="moz-txt-link-rfc2396E" href="mailto:bryan.lawrence@ncas.ac.uk"><bryan.lawrence@ncas.ac.uk></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Gary
This is precisely what the metadata side of things is supposed to pick up. Future versions of the user interface will have links between data and metadata, so you can click through to the distinguishing factors, which hopefully will have been entered in the simulation descriptions.
Cheers
Bryan
</pre>
<blockquote type="cite">
<pre wrap="">Hi Gary,
To be sure, the experiment_id for the CCCMA dataset shown below was (if
correct) "historicalMisc". When they published it, they chose to name
the experiment "volcanic aerosol". This is informational but is not
used by the ESG search engines or in any other automatic processing that
I know of. (I thought whoever was publishing would just put in
experiment="historicalMisc", so it would be consistent with the
experiment_id global attribute.)
I don't think we've provided much guidance about this (outside the DRS
document), but for each different combination of forcings in the
historicalMisc runs, you should assign a different "physics_version"
number (i.e., the "p" in the ensemble identifier, which in the example
below is "p3"). You should also record in the global "forcing"
attribute in the netCDF file each of the forcings included in each of
your historical(Misc) runs. If you do an ensemble of runs with the same
forcing, they should all have the same "p" value and be distinguished by
the "r" values. The standard abbreviations for each forcing are
provided in the last appendix of the DRS document and also can be found
at
<a class="moz-txt-link-freetext" href="http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_Appendix1-2.pdf">http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_Appendix1-2.pdf</a>
[Note that the output_requirements, available at
<a class="moz-txt-link-freetext" href="http://cmip-pcmdi.llnl.gov/cmip5/docs/CMIP5_output_metadata_requirements.pdf">http://cmip-pcmdi.llnl.gov/cmip5/docs/CMIP5_output_metadata_requirements.pdf</a>
, describes the "forcing" attribute.]
I would like to put together a table that provides a key showing which
forcings are included for each model and for each value of "p"; I just
haven't gotten to this yet.
Please let me know if you can think of any way to make this clearer to
everyone.
Best regards,
Karl
On 2/16/12 7:31 AM, Gary Strand wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
At what point (publishing?) does one of an "historicalMisc" experiment
(as defined and required by the CMIP5 tables) get displayed as:
I would like our (NCAR) "historicalMisc" datasets have a bit more
information available than just the standard (as described in the DRS
document) "historical simulation but with other individual forcing
agents or combinations of forcings."
We have a whole slew of variations that are not readily
distinguishable (and less likely usable) by the above generic description.
Thanks!
Gary Strand
<a class="moz-txt-link-abbreviated" href="mailto:strandwg@ucar.edu">strandwg@ucar.edu</a>
_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
--
Bryan Lawrence
University of Reading: Professor of Weather and Climate Computing.
National Centre for Atmospheric Science: Director of Models and Data.
STFC: Director of the Centre for Environmental Data Archival.
Ph: +44 118 3786507 or 1235 445012; Web:home.badc.rl.ac.uk/lawrence
_______________________________________________
GO-ESSP-TECH mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp-tech">http://mailman.ucar.edu/mailman/listinfo/go-essp-tech</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</body>
</html>