Carl A. B. Pearson

also, could embrace the `abbr_function()` convention, and this would look like: ```r res

I imagine that `rbp_parameters()` (or whatever) would roughly be: ```r rbp_parameters

> I'm not a fan of the `rbp_...` syntax. R itself provides a mechanism for that (as you wrote yourself in e.g. `ringbp::parameters()` - which I'm inclined to agree is...

n.b. what I've proposed above would likely close #29 as well (assuming sensible naming conventions).

Some open items maybe to do: - [ ] updating actions to take advantage of the infrastructure addition - [ ] dissecting the vignette builds a bit more to focus...

Sure - I don't know about integration with the actions, but can write the `Makefile` + rules to connect up some examples. I've got some time coming up next week,...

> **Is your feature request related to a problem? Please describe.** > > I use `{epinowcast}` in a containerized pipeline where we try to maximize reproducibility. When building new versions...

Re "antagonistic" - getting runs to produce the precise same results, alongside a fully interpretable audit trail, is going to cost (money, time, sanity, etc) that could be better spent...

@zsusswein calling your attention to this discussion as well: https://community.epinowcast.org/t/epinowcast-command-line-interface/207/3, as that seems pertinent to what you're doing. If you could provide example use cases / user stories / etc,...

Fair re updating the summary/description, but: what is that feature set, precisely? Agree re general update to the README to reflect those different activities, but I'd say the better effort...