-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
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
Standard surveillance output #165
Comments
I think this is a really good idea. Should be reasonable to achieve, we want or already have the functions to fill this in. We can also add a pretty print to the struct so you get a lot of information (Unicode plots even?) |
I think we want more pretty printing of structs in general and wondered if there was a package out there. Can't find anything right now though |
Aside from structs are there any other data structures (and links please) we could be thinking about here to use to control dispatch? |
I think the canonical way of doing this is overloading |
Yeah I saw this and I was wondering if anyone had already done work on that for this kind of use case |
This kind of thing: https://github.com/MechanicalRabbit/PrettyPrinting.jl |
I think we want to define some standard surveillance output for
_make_epi_aware
as this will help with postprocessing and be of general utility (given the aim of the tooling).I think the way to we want to do this is to create a new abstract function in
EpiAwareBase
that is called in the return of_make_epi_aware
and dispatches on theEpiInfModel
type used. This is so that we can have a generic method that just uses the expected infections for its metrics and more specific methods that use the already computed reproduction number estimates and growth rate calculations.Alternatively, we could consider this as a post-processing step for the model output (i.e it works with a for object) but I think its nice to make use of the struct information we have to provide custom solutions which I think favours doing this in model (albeit only as part of the generated quantities).
This would look like
I'm thinking about the return as a struct as then we can build postprocessing that interfaces with this w/ some guarantee of correctness. Not sure this really makes sense or is the right way to think about it so would appreciate thoughts @SamuelBrand1?
The text was updated successfully, but these errors were encountered: