Mercurial > pylearn
changeset 1239:470beb000694
merge
author | Yoshua Bengio <bengioy@iro.umontreal.ca> |
---|---|
date | Thu, 23 Sep 2010 11:49:42 -0400 |
parents | 067b2f9ba122 (diff) 32fc5f442dde (current diff) |
children | 317049b21b77 |
files | |
diffstat | 1 files changed, 26 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/v2_planning/arch_src/plugin_JB_comments_YB.txt Thu Sep 23 11:49:42 2010 -0400 @@ -0,0 +1,26 @@ + +YB. I am very worried about this proposal. It looks again like we would be +creating another language to replace one we already have, namely python, +mainly so that we could have introspection and programmable changes +into an existing control flow structure (e.g. the standard DBN code). + +I feel that the negatives outweigh the advantages. + +Please correct me: + +Disadvantages: + +* much more difficult to read +* much more difficult to debug + +Advantages: + +* easier to serialize (can't we serialize an ordinary Python class created by a normal user?) +* possible but not easier to programmatically modify existing learning algorithms + (why not the usual constructor parameters and hooks, + when possible, and just create another code for a new DBN variant when it can't fit?) +* am I missing something? + +I am not convinced that any of the stated advantages can't be achieved in more traditional ways. + +