Ben Bolker

hmm. At present AFAICT the `predict` method (`?"predict,mle2-method"`) doesn't support *any* kind of intervals (confidence or prediction)? Maybe I'm missing something? Confidence intervals would probably have to be done by...

Yes, something like that would be the way to do it. I'm in a bit of a quandary over `bbmle`: it works well enough in its current form, but there...

Seems fine. The reason I noticed this in the first place is that your package failed the GitHub actions check (see [here](https://github.com/bbolker/McMasterPandemic/runs/2512077506?check_suite_focus=true)) because you use functions from `stringr` and `forcats`...

Adding `forcats` and `stringr` to DESCRIPTION should be easy, I can do it if you like

Done. There are still testing problems (most critical is that the `check_contact_rate_setting()` example fails. You can *avoid* further GitHub actions testing by including the string "[skip ci]" to the end...

I realize that we *do* use tidyverse in other places, e.g. `pivot.pansim()` method. It's handy. Moving forward need to consider: - whether we can subdivide into "core" (no tidyverse) and...

See also https://github.com/hrbrmstr/freebase

Except for backward compatibility/testing purposes, I don't think rounding is terribly important. I would be willing to put this to one side for now. If/when we get to dealing with...

Maybe add a switch to base-MacPan to **not** round initial values, so you can do comparable runs?

I'm not thrilled about the idea of list-columns. (As previously stated I would like to *avoid* tidyverse constructs wherever possible, because (1) I'm less familiar with them; (2) they don't...