Mercurial > pylearn
diff doc/v2_planning/architecture.txt @ 1153:ae5ba6206fd3
a first draft of pseudo-code for logreg .. using version B (?) approach
| author | Razvan Pascanu <r.pascanu@gmail.com> |
|---|---|
| date | Thu, 16 Sep 2010 17:34:30 -0400 |
| parents | 40c1461ce9ef |
| children | f111f8c2a280 |
line wrap: on
line diff
--- a/doc/v2_planning/architecture.txt Thu Sep 16 17:11:10 2010 -0400 +++ b/doc/v2_planning/architecture.txt Thu Sep 16 17:34:30 2010 -0400 @@ -116,6 +116,12 @@ convert it into the pipeline given in the linear version. It's still possible though, but this is probably not the place to get into the details. +RP comment : The way I see it, you could always have everything using the +encapsulation paradigm ( which as you pointed out is a bit more powerful) and +then have linear shortcuts ( functions that take a list of functions and some +inputs and apply them in some order). You will not be able to have a one case +cover all pipeline function, but I think it is sufficient to offer such +options (linear functions) for a few widely used cases .. Jobman Compatibility Approach