Skip to content
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

Resume calculation interactions with --force #256

Open
Martin-Rey opened this issue Jun 4, 2024 · 2 comments
Open

Resume calculation interactions with --force #256

Martin-Rey opened this issue Jun 4, 2024 · 2 comments

Comments

@Martin-Rey
Copy link

Hi,

I have greatly appreciated the new features for restoring runs (#245) which have been a big timesaver for HPC tangos applications.

They however interact unexpectedly with the --force keyword. Even if this keyword is passed, if the Tangos runs has previously crashed/was terminated, the calculation resumes from its previous state rather than recomputing from start as expected from setting --force. You can of course delete the cache folder to avoid this, but the point of --force in my mind is to supersede time-gaining manoeuvres (e.g. don't recalculate if properties already exist).

Was this a wanted behaviour from the resume feature, or an oversight?

Martin

@apontzen
Copy link
Member

apontzen commented Jun 4, 2024

The flag you are looking for is actually --no-resume. I kept this separate from --force since they seem logically distinct to me, and one might want one without the other. That said, I think the advice to delete all the resume info is probably not the best — the message should probably point to the flag rather than the brute-force approach.

@Martin-Rey
Copy link
Author

Aha! Many thanks for the pointer, this does exactly what I wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants