Resilience against interrupt
The distributed reconstruction has to be resilient against interruption of the whole reconstruction. Examples:
- User manually interrupts the process ("Ctrl+C")
- Software crash
- All workers lost due to batch scheduler running out of time or "best effort".
An elegant solution would be to save each state of the reconstruction process, and be able to resume from a given state.
Edited by Pierre Paleo