Open PierreLaville opened 4 months ago
Same goes for multiprocess_aams.py which has a very similar function (launch_aams_pipeline
) which may cause a similar error.
This is also the case for the "y/N" question mentioned in #7, even if "no" is selected, still prints "done".
Ok, that means we need to implement a system with lock files or result files that are tested for existence after it is run.
When running multiprocess_ams.py and facing an error (here was simply forgetting to activate the Conda environment) and didn't output anything, still prints the success message:
This either needs a more robust way to check wether the run is successful or not, or should not print this.