Mercurial > pylearn
changeset 1205:5525cf3faaa2
requirements: Question about the serialization requirement
| author | Olivier Delalleau <delallea@iro> |
|---|---|
| date | Tue, 21 Sep 2010 10:48:01 -0400 |
| parents | d9ffb9ebf8ac |
| children | 203569655069 |
| files | doc/v2_planning/requirements.txt |
| diffstat | 1 files changed, 9 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/v2_planning/requirements.txt Tue Sep 21 10:38:34 2010 -0400 +++ b/doc/v2_planning/requirements.txt Tue Sep 21 10:48:01 2010 -0400 @@ -112,3 +112,12 @@ This requirement is aimed at enabling process migration and job control as well as post-hoc analysis of experiment results. +OD asks: When you say "The experiment cannot assume that resources written by +the experiment will still be there", do you mean we should be able to recover +the exact same output after interrupting an experiment, wiping its expdir, and +restarting it? This would mean that any output saved on disk by the experiment +also has to be serialized within the experiment, which may lead to very big +serialization files (and possibly memory issues?) +A less constraining interpretation of your statement (which I like better) is +that we allow "previous" output to be lost: we only ask that the experiment +should be able to produce the "new" outputs after a wipe+restart.