X-Git-Url: https://bilbo.iut-bm.univ-fcomte.fr/and/gitweb/loba.git/blobdiff_plain/23529d55ccbfd0a851fdc86708320811ddda8ec4..1f1654801b021f79ab05c5a9d0dddc766c423d17:/TODO?ds=inline

diff --git a/TODO b/TODO
index 3152ad9..0d476f4 100644
--- a/TODO
+++ b/TODO
@@ -1,31 +1,30 @@
-* segfault with ./loba cluster1000.xml -N64 -a fairstrategy
+* Create git repo for papers.
+   Done.
 
-    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!
+* Implement algorithm discussed on Feb. 23 with R.C.
 
-* verify bookkeeping version.
+* Implement makhoul2 algorithm?
+   See source code for omnet++.
 
-* add several metrics
-  - flops (total, avg, stddev)
-  - message exchanges (number, volume)
+* Implement some random initial distribution of load
+   Options -r seed, -R [algo ?]
 
-* add options -j/-J : minimum number of iterations ?
+* Support heterogeneous platforms?
+   Not sure yet.
+   Should be doable if each process also sends its speed to its neighbors.
 
-* add a variant to (not) change neighbor load information at send.
+* Add options -j/-J : minimum number of iterations?
 
-* implement loba_* algorithms (start with some trivial one)
+* Add options -f/-F : termination based on flops achieved?
 
-* for automatic process topology,
-   -> implement some random initial distribution of load
+* Choose a license before making the code public.
+   CeCILL-B?
 
-* add synchronized mode
+* Translate french parts in english (README, QUESTIONS, ALGORITHMS, ...)
+   Not urgent.
 
-* translate README file?
+* Add synchronized mode?
+   No.
+
+* Add a variant to (not) change neighbor load information at send?
+   No.