[jira] [Commented] (SINGA-261) Add version ID into the checkpoint files

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SINGA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692455#comment-15692455 ] 

ASF subversion and git services commented on SINGA-261:
-------------------------------------------------------

Commit e43ea694521d64bac276d9e3e634edd5d6a04be9 in incubator-singa's branch refs/heads/master from [~wangwei.cs]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git;h=e43ea69 ]

SINGA-261 Add version ID into the checkpoint files

Add singa version and cudnn version for PySINGA, singa.__version, singa.layer.cudnn_version
Fixed a bug in using PySINGA rnn (caused by swig rename of forward and backward)


> 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)