James Azam

HI @truenomad, I might have encountered a similar issue in the recent past, which was solved here https://github.com/stan-dev/cmdstanr/issues/790. Try and follow the conversation and see if it helps.

@truenomad Glad it helped.

Thank you for your input @alevan2p. I agree that it adds more clarity.

I believe we moved towards enforcing the use of the `*_opts()` interface because of situations where wrong options are passed to an argument like pointed out here https://github.com/epiforecasts/EpiNow2/issues/337#issuecomment-1420621618. If we...

~The linked comment does not lead anywhere so I'm struggling to get the context. I came here after seeing the code chunk [here](https://epiforecasts.io/EpiNow2/articles/estimate_infections_workflow.html#initial-reproduction-number) probably needs to be updated to use...

> ~The linked comment does not lead anywhere so I'm struggling to get the context. I came here after seeing the code chunk [here](https://epiforecasts.io/EpiNow2/articles/estimate_infections_workflow.html#initial-reproduction-number) probably needs to be updated to...

I'm working on this and have a few questions: > and `observations` as everything else, I think, could be constructed from these three elements using appropriate summary or extract_... methods....

This issue has been partly addressed in the "truncation" section of the workflow vignette introduced in #458 (https://epiforecasts.io/EpiNow2/dev/articles/estimate_infections_workflow.html#truncation). However, reading it from the user perspective, I think, where it says...

I'm cleaning up a few docs here and there to see if it clarifies this. PR incoming soon.

I just came across this rlib .lintr setup that checks if existing or incoming code uses base R condition handlers: https://github.com/r-lib/pkgdown/blob/819cede3fbbb2410912f4d49365177c9159b809f/.lintr.R. We can add it after implementing this.