-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional minimal file retention mode #39
Comments
I am not sure it is a good idea or at least that it is worth the effort. 😅 How many files do we store that you would get rid of in this new mode? Could you make a folder tree as example and somehow mark what is kind of superfluous? 🤔 |
Everything except the final particle list from the Afterburner is eventually superflous. |
I believe this is way more intricate that it might sound. We offer full flexibility, so we cannot even assume the
This sentence makes me guess that you would like this feature to happen on the way internally to the sampler. Something like: Once I set-up and I am about running a given phase, I can delete everything about previous phases that is not input for what I am about to run. And once I did the last one, I remove everything but the result. Would this still be fine in case of failure? What about reproducibility? In that mode we would need to store the full hybrid handler config file as part of "the result". 🤔 |
I agree. In case of failure, we usually know that the failure happened in the phase currently running, as this setup is anyway rather for well-tested production. If a stage successfully finished, the user should have the functionality to remove its files. |
Users should have the option to only preserve/generate the minimum amount of intermediate files. By default we keep a lot of files, in order to keep track of the process, but an experienced user should be able to use a more lustre friendly execution mode.
The text was updated successfully, but these errors were encountered: