Mercurial > pylearn

comparison doc/v2_planning/committees.txt @ 1006:49eea4953efe

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
job of each committee
author Yoshua Bengio <bengioy@iro.umontreal.ca>
date Thu, 02 Sep 2010 21:59:22 -0400
parents 5753cd864356
children 0ed99521bc45
comparison
equal deleted inserted replaced
1005:5753cd864356 1006:49eea4953efe
1 List of committees and their members: 1 List of committees and their members:
2 2
3 Python ML libraries investigation: GD, DWF, IG, DE 3 * Existing Python ML libraries investigation: GD, DWF, IG, DE
4 Dataset interface: DE, OB, OD, AB, PV 4 * Dataset interface: DE, OB, OD, AB, PV
5 Learner: AB, PL, GM, IG, RP 5 * Learners: AB, PL, GM, IG, RP
6 Optimization: JB, PL, OD 6 * Optimization: JB, PL, OD
7 Inference/sampling: JB, GD, AC 7 * Inference/sampling: JB, GD, AC
8 Job management, analysis, metrics, costs, visualization: GD, FS, PL, XM 8 * Job management, analysis, metrics, costs, visualization: GD, FS, PL, XM
9 Formulas/tags: FB, NB, RP, AC, OB 9 * Formulas/tags: FB, NB, RP, AC, OB
10 Coding style: DE, OD, DWF, FB 10 * Coding style: DE, OD, DWF, FB
11 11
12 Issues to be tackled in the future:
13
14 * serialization & reproducibility
15 * job management, results analysis, metrics & costs, visualization
16 * GPU portability
17 * social engineering, code review and incentives
18
19 Job of each committee:
20
21 * name a leader
22 * create a text file in this directory associated with their discussion
23 * discuss the issues, write them down in this file
24 * come up with an interface, protocol, or recommendations
25 * bring up the issues and recommendations to the rest of the group, and get feedback
26 * make sure the recommendations fit with other committees recommendations
27 * update the discussion / recommendation file
28 * implement documentation for these conventions in python or proper doc files as appropriate
29 * implement one or a few examples that show what is typically expected
30