# HG changeset patch # User Razvan Pascanu # Date 1285199992 14400 # Node ID 31b72defb680045fdd52e6ba9a51857b3b956fcc # Parent 515033d4d3bf77d30d8788d961dc5dbe9a93afee requirements september 21 diff -r 515033d4d3bf -r 31b72defb680 doc/v2_planning/requirements.txt --- a/doc/v2_planning/requirements.txt Wed Sep 22 19:43:24 2010 -0400 +++ b/doc/v2_planning/requirements.txt Wed Sep 22 19:59:52 2010 -0400 @@ -121,3 +121,27 @@ 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. + + +Requirements from meeting 21 September: +( some of them share things with the requirements above ) + +R15. If you see the library as a driver that controls several components ( and +we argue that any approach can be seen like this), the driver should always : + - be serializable + - respond to internal interrupts ("checkpoints") + - respond to external interrupts ( timeout) + - async interrupts ( eg. SIGTERM) + +R16 Cognitive load should be minimal (debatable requirement) + Notes : Is hard to actually appreciate cognitive load, so this should be + a soft requirement, or in other words, from all proposal that respect all + other requirements the one with least cognitive load should be selected. + +R17 The library should allow surgery on long-running jobs + +R18 Distributed Computation + The library should be able to support at least the followings : + - lunch jobs transparantly across networks + - resume jobs ( or continue jobs ) +