<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
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.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle23
{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;}
/* List Definitions */
@list l0
{mso-list-id:480655165;
mso-list-template-ids:-724901106;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:541940242;
mso-list-template-ids:1493226088;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:740638135;
mso-list-template-ids:-1633231482;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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]-->
</head>
<body bgcolor="white" lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello Karl,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for clear response – I probably should have been able to work that out if I had followed the email thread carefully.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">There is a separate document for CORDEX which describes the intended mapping of attributes onto facets in the ESGF User Interface – I’ll try to send that to
you later.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I understand your reservations about some aspects of the CORDEX data requirements, but the aim was to use terms which are in usage in the community (particularly
for the “region” attribute which actually combines region and resolution) and thus, hopefully, improve compliance and acceptance of the standard. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">There is an aspiration to include statistically downscaled data in the CORDEX archive (and it is another shortcoming of the CORDEX document you refer to, I
think, that it only deals with dynamically downscaled data and does not leave a hook to allow extension to statistically downscaled). The system you’ve described could presumably be used for statistically downscaled data in CORDEX. We have a new European Union
project starting next week which funds Bruce Hewitson’s group in Cape Town to do some coordination and networking on data standards for CORDEX downscaling, so I’ve copied in Chris Jack who is, I think, leading their effort.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Martin<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Karl Taylor [mailto:taylor13@llnl.gov] <br>
<b>Sent:</b> 27 March 2013 00:51<br>
<b>To:</b> Juckes, Martin (STFC,RAL,RALSP)<br>
<b>Cc:</b> galina@ucar.edu; obc@dmi.dk; colin.jones@smhi.se; ncpp_core@list.woc.noaa.gov; ncpp_tech@list.woc.noaa.gov; go-essp-tech@ucar.edu; laura.e.carriere@nasa.gov; gerald.potter@nasa.gov; williams13@llnl.gov; denis.nadeau@nasa.gov; Pascoe, Stephen (STFC,RAL,RALSP)<br>
<b>Subject:</b> Re: Global attributes and DRS extensions for downscaled datasets<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
Dear Martin,<br>
<br>
I'm not advocating changing the CORDEX requirements; it's probably much too late for that. There are are limitations to the generality of the CORDEX specifications, which means they might not be applicable to downscaling efforts outside of CORDEX. The document
I prepared was to try to address the more general issue of what descriptors are needed for downscaled datasets.
<br>
<br>
I have proposed that a single additional "descriptor" be added to the already defined components of the DRS:<br>
<br>
Source of predictor data <span style="font-family:"Cambria Math","serif"">⇒</span> driving_model_id - driving_model_rip (e.g. “GFDL-CM3-r1i1p1”) In some cases the driving_model_rip might be omitted (e.g., when using reanalysis output to drive the downscaling).
<br>
<br>
In CORDEX this descriptor could be formed by joining with a hyphen your GCMModelName and CMIP5EnsembleMember.<br>
<br>
I have also proposed expanding the "ensemble member" descriptor to include an indication of the "nominal resolution". The idea here is that output might need to be regridded or be made available at various resolutions, so we would like to be able to distinguish
among these closely related datasets. Here is the description of the 'riph' designator:<br>
<br>
Ensemble member<span style="font-family:"Cambria Math","serif"">⇒</span> ‘riph’ designator, where the “rip” form is defined as in CMIP5 (which for downscaled data would usually be “r1i1p1”), and the “h” is followed by nominal resolution expressed in kilometers.
(For backward compatibility the DRS would consider the “h” segment as optional, but it is required for downscaled datasets.) The last part of the 'riph' designator is of the form “hnXXXX” or “hiXXXX” where XXXX is the nominal horizontal resolution of the
downscaled data, expressed in kilometers (rounded to the nearest km with leading zeros dropped). “hn” indicates that the data is stored on the model’s “native” grid, while “hi” indicates that the data has been interpolated from a model’s native grid to a
different grid. (Statistically downscaled data would normally be recorded on a so-called “native” grid.) Data on a native grid at a nominal resolution of 5 km, for example, would be identified as “hn5”, while regridded data at 11 km resolution would be identified
as “hi11”. The XXXX should be calculated as follows: XXXX = sqrt(domain area / (number of grid cells)), expressed in km/grid cell and rounded off to the nearest km.
<br>
<br>
CORDEX has chosen to include resolution information as part of a domain name (e.g., CAM-44 or SAM-44i), but the resolution doesn't seem to me to belong as part of the region identification.<br>
<br>
I should note also that CORDEX specifies a directory structure and/or filenames where in the CORDEX document some of the DRS categories are renamed. I've attached a table that shows the DRS elements and corresponding CORDEX identifiers, along with global attributes.
(I'm going to try to get NASA / NOAA to be consistent with the DRS.) I also provide a table of additional global attributes. CORDEX is mostly consistent with this table, except for using "CORDEX_domain and omitting driving_model_tracking_ids.
<br>
<br>
Finally, I note that in the example found in the CORDEX document for global attributes:<br>
<br>
1) experiment_id = "evaluation", but in the directory structure and filename templates, this is presumably used as "CMIP5ExperimentName", but of course "evaluation" is not a CMIP5 experiment. I think a better term for "CMIP5ExperimentName" is simply "experiment",
which in the case of CORDEX is usually the same as the CMIP5 experiment_id.<br>
<br>
2) CORDEX requires "contact", but this was left out of the example.<br>
<br>
Please let me know what you think.<br>
<br>
Best regards,<br>
Karl<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On 3/26/13 4:58 AM, <a href="mailto:martin.juckes@stfc.ac.uk">
martin.juckes@stfc.ac.uk</a> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello Karl,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m puzzled about how this fits in with CORDEX. We went through this discussion some time ago, and agreed on some data requirements
in the document you cite below which we believed to be appropriately consistent with the CMIP5 requirements. This document was then discussed at a WCRP meeting and has been circulated as the requirements for groups submitting CORDEX data to ESGF. Since then,
modelling groups have been preparing data and we are expecting to start publication soon. Do you think there are problems with uniformity in the way the CORDEX requirements are specified?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Martin </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:72.0pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Karl Taylor [<a href="mailto:taylor13@llnl.gov">mailto:taylor13@llnl.gov</a>] <br>
<b>Sent:</b> 25 March 2013 21:50<br>
<b>To:</b> Galia Guentchev<br>
<b>Cc:</b> <a href="mailto:ncpp_core@list.woc.noaa.gov">ncpp_core@list.woc.noaa.gov</a>; NCPP TECHNICAL TEAM;
<a href="mailto:go-essp-tech@ucar.edu">go-essp-tech@ucar.edu</a>; <a href="mailto:laura.e.carriere@nasa.gov">
laura.e.carriere@nasa.gov</a>; Potter, Gerald Lee. (GSFC-606.2)[UNIVERSITY OF MARYLAND]; Dean Williams; Nadeau, Denis (GSFC-610.1)[R S INFORMATION SYSTEMS, ]; Juckes, Martin (STFC,RAL,RALSP); Pascoe, Stephen (STFC,RAL,RALSP)<br>
<b>Subject:</b> Global attributes and DRS extensions for downscaled datasets</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:72.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
Dear all,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
I have spent considerable time reviewing the following four documents:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
A. The email (copied below) sent by Galia and Aparna, which proposed attributes, filenames, and directory structures for downscaled data.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
B. <a href="http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_syntax.pdf">
http://cmip-pcmdi.llnl.gov/cmip5/docs/cmip5_data_reference_syntax.pdf</a> which describes the corresponding CMIP5 metadata.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
C. <a href="http://cordex.dmi.dk/joomla/images/CORDEX/cordex_archive_specifications_121022.pdf">
<span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#1155CC">http://cordex.dmi.dk/joomla/images/CORDEX/cordex_archive_specifications.pdf</span></a> which describes the corresponding CORDEX metadata.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
D. <a 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> which specifies all the CMIP5 metadata requirements.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
I hope that document A above could be made compatible with the others and in general could provide a sound basis for establishing more uniformity moving forward. Toward that end, I have prepared the attached document describing for downscaled data a minimal
set of global attributes needed to augment those used in CMIP5 and also the extensions needed to the DRS document to accommodate downscaled data.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
I hope at least a few of you will take the time to study this document and provide feedback.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
Best regards,<br>
Karl<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:72.0pt">
<br>
Mail sent by Galia Guentchev 3/12/13<br>
<br>
**********************************************************************<br>
Details of each element of the proposed directory structure:<br>
<br>
Proposed elements -<br>
/projectID/<span style="color:#3333FF">sub-project</span>/product/institution/<b>predictorModel/experimentID/frequency/realm/MIPtable/Pred<br>
ictor_experiment_rip/predictorversion</b>/<i>downscalingMethod/predictand (variableName)/region</i>/<i>DownscaledDataversion</i>/file_name.nc<br>
<br>
Example:<br>
<br>
/ncpp2013/<span style="color:#3333FF">perfectModel</span>/downscaled/NOAA-GFDL/<b>GFDL-HIRAM-C360-coarsened/amip/day/atmos/day/r1i1p1/v20121024</b>/<i>GFDL-ARRMv1/tasmax/US48/v20120227</i>/tasmax_day_amip_r1i1p1_downscaled_US48_GFDLARRMv1_19790101-19831231.nc<br>
<br>
The new element <span style="color:#3333FF">sub-project </span>(in blue above) gives the opportunity to indicate to users that in the one case the method was trained on observations (standard setting), and in the other on model that was considered to be the
truth (perfect model setting);<br>
The options there could be: PerfectModel or Standard - where possibly there could be a different name instead of 'standard' for the standard downscaling setting.<o:p></o:p></p>
<p style="margin-left:72.0pt">For NASA datasets some of the directories could be:
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt">project = NEX<br>
product = downscaled<br>
institution = NASA-Ames<br>
predictorModel - original model value<br>
experimentID = historical<br>
frequency = mon<br>
realm = atmos<br>
Predictor_experiment_rip - original model value<br>
variable = precipitation or temperature<br>
region = CONUS<br>
<br>
DownscalingMethod will also be included as a directory to allow for search on method.<br>
<br>
**********************<br>
There are a set of sub-directories that refer to the <u>PredictorModel</u> - presented in bold -
<b>/predictorModel/experimentID/frequency/realm/MIPtable/Pred<br>
ictor_experiment_rip/predictorversion</b><br>
<br>
Where: <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>predictor model - is the specific GCM which is the source of the predictor data set - GFDL-HIRAM-C360-coarsened - in the above example<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>experimentID - the specific experiment - amip in this case<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>frequency - refers to the temporal scale of the predictor fields - daily<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>realm - the realm of the predictors - in this case atmos(phere)<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>MIPtable - name of the model intercomparison table - daily in this example, could be amon - for atm monthly data;<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Predictor-Experiment-rip - follows the standard notation from CMIP5<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>version - the version date of the global model that provided the predictor dataset<o:p></o:p></p>
<p style="margin-left:72.0pt">The elements above follow quite closely the structure for CMIP5 model output directory elements.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt">There is a set of sub-directories that refer to the Downscaling method - presented in italics -
<br>
<i>downscalingMethod/predictand (variableName)/region/DownscaledDataversion<br>
<br>
</i>Where:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo4">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>downscalingMethod - is the downscaling method abbreviation - in this case GFDL-ARRMv1 - the GFDL in the name indicates that this is a setting applied by GFDL where there were two sets of predictors, based on the ARRM method of
K.Hayhoe; also v.1 indicates which version of the ARRM method was used (the original version) - more details about the method are given in the global attributes of the file;<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo4">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Predictand (variableName) - the specific predictand variable that was downscaled; tasmax in this case;<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo4">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>region - indicates that the method was applied to the US48<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo4">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>DownscaledDataversion - the version of the downscaled dataset<o:p></o:p></p>
<p style="margin-left:72.0pt"><b>For the purposes of standardization there are two directions to consider:</b>
<o:p></o:p></p>
<p style="margin-left:72.0pt">1) One is to have<b> one standard directory</b> structure that will be used by all - for example, following the example of GFDL to have the details of the predictor model first and then the downscaling method details:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:108.0pt;text-indent:-18.0pt;mso-list:l2 level1 lfo6">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>ProjectID - sub-project - product - Institution - Predictor dataset details - Downscaling method details - Filename<o:p></o:p></p>
<p style="margin-left:72.0pt">Having a standardized approach would help any automated service/web service to detect the directory path for a particular dataset.
<o:p></o:p></p>
<p style="margin-left:72.0pt">2) During our last teleconference there was a proposal to follow the downscaling practice and describe the downscaling method first and then the predictor model. This leads to
<b>two paths</b>:<o:p></o:p></p>
<p style="margin-left:72.0pt"> • ProjectID - <u><span style="color:#3333FF">Standard or Perfect Model sub-project facet</span></u><span style="color:#3333FF">
</span>- product - Institution - then see below:<br>
- (if Perfect model setting) Predictor dataset details - Downscaling method details,
<br>
- (if Standard setting) - Downscaling method details - Predictor dataset details<o:p></o:p></p>
<p style="margin-left:72.0pt"><br>
The NCPP Core team accepts that it may be reasonable to have a directory structure - where the method description is first; and another directory structure - where the predictor description is first and then the methods that are applied are described;
<b>NCPP will support either approach</b> (one overall directory structure, or two separate pathways) and if the second approach is chosen (with two different sub-directory sequences) - we would like to promote and to support the standardization of these different
directory pathways - meaning - we will support two standardized directory structures to accommodate two common practices.<o:p></o:p></p>
<p style="margin-left:72.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt">******************<br>
<span style="color:#009900">Additional details</span>: <br>
<br>
<b>Variable level attributes-</b><br>
The published dataset should also conform to CF-standards. <br>
eg-<br>
<br>
tasmax:long_name = "Downscaled Daily Maximum Near-Surface Air Temperature" ; <br>
tasmax:units = "K" ; <br>
tasmax:missing_value = 1.e+20f ; <br>
tasmax:_FillValue = 1.e+20f ; <br>
tasmax:standard_name = "air_temperature" ; <br>
tasmax:original_units = "K" ; <br>
<b> tasmax:downscaling_method: GFDL-ARRMv1</b><br>
<br>
<b>Global attributes- </b>listing a few here, several CMIP-style attributes will be inherited.
<br>
<br>
"predictorModel" will replace "model_id"<br>
For the 'downscaling model', as agreed with Luca on the call it would be 'downscalingMethod'
<br>
<br>
:Conventions = "CF-1.4" ;<br>
:references = "info about model, training datasets etc will be provided here"<br>
:info = "additional info about the downscaling method" <br>
:creation_date = "2011-08-19T21:57:06Z" ;<br>
:institution = "NOAA GFDL(201 Forrestal Rd, Princeton, NJ, 08540)" ;<br>
:history = "info on file processing. Eg" processed by toolX." ;<br>
:projectID = ncpp2013<br>
:subprojectID = perfectModel<br>
:product = downscaled<br>
:institution = NOAA-GFDL<br>
:predictorModel = GFDL-HIRAM-C360-coarsened<br>
:experimentID = amip<br>
:frequency = day<br>
:modeling_realm = atmos<br>
:Predictor_experiment_rip = r1i1p1<br>
:region = US48<br>
:table_id = day<br>
:version = v20120227<br>
:downscalingMethod = GFDL-ARRMv1<br>
**************************************************<br>
<br>
Best regards,<br>
Galia and Aparna<br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre style="margin-left:72.0pt">-- <o:p></o:p></pre>
<pre style="margin-left:72.0pt">Galia Guentchev, PhD<o:p></o:p></pre>
<pre style="margin-left:72.0pt">Project Scientist<o:p></o:p></pre>
<pre style="margin-left:72.0pt">National CLimate<o:p></o:p></pre>
<pre style="margin-left:72.0pt">Predictions and <o:p></o:p></pre>
<pre style="margin-left:72.0pt">Projections <o:p></o:p></pre>
<pre style="margin-left:72.0pt">Platform (NCPP)<o:p></o:p></pre>
<pre style="margin-left:72.0pt">NCAR RAL CSAP<o:p></o:p></pre>
<pre style="margin-left:72.0pt">FL2 3103<o:p></o:p></pre>
<pre style="margin-left:72.0pt">3450 Mitchell Lane<o:p></o:p></pre>
<pre style="margin-left:72.0pt">Boulder, CO, 80301<o:p></o:p></pre>
<pre style="margin-left:72.0pt">phone: 303 497 2743 <o:p></o:p></pre>
<p class="MsoNormal" style="margin-left:72.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p style="margin-left:36.0pt">-- <br>
Scanned by iCritical. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
</body>
</html>