[
https://issues.apache.org/jira/browse/SINGA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760142#comment-15760142
]
ASF subversion and git services commented on SINGA-261:
-------------------------------------------------------
Commit 4dfee520809e467c7794c20e29b6d90d771c1653 in incubator-singa's branch
refs/heads/master from wangwei
[ https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git;h=4dfee52 ]
SINGA-261 Add version ID into the checkpoint files
replace CUDNN_MAJOR_VERSION with CUDNN_MAJOR (from cudnn.h) in singa cpp code.
add cudnn version test for pysinga
add cuda test for pysinga (device and layer)
> Add version ID into the checkpoint files
> ----------------------------------------
>
> Key: SINGA-261
> URL: https://issues.apache.org/jira/browse/SINGA-261
> Project: Singa
> Issue Type: Improvement
> Reporter: wangwei
>
> During the development progress, we may change the checkpoint file structure.
> To be compatible with previous version, we need to add the version ID
> (MAJOR_VERSION, MINOR_VERSION, PATCHLEVEL) into the checkpoint file and
> convert the checkpoint file content automatically when we load it.
> The version ID would be written into the .desc file. The load() function
> would read the .desc file firstly and then choose the correponding method to
> read the parse the .model file.
> The the weight matrix of the dense layer as an example. Some systems (e.g.
> Caffe) set the shape as (num_output, num_input), whereas SINGA uses
> (num_input, num_output). If we change it to (num_output, num_input) in a new
> patch/version, we need to associate the checkpoint file with the SINGA
> version and SINGA would then know how to load the checkpoint file correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
