When config.py is changed, the timestamp is updated and all outputs are routed to the new storage directory, which doesn't exist.
Proposed quick solution: Change the example configuration on the lobster webpage so that it does not use the timestamp. Optionally, include information about how lobster handles immutable parameters.
Including a timestamp in the directory name results in runtime errors when config.py is edited mid-run.
Example of timestamp:
When config.py is changed, the timestamp is updated and all outputs are routed to the new storage directory, which doesn't exist.
Proposed quick solution: Change the example configuration on the lobster webpage so that it does not use the timestamp. Optionally, include information about how lobster handles immutable parameters.