[Go-essp-tech] output1 vs. output2

[Drach, Bob]

I agree – at first glance it looks like a bug. I'll fix this in the next release. --Bob

From: "stephen.pascoe at stfc.ac.uk<mailto:stephen.pascoe at stfc.ac.uk>" <stephen.pascoe at stfc.ac.uk<mailto:stephen.pascoe at stfc.ac.uk>>
Date: Tue, 28 Feb 2012 03:14:21 -0800
To: "Taylor, Karl Taylor" <taylor13 at llnl.gov<mailto:taylor13 at llnl.gov>>, "go-essp-tech at ucar.edu<mailto:go-essp-tech at ucar.edu>" <go-essp-tech at ucar.edu<mailto:go-essp-tech at ucar.edu>>, "Drach, Bob" <drach1 at llnl.gov<mailto:drach1 at llnl.gov>>
Subject: RE: [Go-essp-tech] output1 vs. output2

Karl, Bob,

I think this is a bug in ESG publisher.  I've just taken a look at the code and it converts the variable to lower-case before looking it up in an internal table, however the internal table has "sfcWind" so it never finds the variable.  Other variables that may be affected are tasAdjust, tsAdjust and parasolRefl

### In esgcet.config.cmip5_product
def getProduct(cmor_table, variable, experiment, year1, year2):
    """Get the DRS product value associated with the file.
    Returns
      'output1' for datasets to be replicated,
      'output2' for datasets outside the replicated datasets,
      'output' if the product cannot be determined.
    """
    cmor_table = cmor_table.lower()
    variable = variable.lower()

### In esgcet.config.cmip5_tables
# cmor_variables : cmor_table => { variable => (priority, dimension_names)}
cmor_variables = {   '3hr': {   'clt': (1, ['longitude', 'latitude', 'time']),
    # ...
    'amon': {   'ccb': (1, ['longitude', 'latitude', 'time']),
                # ...
                'sfcWind': (1, ['longitude', 'latitude', 'time', 'height10m']),
                'ta': (1, ['longitude', 'latitude', 'plevs', 'time']),
                'tas': (1, ['longitude', 'latitude', 'time', 'height2m']),
                'tasAdjust': (1, ['longitude', 'latitude', 'time', 'height2m']),


Cheers,
Stephen

---
Stephen Pascoe  +44 (0)1235 445980
Centre of Environmental Data Archival
STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK

From: go-essp-tech-bounces at ucar.edu<mailto:go-essp-tech-bounces at ucar.edu> [mailto:go-essp-tech-bounces at ucar.edu] On Behalf Of Karl Taylor
Sent: 28 February 2012 00:52
To: go-essp-tech at ucar.edu<mailto:go-essp-tech at ucar.edu>
Subject: [Go-essp-tech] output1 vs. output2

Hi all,

I have noticed (using the new p2p search engine, which works much faster, and I'm pretty sure is accurate) that sfcWind_Amon_historical output is designated as "output 1" for some models (from IPSL, MOHC, MPI-M, and NOAA-GFDL), but "output2" for the rest.  I think "output1" is correct.

Can anyone explain why the publisher correctly characterized the output from some groups, but not for the rest?

thanks,
Karl


--
Scanned by iCritical.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/go-essp-tech/attachments/20120228/3be608ab/attachment.html