You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@climate.apache.org by "Alex Goodman (JIRA)" <ji...@apache.org> on 2013/07/10 03:04:46 UTC

[jira] [Comment Edited] (CLIMATE-186) RCMES cannot handle NCEP reanalysis and GCM data

    [ https://issues.apache.org/jira/browse/CLIMATE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704070#comment-13704070 ] 

Alex Goodman edited comment on CLIMATE-186 at 7/10/13 1:03 AM:
---------------------------------------------------------------

(1) and (2) can be fixed rather easily, especially if you use basemap.shiftgrid. I'll go ahead and work on this and post the patch as soon as possible.

My main concern with (3) is that for evaluation purposes all the models may need to be converted to the same calendar for daily data. If this were the case I agree with what Jinwon said along the lines of letting the user pick the calendar type for daily data. As far as adding support for the different calendars themselves in code though, this can also easily be done with netCDF4.num2date (converts times from a list of floats to datetime objects). It has inherent support for CF metadata conventions.


                
      was (Author: agoodman):
    (1) and (2) can be fixed rather easily, especially if you use basemap.shiftgrid. I'll go ahead and work this and post the patch as soon as possible.

My main concern with (3) is that for evaluation purposes all the models may need to be converted to the same calendar for daily data. If this were the case I agree with what Jinwon said along the lines of letting the user pick the calendar type for daily data. As far as adding support for the different calendars themselves in code though, this can also easily be done with netCDF4.num2date (converts times from a list of floats to datetime objects). It has inherent support for CF metadata conventions.


                  
> RCMES cannot handle NCEP reanalysis and GCM data 
> -------------------------------------------------
>
>                 Key: CLIMATE-186
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-186
>             Project: Apache Open Climate Workbench
>          Issue Type: Bug
>          Components: regridding
>    Affects Versions: 0.1-incubating
>            Reporter: Huikyo Lee
>            Assignee: Huikyo Lee
>            Priority: Critical
>             Fix For: 0.1-incubating
>
>
> I found some critical bugs while using Jinwon's version 2.1 with CMIP5 outputs and NCEP DOE reanalysis 2 data.  
> They are common problems of 0.1-incubating (RC4) and Jinwon's 2.1
> Currently RCMES cannot properly handle NCEP/NCAR reanalysis or CMIP5 outputs 
> 1. longitude issue
> When reading longitude from netcdf files, the modules in files.py automatically convert longitudes larger than 180 to negative values. This becomes a problem because in GCMs, the longitude array is not monotonically increasing any more (0, 2.5, ...., 180, -175, -172.5, -170,.......... -2.5) due to the conversion. If we choose North America region, RCMES subsets data over the Tibetan Plateau for regridding.
> 2. latitude issue
> In NCEP/NCAR reanalysis, latitude variable (lat) monotonically decreases from north to south. With the current version, users must re-order data so that latitude values increase monotonically from south to north.  
> 3. leap years
> Some CMIP5 GCMs do not consider leap years at all. Our current time decoding reading modules cannot handle these model outputs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira