You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@climate.apache.org by "Michael Joyce (JIRA)" <ji...@apache.org> on 2013/09/10 22:23:54 UTC
[jira] [Resolved] (CLIMATE-284) Create separate Base Classes for
metric.py
[ https://issues.apache.org/jira/browse/CLIMATE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Joyce resolved CLIMATE-284.
-----------------------------------
Resolution: Fixed
Resolved
http://svn.apache.org/r1521554
> Create separate Base Classes for metric.py
> ------------------------------------------
>
> Key: CLIMATE-284
> URL: https://issues.apache.org/jira/browse/CLIMATE-284
> Project: Apache Open Climate Workbench
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 0.2-incubating
> Reporter: Michael Joyce
> Assignee: Michael Joyce
> Fix For: 0.3-incubating
>
>
> We currently have a single base class from which we inherit all metrics. This makes the code a bit ugly when we call a metric's 'run' function because we have to be flexible enough to accept a variable amount of datasets. So a unary metric's run function still takes an array of datasets even though that array will only have a single dataset in it.
--
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