singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wangwei (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SINGA-193) Add Python layers
Date Fri, 17 Jun 2016 14:43:05 GMT

     [ https://issues.apache.org/jira/browse/SINGA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

wangwei updated SINGA-193:
--------------------------
    Description: 
This ticket creates the python layers for V1, which differ to the python layers of v0,3 in
terms of the layer construction.
The python layers should provide intuitive APIs for uses to configure the layer. Keras API
would be a reference.
We need to consider the param specs in the layer creation which is missing in Keras APIs.
The python layer would be uniform for cudnn, opencl and cpp. A backend (e.g., 'cudnn', 'cuda')
field would be used to create the C++ layer, e.g., cudnnPooling or openclPooling. 




  was:
This ticket creates the base python layer for V1, which differs to the python layers of v0,3
in terms of the layer construction.
The python layers should provide intuitive APIs for uses to configure the layer. Keras API
would be a reference.
We need to consider the param specs in the layer creation which is missing in Keras APIs.
The python layer would be uniform for cudnn, opencl and cpp. A backend field would be used
to create the C++ layer, e.g., cudnnPooling or openclPooling. 

The python version of dense layer would be provided as an example.



> Add Python layers
> -----------------
>
>                 Key: SINGA-193
>                 URL: https://issues.apache.org/jira/browse/SINGA-193
>             Project: Singa
>          Issue Type: New Feature
>            Reporter: wangwei
>            Assignee: wangwei
>
> This ticket creates the python layers for V1, which differ to the python layers of v0,3
in terms of the layer construction.
> The python layers should provide intuitive APIs for uses to configure the layer. Keras
API would be a reference.
> We need to consider the param specs in the layer creation which is missing in Keras APIs.
> The python layer would be uniform for cudnn, opencl and cpp. A backend (e.g., 'cudnn',
'cuda') field would be used to create the C++ layer, e.g., cudnnPooling or openclPooling.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message