[
https://issues.apache.org/jira/browse/CLIMATE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181954#comment-14181954
]
Cameron Goodale commented on CLIMATE-536:
-----------------------------------------
Good point Mike. I thought we had code to write out NetCDF files, but I didn't
dig into where it was located.
I still struggle a bit with data_source writing data, it just isn't intuitive.
Another option is to create a data_writer sub-package with it's own local.py
that would handle writing out different data file formats. That make sense to
me, but could be confusing and mixed with the data_source.local.
So many holes in my plan, but I am glad we are working through them.
> Update mccsearch files.py to use current replacement of utils.fortran function
> ------------------------------------------------------------------------------
>
> Key: CLIMATE-536
> URL: https://issues.apache.org/jira/browse/CLIMATE-536
> Project: Apache Open Climate Workbench
> Issue Type: Task
> Components: mcc search
> Affects Versions: 0.5
> Reporter: Lewis John McGibbney
> Assignee: Kim Whitehall
> Priority: Critical
> Fix For: 0.5
>
>
> Currently files.py within the mccsearch module uses a legacy (incorrect)
> fortranfile.py (0)... which hails from the now deprecated rcmet
> fortranfile.py (1)
> We need to make a determination as to how this should be upgraded.
> In particular, we use the following functions
> * [fortranfile.FortranFile(fileName,
> mode='w')|https://github.com/apache/climate/blob/master/mccsearch/code/files.py#L529]
> (0) https://github.com/apache/climate/blob/master/mccsearch/code/files.py#L32
> (1)
> https://github.com/apache/climate/blob/master/rcmet/src/main/python/rcmes/utils/fortranfile.py
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
