Mercurial > pylearn

comparison doc/v2_planning/requirements.txt @ 1241:6801451a86bb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add a point I brought during the last architecture meeting.
author Pascal Lamblin <lamblinp@iro.umontreal.ca>
date Thu, 23 Sep 2010 12:02:58 -0400
parents 31b72defb680
children 7b86c1772932
comparison
equal deleted inserted replaced
1240:317049b21b77 1241:6801451a86bb
110 at deserialization time. 110 at deserialization time.
111 111
112 This requirement is aimed at enabling process migration and job control as well 112 This requirement is aimed at enabling process migration and job control as well
113 as post-hoc analysis of experiment results. 113 as post-hoc analysis of experiment results.
114 114
115 PL: I'm not sure it the job should have to return its current state. I think
116 it would be enough that it returns a consistent checkpoint, even if it is from
117 some time in the past (ideally, not more than a few minutes ago).
118
115 OD asks: When you say "The experiment cannot assume that resources written by 119 OD asks: When you say "The experiment cannot assume that resources written by
116 the experiment will still be there", do you mean we should be able to recover 120 the experiment will still be there", do you mean we should be able to recover
117 the exact same output after interrupting an experiment, wiping its expdir, and 121 the exact same output after interrupting an experiment, wiping its expdir, and
118 restarting it? This would mean that any output saved on disk by the experiment 122 restarting it? This would mean that any output saved on disk by the experiment
119 also has to be serialized within the experiment, which may lead to very big 123 also has to be serialized within the experiment, which may lead to very big