+1. This is only a small limitation in the version 0.1. This exception occurs only when the model/evaluation domain is located across the dateline. This limitation needs to be removed in a future release version (e.g., 0.2) but should not hold the release of v0.1 which is good for most users.
I propose to release 0.1 and specify the limitation in a release note or user manual, e.g., (1) If a user works with a GCM and the GCM domain ranges from 0E to 360E (i.e., the date line in the middle of the GCM domain), re-order the GCM data to be in the -180 to 180 range before feeding the data into RCMES, (2) Avoid using an evaluation domain to cross the dateline. Please note that this limitation will be applied practically to the case in which the domain must includes Alaska, e.g., NARCCAP domain. Even for the NARCCAP domain, only a limited number of RCMs include Alaska in their domain. (3) If a user must set a domain to cross the dateline, they have two options; wait until 0.2is released or introduce their own patch to fix the problem. The latter will be great because it is among the key advantage of open source approach. ----------------------------------------------------------------------------------------------------- Jinwon Kim Dept. Atmospheric and Oceanic Sciences and Joint Institute for Regional Earth System Science and Engineering University of California, Los Angeles Los Angeles, CA 90095-1565 ________________________________________ From: Cameron Goodale (JIRA) [[email protected]] Sent: Monday, July 29, 2013 9:47 AM To: [email protected] Subject: [jira] [Commented] (CLIMATE-221) checkLatLon in files.py doesn't work if lons are in the domain (180, 360) [ https://issues.apache.org/jira/browse/CLIMATE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722615#comment-13722615 ] Cameron Goodale commented on CLIMATE-221: ----------------------------------------- Alex, What was the revision you committed to resolve this issue? At the very least that information should be posted to the JIRA issue before marking it resolved. > checkLatLon in files.py doesn't work if lons are in the domain (180, 360) > ------------------------------------------------------------------------- > > Key: CLIMATE-221 > URL: https://issues.apache.org/jira/browse/CLIMATE-221 > Project: Apache Open Climate Workbench > Issue Type: Bug > Affects Versions: 0.1-incubating > Reporter: Alex Goodman > Assignee: Alex Goodman > Priority: Blocker > Fix For: 0.2-incubating > > > If the latlon grid domain is outside [-180,180) but the starting longitude is > greater than 180, checkLatLon throws an exception. Will need to rewrite the > function so it handles such a case. -- 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
