I stumbled upon this workshop template when looking for inspiration for an internal targets training for my organization. This is all very well done, and I have found it really useful to poke around.
I did want to mention that in the section about maintaining package versions, one important aspect of renv is now (thankfully) out of date. As of renv 0.13.2 (2021-03-30), renv can parse the packages in targets::tar_option_set().
This may also impact the preference away from using targets::tar_option_set() in Issue #22. For another (and completely unsolicited) option, I tend to teach folks that using library() is helpful if you are relying on a package for building the pipeline (common examples: tarchetypes or tibble, especially when static branching), and tar_option_set() is helpful for packages used when running the pipeline (i.e., functions within a target.
Hope this is useful... if not, feel free to disregard and close the issue :)
I stumbled upon this workshop template when looking for inspiration for an internal targets training for my organization. This is all very well done, and I have found it really useful to poke around.
I did want to mention that in the section about maintaining package versions, one important aspect of renv is now (thankfully) out of date. As of renv 0.13.2 (2021-03-30), renv can parse the packages in
targets::tar_option_set().This may also impact the preference away from using
targets::tar_option_set()in Issue #22. For another (and completely unsolicited) option, I tend to teach folks that usinglibrary()is helpful if you are relying on a package for building the pipeline (common examples: tarchetypes or tibble, especially when static branching), andtar_option_set()is helpful for packages used when running the pipeline (i.e., functions within a target.Hope this is useful... if not, feel free to disregard and close the issue :)
All the best, Anthony Martinez