[
https://issues.apache.org/jira/browse/CLIMATE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739134#comment-14739134
]
ASF GitHub Bot commented on CLIMATE-669:
----------------------------------------
GitHub user huikyole opened a pull request:
https://github.com/apache/climate/pull/231
CLIMATE-669 - OCW spatial_boundary bug
- min and max functions in ocw.dataset.spatial_boundaries are replaced by
numpy.min and numpy.max
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huikyole/climate CLIMATE-669
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/231.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #231
----
commit 96c7e377dce9c40eca9472e23ccd26fa22c236c3
Author: huikyole <[email protected]>
Date: 2015-09-10T17:03:34Z
CLIMATE-669 - OCW spatial_boundary bug
- min and max functions in ocw.dataset.spatial_boundaries are replaced by
numpy.min and numpy.max
----
> OCW spatial_boundary bug
> ------------------------
>
> Key: CLIMATE-669
> URL: https://issues.apache.org/jira/browse/CLIMATE-669
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Reporter: Huikyo Lee
>
> (I reopen #667 JIRA issue).
> Currently, dataset.spatial_boundaries does not properly find maximum and
> minimum values of self.lats and self.lons if self.lats and self.lons are two
> dimensional. This can be easily solved by using numpy.min and numpy.max
> functions instead of min and max.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
