<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Luca,</div><div><br></div><div>I was experimenting with setting up a publishing script for the ARM cmbe observational data following the proposal below. I see few issues:</div><div>I understand (I am cc-ing Bob Drach to check on that) the publisher needs at least those 3 fields for the "CMIP5' project:</div><div>project (which is 'CMIP5'), experiment (that could be specified as 'none' in command options, but maybe should be 'observations' ?), and model </div><div>A 'model' is an important field and I was trying to set it up so as 'cmbe' would be my 'model', which seems to be equivalent to 'airs' for NASA AIRS data</div><div><br></div><div>The other problem is that we need a specific table (CMOR table) to establish the controlled variable list and data frequency that is obs specific.</div><div>We (with ORNL team) are trying to create an obsCfSites table, that would be mostly a copy of cfSites table with obs specific time definition (for cmbe it's 1 hour average, for CDIAC data - 30 min average, and for 3D data with vertical axis - we would like to specify that any pressure level could be reported). I think it would be good if we could encompass all the observational data needs in one observational table. </div><div> </div><div>I did not try to test publish the data yet, I am working on rewriting the data with the appropriate metadata first, so I am not sure what other problems may pop up.</div><div><br></div><div>Greetings,</div><div>Renata</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><div>------------------------------------------------------------<br>Renata B. McCoy, Ph.D<br>Program for Climate Model Diagnosis and Intercomparison(L-103)<br>Lawrence Livermore National Laboratory<br>P.O. Box 808<br>Livermore, CA 94551<br><br>(925) 424-5237 (voice)<br>(925) 422-7675 (fax)<br><a href="mailto:mccoy20@llnl.gov">mccoy20@llnl.gov</a><br>------------------------------------------------------------<br></div><div><font class="Apple-style-span" face="Arial"><font class="Apple-style-span" face="Helvetica"><br></font></font></div></div></div></div></div></span></div></span></div></span></div></span></span>
</div>
<br><div><div>On Jan 26, 2011, at 2:50 PM, Cinquini, Luca (3880) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi all,<div><span class="Apple-tab-span" style="white-space:pre"> </span>apologies for cross-posting...</div><div><br>I'd like to start a discussion on how the DRS specification for CMIP5 model output (<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>)<br>can be applied to observational datasets that will be made part of the same archive. A proposal based on recent workshops with PCMDI is detailed on this wiki page:<br><br><font class="Apple-style-span" color="#144FAE"><u><a href="http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets">http://oodt.jpl.nasa.gov/wiki/display/CLIMATE/Data+and+Metadata+Requirements+for+CMIP5+Observational+Datasets</a></u></font></div><div><font class="Apple-style-span" color="#144FAE"><u><br></u></font>As an example, the directory structure for the NASA AIRS dataset would look like this:<br><br><root directory>/cmip5/observations/nasa/aqua/airs/mon/atmos/ta/l3/vYYYYMMDD/<files><br><br>where:<br><br>"observations"=<product>, same as DRS "output1" or "output2"<br>"nasa"=<agency>, same as DRS "institute"<br>"aqua"=<mission>, replaces DRS "model"<br>"airs"=<instrument>, replaces DRS "experiment"<br>"l3"=<processing level>, replaces DRS "ensemble member"<br>vYYYYMMDD=the dated version, same as specified by the DRS<br><br>The values for the various fields <agency>, <mission>, <instrument> and <processing level> would need to be selected from a controlled vocabulary similar to the one established for models.<br><br>Any comment or insight on the matter is appreciated.... The idea is to try to finalize the specification relatively quickly, let's say a couple of weeks, so that we can start preparing<br>and publishing these observations into the CMIP5 archive.<br><br>thanks in advance,<br><br>Luca<br><div><br></div></div></div></blockquote></div><br></body></html>