-* segfault with ./loba cluster1000.xml -N64 -a fairstrategy
+* Support heterogeneous platforms?
+ Not sure yet.
+ Should be doable if each process also sends its speed to its neighbors.
- 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!
+* Add options -j/-J : minimum number of iterations?
-* verify bookkeeping version.
+* Add options -f/-F : termination based on flops achieved?
-* add several metrics
- - flops (total, avg, stddev)
- - message exchanges (number, volume)
+* Choose a license before making the code public.
+ CeCILL-B?
-* add options -j/-J : minimum number of iterations ?
+* Translate french parts in english (README, QUESTIONS, ALGORITHMS, ...)
+ Not urgent.
-* add a variant to (not) change neighbor load information at send.
+* Add synchronized mode?
+ No.
-* implement loba_* algorithms (start with some trivial one)
-
-* for automatic process topology,
- -> implement some random initial distribution of load
-
-* add synchronized mode
-
-* translate README file?
+* Add a variant to (not) change neighbor load information at send?
+ No.
