<!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 bgcolor="#ffffff" text="#000000">
Hi Stephen,<br>
<br>
Thanks for getting back on this. Note I said "The "Data Reference
Syntax"
document and the CMOR tables will be revised shortly to include
these
"new" experiments." .... clearly, "shortly" has not yet arrived.<br>
<br>
cheers,<br>
Karl<br>
<br>
On 11/15/10 2:07 AM, <a class="moz-txt-link-abbreviated" href="mailto:stephen.pascoe@stfc.ac.uk">stephen.pascoe@stfc.ac.uk</a> wrote:
<blockquote
cite="mid:EB1E7CB92F5B35459E0B926D2A614DB60D5ECBEE@EXCHANGE19.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;}
@font-face
{font-family:"Times\000D\000A New Roman";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Times New Roman \; color\: black\;";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Times New\000D\000A Roman";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:6.0pt;
margin-right:0cm;
margin-bottom:6.0pt;
margin-left:0cm;
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;}
span.download
{mso-style-name:download;}
span.moz-txt-citetags
{mso-style-name:moz-txt-citetags;}
span.moz-txt-tag
{mso-style-name:moz-txt-tag;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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="Section1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Hi Karl,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">drslib reads the CMOR MIP tables to find the
experiment
vocabulary so there will be no need to change the code to
accommodate a historicalExt
experiment provided it is defined in the tables. However, I
notice the
latest tables do not include this (downloaded today).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Cheers,<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>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span
style="font-size: 10.5pt; font-family: Consolas; color:
rgb(31, 73, 125);">---<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><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" style="margin: 0cm 0cm 0.0001pt;"><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" style="margin: 0cm 0cm 0.0001pt;"><span
style="font-size: 10.5pt; font-family: Consolas; color:
rgb(31, 73, 125);">Rutherford Appleton
Laboratory, Chilton, Didcot OX11 0QX, UK<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);"><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>
<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" style="margin: 0cm 0cm 0.0001pt;"><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>Karl Taylor<br>
<b>Sent:</b> 13 November 2010 19:33<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a><br>
<b>Cc:</b> Charles Doutriaux<br>
<b>Subject:</b> [Go-essp-tech] new expt. to add to CMIP5
and the DRS document<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;">*** nb.
Those
of you developing software in support of CMIP5 may need to
modify things to
include one more CMIP5 experiment. See below:<br>
<br>
Dear all,<br>
<br>
At the WGCM meeting in Exeter there was agreement that the
"historical" runs should be extended from their official
ending date
at the end of 2006 to about year 2012. The concentrations and
land-use
changes specified in these runs will not be the same for all
groups and may not
even be based on true observations (but instead be estimated
in various ways).
Since these runs should not be confused with the "historical"
runs
where everyone uses the same forcing (based on observations),
the feeling is
these short runs (2006-2012) should be labeled as a new
experiment. I've
sent a message to the modeling groups describing what they
should do. You
might want to read items 6e and 6f in that message (copied
below). <span style="">To accommodate
these new runs, we need to add a line to the second table of
Appendix 1.1 of
the DRS document with the following entries:<br>
<br>
7.4 historicalExt
historical extension</span> e<span style="font-size:
10pt; font-family: "Times New Roman ; color:
black;","serif";">xtension
of the historical simulation (experiment 3.2) through year
2012.</span> <br>
<br>
I understand this will require additions to much of the
software, possibly
including CMOR2 tables, ESG publisher?, ESG node software?,
METAFOR
questionnaire, ESG search?, etc.<br>
<br>
I apologize for these late changes, but the WGCM thought it
important to
include these extensions of the historical runs so that
detection attribution
studies could be done.<br>
<br>
Please pass on this message to anyone who might need to know
this (beyond those
already on the GO-ESSP-tech mail list).<br>
<br>
Best regards,<br>
Karl<br>
<br>
---------------------------<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><span
style="">Dear all,<br>
<br>
Here are some items that should be of interest to those of
you participating in
CMIP5. Please pass on this information, especially to
those who are
responsible for preparing the model output for the CMIP5
archive.<br>
</span><br>
1. For those of you doing the emissions-driven
simulations: Unless
it's too late, it is recommended that the recently produced
gridded fossil fuel
emissions data from Andres (hosted by IPSL) and the the
land use data
from Houghton (hosted at MPI) should be used for the
historical
simulations. More information should appear soon on the
CMIP5
website. <br>
<br>
These fossil fuel emissions data can be retrieved from:<br>
<a moz-do-not-send="true"
href="http://BLOCKED*dods.ipsl.jussieu.fr/cpipsl/ANDRES/">http://BLOCKEDdods.ipsl.jussieu.fr/cpipsl/ANDRES/</a><br>
File name is :
CMIP5_gridcar_CO2_emissions_fossil_fuel_Andres_1751-2007_monthly_SC_mask11.nc<br>
It is a monthly dataset, units are gC/m2/s<br>
Also provided is an ascii file that contains the globally
integrated emissions
for every month.<br>
CMIP5_gridcar_CO2_emissions_fossil_fuel_Andres_1751-2007_monthly_SC_grid1x1.txt
<br>
<br>
The land use file can be found at MPI:<br>
<a moz-do-not-send="true"
href="http://BLOCKED*www.BLOCKED*mpimet.mpg.de/en/wissenschaft/land-im-erdsystem/wechselwirkung-klima-biogeosphaere/landcover-change-emission-data.html">http://BLOCKEDwww.BLOCKEDmpimet.mpg.de/en/wissenschaft/land-im-erdsystem/wechselwirkung-klima-biogeosphaere/landcover-change-emission-data.html</a><br>
File name is:<span class="download">
carbon_emissions_landuse_20person.nc</span>
<br>
It is an annual dataset, units are also gC/m2/s<br>
<br>
2. Again for those of you with coupled carbon climate
models
(ESM's): The CMIP5 expts. 5.4 and 5.5 are designed to
isolate the climate
change effects on carbon uptake from the uptake due to CO2
concentration
increases (in the absence of climate change). Originally
there were two options
proposed for these experiments: analyze 1%/yr CO2 increase
runs or analyze
historical+RCP4.5 runs. At the WGCM meeting last month and
in subsequent discussion,
it was decided that for groups who have not yet performed
these experiments, it
would be better if they would base these runs on the
idealized 1%/yr CO2
increase (rather than the historical+RCP4.5 simulations).
There will, of
course, also be interest in the historical+RCP4.5 runs, so
groups who have
already done these runs, should contribute them to the
archive.<br>
<br>
3. We recently posted a revised document describing the
model output
requirements for CMIP5 (see <a moz-do-not-send="true"
href="http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#metadata">http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#metadata</a>
). (Those of you who have chosen *not* to use CMOR2 to
rewrite your model
output should study this document carefully; those of you
using CMOR may refer
to the CMOR documentation for most of the information you
need to know. The
CMOR documentation has also been recently revised with
expanded descriptions of
what you must supply.) At the beginning of the output
requirements document
there is a link directing the user to the bottom of the
document where a list
of the changes that were made can be found. Nearly all the
changes were
simply to improve clarity. Please note, however, that a new
global
attribute is now required for most simulations
(parent_experiment_rip), which
identifies which ensemble member the child experiments was
spawned from.
This information will be essential for many CMIP5 studies.<span
style=""><br>
<br>
4. The so-called "data reference syntax" document has
also been
revised. Again, many of the changes should simply make it
easier to
understand. Data providers will be especially interested
in the official
"short names" of the CMIP5 experiments, since these names
are used in
constructing filenames. This document can be obtained
through the following
link: <a moz-do-not-send="true"
href="http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#req_format">http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#req_format</a><br>
<br>
5. The latest version of CMOR2 was just released on 12
November
2010. The changes made were summarized on an announcement
made to those
of you on the cmor email list. It also includes the
latest
"requested variables" CMOR tables (also posted at <a
moz-do-not-send="true"
href="http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#req_list">http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/output_req.html?submenuheader=2#req_list</a>
), which includes a number of formerly missing "standard
names", and also some corrections. Please download the
latest version of
CMOR, the CMOR tables and the documentation before
continuing to process your
data.<br>
</span><br>
6. At the WGCM meeting there was agreement that it would be
useful for
model evaluation and detection/attribution studies to extend
the CMIP5
historical runs to near-present (as we have for AMIP),
rather than ending them
in 2005. In fact since the CMIP5 project is ongoing, it
would be useful
to have simulations extended to at least the end of 2012
using some estimate of
recent and future forcing. There is, however, no
community-wide accepted
observationally-based concentration/emissions past 2005.
Groups are
therefore free to use whatever concentrations, solar
forcing, SO2 emissions
etc. they want to use in extending these runs. It is also
o.k. for
detection/attribution studies to simply splice one of the
RCP runs to the end
of the historical simulations. No matter what forcing is
chosen it is
important to consider the following:<br>
<br>
a) The groups should take care that there are no substantial
discontinuities in
the forcing in passing from the "past" to the "future",
defined to be the end of 2005. <br>
<br>
b) It is recommended that if an ensemble of "all-forcings"
historical
simulations have been run, then <span class="moz-txt-tag"><b>*</b></span><b>each<span
class="moz-txt-tag">*</span></b> member of the ensemble
should be carried to the
end of 2012. Thus, a full ensemble of runs (through year
2012)
would be available for analysis.<br>
<br>
c) It is recommended that all historical runs with only a
subset of
forcing (e.g., GHG only, natural forcing only) should also
be extended through
the year 2012.<br>
<br>
d) If one of the RCP forcings is used to extend the
historical run, it may not
matter too much which RCP is chosen, and CMIP5 makes no
strong recommendation.
If a modeling group has no preference, they might choose the
RCP8.5 expt., as
at least one group (the Hadley Centre) has made this choice
already.<br>
<br>
e) For all-forcing (anthro + natural) historical runs, the
extended portions of
these runs should be treated as a new runs spawned from the
parent historical
runs at the end of year 2005. If this run is forced by an
RCP that
extends at least to the end of the 21st century, then
nothing special needs to
be done. If, however, some other forcing is used or if the
run is an RCP
run that is truncated after a few years (say ending in
2012), then the run
should be considered a "historical extension" experiment
with its
output placed in a directory named historicalExt. The
"forcing"
attribute (a netCDF global attribute) should describe what
forcing is used to
extend the run, and this information will also need to be
recorded when
entering information about the run in the METAFOR
questionnaire. Placing
the extended portion of the historical runs in a separate
place will help guard
against users assuming that these runs are necessarily based
on
historically-measured concentrations, land-use changes,
solar forcing,
etc. For these historicalExt experiments, the ensemble
member (designated
by the "rip" value appearing in the filename and recorded as
netCDF
global attributes) will be identical to the historical run
it extends. Also for
the runs, the identifying netCDF global attributes should be
defined as
follows: experiment="historical extension" and
experiment_id="historicalExt". The "Data Reference Syntax"
document and the CMOR tables will be revised shortly to
include these
"new" experiments. <br>
<br>
f) If one chooses to do historical runs with only a subset
of forcing (e.g.,
GHG only, natural forcing only, single-forcing experiments,
etc.), then all the
data for the complete historical period and in the extended
portion (from
2006-2012) would be kept together, no matter what forcing
was used (in the
historicalNat, historicalGHG, or historicalMisc
directories). (In these
clearly "unrealistic" cases, naive users will be less likely
to
access the output and possibly misuse it.) <br>
<br>
7. For your information, We've posted (see <a
moz-do-not-send="true"
href="http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/terms.html?submenuheader=3">http://BLOCKEDcmip-pcmdi.llnl.gov/cmip5/terms.html?submenuheader=3</a>
) the latest (and final) version of the the two different
terms of use
governing the CMIP5 model output. It looks like about half
the groups
plan to release their data for "unrestricted" use and half
for
"non-commercial educational and research purposes" only. <br>
<br>
Carry on!<br>
<br>
Best regards,<br>
your faithful CMIP5 comrades (Karl's lame attempt to try to
develop a little
esprit de corps here),<br>
Karl and Ron <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><o:p> </o:p></p>
</div>
<br>
<p>-- <br>
Scanned by iCritical.
</p>
<br>
</blockquote>
</body>
</html>