[
https://issues.apache.org/jira/browse/CLIMATE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744560#comment-13744560
]
Cameron Goodale commented on CLIMATE-260:
-----------------------------------------
Andrew,
I know this issue was resolved by Kim Whitehall this summer because she was
working with a dataset with a similar issue. Turns out we have duplicate
functionality, i mean the functions are named the exact same name, even the
docstrings match up.
Check out:
rcmes.toolkit.process.decodeTimeFromString(time_string)
vs.
rcmes.services.decode_model_times.decodeTimeFromString(time_string)
I will open a new JIRA issue to resolve this duplication problem.
> decode_model_times chokes if time representation contains .0 after seconds
> --------------------------------------------------------------------------
>
> Key: CLIMATE-260
> URL: https://issues.apache.org/jira/browse/CLIMATE-260
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Components: rcmet
> Affects Versions: 0.2-incubating
> Reporter: Andrew Hart
> Assignee: Andrew Hart
> Labels: time
> Fix For: 0.3-incubating
>
>
> decoding of the time variable in model files currently chokes if time is
> specified in the model file with an extra ".0" in the seconds position. This
> currently causes a parse error in trying to decode the variables in the model
> file even though this is a valid way to represent time.
--
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
