<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">Hi Mike,<br>
<br>
Do you want us to do something on our end? <br>
<br>
I'm not that familiar with esg.ini. For anyone who publishes an
historicalMisc dataset, will the experiment description that
appears in ESG be "volcanic aerosol"? If so, this is generally
wrong, so what should be done to fix this?<br>
<br>
best regards,<br>
Karl<br>
</font><br>
On 2/17/12 10:54 AM, Mike Berkley wrote:
<blockquote
cite="mid:CACkQwYVxC2j6gSwrWHAJdiEKb7QLC3yW8henQNxCZG1v5sTF5w@mail.gmail.com"
type="cite">
<pre wrap="">The "volcanic aerosol" description was a surprise to CCCma, since it
appeared nowhere in our netCDF files. We finally found "volcanic
aerosol" associated with historicalMisc in the default data node
esg.ini file from PCMDI. We have corrected our copy of esg.ini, but
have so far not found the magic incantation to update the metadata
description. Unpublishing and republishing does not change the
metadata, presumably because the data hasn't actually changed.
On Thu, Feb 16, 2012 at 12:21, Karl Taylor <a class="moz-txt-link-rfc2396E" href="mailto:taylor13@llnl.gov"><taylor13@llnl.gov></a> wrote:
</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-f
reetext" 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:
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>
_______________________________________________
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>
</blockquote>
</body>
</html>