For all intents and purposes this is a minor bug of the programme. An instance where this can come up is when the output folder is being monitored by some process (e.g. watchdog for python or inotifywait -from inotify_suite- running on Linux) for read and write events.
It is highly likely that this condition causes race conditions which result in the monitoring process not behaving as it is intended.
An example of how this warning can occur is the following:
Beginning simulation
sh: 1: /output_path/testing_time_100.h5: Permission denied
Writing file after 100 days: Done.
sh: 1: /output_path/testing_time_200.h5: Permission denied
Writing file after 200 days: Done.
...
Most likely the programme is trying to open for some operation any .h5 file in question right before it is created.
For all intents and purposes this is a minor bug of the programme. An instance where this can come up is when the output folder is being monitored by some process (e.g. watchdog for python or inotifywait -from inotify_suite- running on Linux) for read and write events.
It is highly likely that this condition causes race conditions which result in the monitoring process not behaving as it is intended.
An example of how this warning can occur is the following: Beginning simulation sh: 1: /output_path/testing_time_100.h5: Permission denied Writing file after 100 days: Done. sh: 1: /output_path/testing_time_200.h5: Permission denied Writing file after 200 days: Done. ...
Most likely the programme is trying to open for some operation any .h5 file in question right before it is created.