We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I think the two packages fill 2 different niches and it's good to keep them both alive (especially since both of them are already on CRAN).
However, we should make sure that they play well together and that it is easy for users to go from one to the other.
It might also be useful to provide a shared S3 class for contact matrices so we can write common methods.
See also: epiforecasts/socialmixr#55
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I think the two packages fill 2 different niches and it's good to keep them both alive (especially since both of them are already on CRAN).
However, we should make sure that they play well together and that it is easy for users to go from one to the other.
It might also be useful to provide a shared S3 class for contact matrices so we can write common methods.
See also: epiforecasts/socialmixr#55
The text was updated successfully, but these errors were encountered: