Is your feature request related to a problem? Please describe.
I recently ran into a problem: I included a single corrupt image file, and the algorithms failed to segment it. However, the error messages produced were rather generic/vague. Thanks to the excellent documentation (https://brats.readthedocs.io/en/latest/core/segmentation_algorithms.html), I figured out how to save a .log file, which greatly helped in identifying and fixing the problem - but I needed to first manually define saving logs.
Describe the solution you'd like
While I agree it doesn't make sense to save log files all the time (unless the user explicitly adds the flag), it would be nice if, in case of a failure/crash, a log file is automatically saved (and a message printed with instructions on where to find it). I don't know if this is feasible, but it would help a lot in triaging and fixing runtime errors.
Is your feature request related to a problem? Please describe.
I recently ran into a problem: I included a single corrupt image file, and the algorithms failed to segment it. However, the error messages produced were rather generic/vague. Thanks to the excellent documentation (https://brats.readthedocs.io/en/latest/core/segmentation_algorithms.html), I figured out how to save a .log file, which greatly helped in identifying and fixing the problem - but I needed to first manually define saving logs.
Describe the solution you'd like
While I agree it doesn't make sense to save log files all the time (unless the user explicitly adds the flag), it would be nice if, in case of a failure/crash, a log file is automatically saved (and a message printed with instructions on where to find it). I don't know if this is feasible, but it would help a lot in triaging and fixing runtime errors.