Replies: 1 comment 1 reply
-
If the output of the new function is indeed exactly the same, you are correct that the It may seem this way when you look at the dependency graph, but that is because {targets} has no way to know what the output will be until it actually runs the code. The "outdated" targets in the dependency graph are only estimates. The graph is accurate in terms of the dependency relationships, but it cannot actually predict precisely which targets will be run with the next |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Help
Description
Is there a way to do the opposite of
tar_invalidate()
i.e. make a target that is outdated up to date without rerunning it viatar_make()
? I can't find any documentation on this issue.My use case is that I have a helper function e.g.
read_data()
that is used by many targets.At some point, I update this function with some new features.
Now all my targets that use this function are outdated. But I know that this new feature is not relevant to the old targets. In this case, the new
sep
argument is the default forread.csv
so the result ofread_data("my.csv")
will be identical with the old and new functions.Now I could just run
tar_make()
but suppose that I have a large workflow with hundreds of files that are GB in size, and have plenty of downstream processing. This could be hours or days of computation to recreate the targets that I already have.There should be a simple way to say "this outdated target is actually up to date".
Beta Was this translation helpful? Give feedback.
All reactions