You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#' @param data An object with class corresponding to an implemented model.
#' The currently available models classes are `epidist_latent_model` and
#' `epidist_naive_model`.
I think this is fine for now but really we don't want to have to be updating documenation like this when we add a new model.
Instead, I think perhaps we could have some kind of data object or function in the package which lists the available models. Then in documentation we say that you can call epidist_model_classes() to look at them. Or for the data ones we can say that they can call epidist_data_classes().
What do you think @seabbs? I think this is something you've probably encountered before.
The text was updated successfully, but these errors were encountered:
Yes could do. Maybe in the first instance though we jus want to have aim for a vignette that lists the models in a single place and then point to that?
In PR #447 I suggested adding documentation like:
I think this is fine for now but really we don't want to have to be updating documenation like this when we add a new model.
Instead, I think perhaps we could have some kind of data object or function in the package which lists the available models. Then in documentation we say that you can call
epidist_model_classes()
to look at them. Or for the data ones we can say that they can callepidist_data_classes()
.What do you think @seabbs? I think this is something you've probably encountered before.
The text was updated successfully, but these errors were encountered: