You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@climate.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/04/05 02:39:14 UTC
[jira] [Commented] (CLIMATE-391) Date ranges for UI evaluation are
not normalized
[ https://issues.apache.org/jira/browse/CLIMATE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960858#comment-13960858 ]
ASF GitHub Bot commented on CLIMATE-391:
----------------------------------------
GitHub user MJJoyce opened a pull request:
https://github.com/apache/climate/pull/8
CLIMATE-391 - Normalize evaluation time values in OCW UI
- Date values that are passed for an evaluation are now normalized so
all the day values are 1 unless the evaluation is handling daily data.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MJJoyce/climate CLIMATE-391
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/8.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 #8
----
commit ee7bc13defcb4ce14f3760d7ce11065f2513f7ca
Author: Michael Joyce <jo...@apache.org>
Date: 2014-04-05T00:00:15Z
CLIMATE-391 - Normalize evaluation time values in OCW UI
- Date values that are passed for an evaluation are now normalized so
all the day values are 1 unless the evaluation is handling daily data.
----
> Date ranges for UI evaluation are not normalized
> ------------------------------------------------
>
> Key: CLIMATE-391
> URL: https://issues.apache.org/jira/browse/CLIMATE-391
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Components: webapp
> Affects Versions: 0.3-incubating
> Reporter: Michael Joyce
> Assignee: Michael Joyce
> Fix For: 0.4
>
>
> The date ranges that the evaluation UI passes to the backend are not normalized before attempting to subset datasets. This can result in an issue where a dataset's time values have been shifted to the start of the month (in the non-daily data case) while the subset's time values still point to a different day later in the month. This results in the subset being "out of bounds" even though it should be valid.
--
This message was sent by Atlassian JIRA
(v6.2#6252)