[ 
https://issues.apache.org/jira/browse/CLIMATE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Joyce updated CLIMATE-501:
----------------------------------

    Description: 
Per the discussion on the mailing list, data_source.local is unable to open a 
RegCM file. It seems at first glance that it is failing to find the user 
supplied variable names even though I'm able to access the requested variable 
through the netCDF4.Dataset object in the REPL.

Loading the attached example file with the following commands results in the 
error:

{code}
>>> local.load_file('/Users/mjjoyce/Downloads/RegCM_4-3_SampleOutput.nc', 
>>> 'prmax')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "ocw/data_source/local.py", line 216, in load_file
    lat_name = _get_netcdf_variable_name(LAT_NAMES, netcdf, variable_name)
  File "ocw/data_source/local.py", line 93, in _get_netcdf_variable_name
    raise ValueError(error)
ValueError: Unable to locate a single matching variable name in NetCDF object. 
{code}

However, manually loading the dataset and attempting to access the same 
variable works file. Note that 'x' here is simply the path to the same file.

{code}
>>> y = netCDF4.Dataset(x)
>>> y.variables['prmax']
<netCDF4.Variable object at 0x104f6c3b0>
{code}

  was:
Per the discussion on the mailing list, data_source.local is unable to open a 
RegCM file. It seems at first glance that it is failing to find the user 
supplied variable names even though I'm able to access the request variable 
through the netCDF4.Dataset object in the REPL.

Loading the attached example file with the following commands results in the 
error:

{code}
>>> local.load_file('/Users/mjjoyce/Downloads/RegCM_4-3_SampleOutput.nc', 
>>> 'prmax')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "ocw/data_source/local.py", line 216, in load_file
    lat_name = _get_netcdf_variable_name(LAT_NAMES, netcdf, variable_name)
  File "ocw/data_source/local.py", line 93, in _get_netcdf_variable_name
    raise ValueError(error)
ValueError: Unable to locate a single matching variable name in NetCDF object. 
{code}

However, manually loading the dataset and attempting to access the same 
variable works file. Note that 'x' here is simply the path to the same file.

{code}
>>> y = netCDF4.Dataset(x)
>>> y.variables['prmax']
<netCDF4.Variable object at 0x104f6c3b0>
{code}


> data_source.local is unable to open RegCM data
> ----------------------------------------------
>
>                 Key: CLIMATE-501
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-501
>             Project: Apache Open Climate Workbench
>          Issue Type: Bug
>          Components: data sources
>    Affects Versions: 0.3-incubating
>            Reporter: Michael Joyce
>             Fix For: 0.5
>
>         Attachments: RegCM_4-3_SampleOutput.nc.zip
>
>
> Per the discussion on the mailing list, data_source.local is unable to open a 
> RegCM file. It seems at first glance that it is failing to find the user 
> supplied variable names even though I'm able to access the requested variable 
> through the netCDF4.Dataset object in the REPL.
> Loading the attached example file with the following commands results in the 
> error:
> {code}
> >>> local.load_file('/Users/mjjoyce/Downloads/RegCM_4-3_SampleOutput.nc', 
> >>> 'prmax')
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "ocw/data_source/local.py", line 216, in load_file
>     lat_name = _get_netcdf_variable_name(LAT_NAMES, netcdf, variable_name)
>   File "ocw/data_source/local.py", line 93, in _get_netcdf_variable_name
>     raise ValueError(error)
> ValueError: Unable to locate a single matching variable name in NetCDF 
> object. 
> {code}
> However, manually loading the dataset and attempting to access the same 
> variable works file. Note that 'x' here is simply the path to the same file.
> {code}
> >>> y = netCDF4.Dataset(x)
> >>> y.variables['prmax']
> <netCDF4.Variable object at 0x104f6c3b0>
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to