simulations: decide what to do with legacy simulations

[tahini]

Current work is being done to allow to execute of transit network design using the evolutionary algorithm. Since it could only be run through the CLI, the whole wrapping around the evolutionary algorithm is being refactored, to turn them into ExecutableJob, configured at each run.

What to do about the legacy "simulations"?

• Just silently delete them, assuming no-one has an instance using them?
• Propose a migration plan to turn previous simulation runs into completed jobs to store the results and allow to consult them?
• Keep the parallel simulation framework? (I have no idea why we would do that, but it's an option! it's actually the default option that will be taken until we decide on the future course, with it completely disabled and maybe not even able to run from CLI anymore... fwiw)

[greenscientist]

I think from the previous discussion it was getting that we can start from scratch for the new design. WE don't need to migrate old data.

[greenscientist]

Is it ok if we just leave the old stuff there or is it necessary to delete them?

[kaligrafy]

Delete, nobody except me was using this.

[greenscientist]

[tahini]

Ftr, tout ce qui était utile de Simulation a été migré/recodé/repris dans la branche evolutionaryTransitNetworkDesign. Si qqn veut avoir beaucoup de code rouge à son actif, c'est le moment!!! Sinon, je me lance bientôt :p