+* segfault with ./loba cluster1000.xml -N64 -a fairstrategy
+
+ this is a deadlock occuring when:
+ - a process is in the finalize stage;
+ - all processes but one are blocked on receive;
+ - the process that is still running owns all the remaining load,
+ and sends it all to the finalizing process, and then goes in
+ blocking receive.
+ The finalizing process receives the load, and blocks again,
+ waiting for a close message.
+ All processes are then blocked, and non-one is able to see that
+ there is no more load in the system!
+
+* verify bookkeeping version.
+
+* add several metrics
+ - flops (total, avg, stddev)
+ - message exchanges (number, volume)
+
+* add options -j/-J : minimum number of iterations ?
+
+* add a variant to (not) change neighbor load information at send.
+
* implement loba_* algorithms (start with some trivial one)
-* add loba algorithm selection (-a number ?)
-* fix process::run when load is 0
- -> wait for a message...
- -> how does it work with opt::bookkeeping ???
+* for automatic process topology,
+ -> implement some random initial distribution of load
+
+* add synchronized mode
-* implement automatic process topology
- (line, ring, star, btree, clique, hypercube, etc..)
-* implement automatic platform generation
- (number of hosts, all connected, constant bandwidth/latency)
+* translate README file?
