Prework

• Read and agree to the code of conduct and contributing guidelines.
• If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.
• For any problems you identify, post a minimal reproducible example like this one so the maintainer can troubleshoot. A reproducible example is:
  • Runnable: post enough R code and data so any onlooker can create the error on their own computer.
  • Minimal: reduce runtime wherever possible and remove complicated details that are irrelevant to the issue at hand.
  • Readable: format your code according to the tidyverse style guide.

Question

Hi @wlandau,

I was wondering if it would be reasonable to have it so the dependency graph in tar_watch() could somehow show within-target progress when using dynamic branching. In other words, somehow show how many branches out of N total branches have been built.

I suppose this would mean adding some functionality to tar_visnetwork() since this powers tar_watch(). But it seems to me that at runtime a few things are known:

1. How many total branches belong to a given target

2. How many of those branches requiring being built/re-built

tar_watch() knows once ALL branches are built for a target, but not at a more granular level.

If this information could be shared in some way with tar_visnetwork(), it would be nice to present it to give a sense of within-target progress. Also, with dynamic branching sometimes we may not know how many branches we are even creating, so one cannot easily figure out the progress just by looking at how many branches have finished so far by the textual progress updates.

Thoughts?