Mailing-List: contact dev-help@singa.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@singa.incubator.apache.org
Date: Fri, 1 Jan 2016 12:29:40 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: dev@singa.incubator.apache.org
Message-ID: <JIRA.12902272.1443896613000.1101.1451651380334@Atlassian.JIRA>
In-Reply-To: <JIRA.12902272.1443896613000@Atlassian.JIRA>
References: <JIRA.12902272.1443896613000@Atlassian.JIRA>
 <JIRA.12902272.1443896613387@arcas>
Subject: [jira] [Commented] (SINGA-81) Add Python Helper, which enables
 users to construct a model (JobProto) and run Singa in Python
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Commit 9ff176c304efddb9169d20f7c213be9c222edf17 in incubator-singa's branch refs/heads/master from chonho
[ https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git;h=9ff176c ]

SINGA-81 Add Python Helper

- Revise src/driver.cc to skip the case of no conf file
- Change import path for datasets in example python codes
- Format python codes and Add license message
- Update README.md


> Add Python Helper, which enables users to construct a model (JobProto) and run Singa in Python
> ----------------------------------------------------------------------------------------------
>
>                 Key: SINGA-81
>                 URL: https://issues.apache.org/jira/browse/SINGA-81
>             Project: Singa
>          Issue Type: New Feature
>            Reporter: Lee Chonho
>
> Proposed design v1
> - (1) have a class named Builder
>    * (2) use Boost::parameter library (+ associated necessary header files)
> (1)
> Builder class implements api-like functions to configure JobProto including NetProto (LayerProto), ClusterProto, UpdaterProto, etc.
> Two options
> a. users call Builder's functions in main.cc like
> {code}
> JobProto jobproto;
> Builder builder( &jobproto, "job name" );
> builder.xxx(xxx)  // add data layer
> builder.xxx(xxx)  // add parser layer
> ... etc. ...
> {code}
> b. we set main.cc like below and users call Builders functions in Construct() 
> {code}
> JobProto jobproto;
> Builder builder( &jobproto, "model name" );
> builder.Construct()
> {code}
> (2)
> Planning to use header-only files from Boost library
> - if the necessary files are small enough
> - because we can use "named arguments" feature with no restriction of # of arguments, order, types.
> - because function will be intuitive, and adding users' own proto in a straightforward way.
> Example is here. http://theboostcpplibraries.com/boost.parameter
> By following the example, we can do like
> {code}
> BOOST_PARAMETER_MEMBER_FUNCTION(   
>  (char*), AddLayerData,   tag,   
>  (required     
>    (type, (int))  (name, (char*))  (src, (char*))
>  ) 
>  (optional     
>    (path, (char*), *) (bsize (int) *)
>  ) )
>  {
>     ...  // set values
>     return name;
>  }
> {code}
> Then, users can add a datalayer by
> {code}
> L1 = builder.AddLayerData(kShardData, "data", null, _path="train_shard", _bsize=1000);
> {code}
> (TODO)
> - make use of google protobuf reflection for efficient parameter setting
> - need to avoid multiple calls for adding same/similar layers
> Any suggestion, design idea, comments please.


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