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

Allow to conciously break consistency #15

Open
maowerner opened this issue Apr 3, 2019 · 0 comments
Open

Allow to conciously break consistency #15

maowerner opened this issue Apr 3, 2019 · 0 comments

Comments

@maowerner
Copy link

The emphasis of paramvalf is to always ensure consistency of the data. This is already circumvented by the -k flag. In case of an error the remainder of a dependency graph is not executed. In practice this leads to deprecated and due to the error currently not reproducible files lying around. In addition it often happens that a minor change (e.g. not using a certain parameter set anymore) makes the framework redo time-intensive parts of the analysis. One workaround is to touch the corresponding output file to fool make but I think there should be some built-in way for the user to take over responsibility.

One way would be a flag like -use gevp.Rdata which tells it to ignore changes to the dependency graph that happened before that.

One more thing is a flag --ensure-consitency which deletes all output and reproduces everything from scratch to completely rule out inconsistent data e.g. from deprecated files that are still used somewhere or not reproduced files due to -k

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

1 participant