Mercurial > pylearn
changeset 1008:a5886b394bda
Updating with talking points from Sept. 2 discussion
| author | Dumitru Erhan <dumitru.erhan@gmail.com> |
|---|---|
| date | Fri, 03 Sep 2010 10:01:02 -0400 |
| parents | 2e515be92a0e |
| children | 6803b57e1da9 |
| files | doc/v2_planning/dataset.txt doc/v2_planning/existing_python_ml_libraries.txt |
| diffstat | 2 files changed, 29 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/v2_planning/dataset.txt Thu Sep 02 22:28:32 2010 -0400 +++ b/doc/v2_planning/dataset.txt Fri Sep 03 10:01:02 2010 -0400 @@ -1,3 +1,14 @@ Discussion of Function Specification for Dataset Types ====================================================== +Some talking points from the September 2 meeting: + + * Datasets as views/tasks (Pascal Vincent's idea): our dataset specification + needs to be flexible enough to accommodate different (sub)tasks and views of + the same underlying data. + * Datasets as probability distributions from which one can sample. + * Our specification should allow transparent handling of infinite datasets (or + simply datasets which cannot fit in memory) + * GPU/buffering issues. + +Commiteee: DE, OB, OD, AB, PV
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/v2_planning/existing_python_ml_libraries.txt Fri Sep 03 10:01:02 2010 -0400 @@ -0,0 +1,18 @@ +Committee members: GD, DWF, IG, DE + +This committee will investigate the possibility of interfacing and/or +borrowing from other Python machine learning libraries that exist out there. +Some questions that we need to answer: + + * How much should we try to interface with other libraries? + * What parts can we and should we implement ourselves and what should we leave + to the other libraries? + +Preliminary list of libraries to look at: + + * Pybrain + * MDP + * Orange + * Shogun python bindings + * libsvm python bindings +