[
https://issues.apache.org/jira/browse/CLIMATE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704103#comment-13704103
]
Kim, Jinwon commented on CLIMATE-186:
-------------------------------------
Additional point related with 1:
My suggested solution will still have problem is the analysis domain includes
the dateline. In this case, the longitude will change from +180 to -177.5
across one grid interval, for example. Thus, suggested simple re-ordering of
the GCM data does not resolve the problem; instead, either the reference data
(from RCMED) or both the reference and model data must be adjusted in such as
way to vary consistently within the domain (e.g., model from 170 to 220;
re-order the reference data from RCMED accordingly). This is a very special
case unless your domain includes the western tip of Alaska.
> 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
