Most of those were for debugging purposes and can be simply removed.
Of course, the behavior of the program should otherwise not be changed, but I think that would be the case when simply dropping the print-calls.
If some of the currently existing print-calls look like they are actually directed toward the user of the program (e.g., that might be the case for message printouts from/after the file selection dialog), these could be replaced by GUI message boxes.
Most of those were for debugging purposes and can be simply removed.
Of course, the behavior of the program should otherwise not be changed, but I think that would be the case when simply dropping the
print-calls.If some of the currently existing
print-calls look like they are actually directed toward the user of the program (e.g., that might be the case for message printouts from/after the file selection dialog), these could be replaced by GUI message boxes.And if some of the currently existing
print-calls look like they would be really useful for understanding the behavior of the program (say, during future extensions), then they could be redirected from consoleprinting to the more systematic logging facility that appears to be set up here: https://github.com/fmidue/sd-simulate/blob/601e3ea020a58b1ce74a3c7a49e0d2e89e1fdcc7/src/config.py#L28-L32