Skip to content
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

Function to backcalculate Rt and the growth rate #116

Closed
seabbs opened this issue Mar 6, 2024 · 7 comments · Fixed by #314
Closed

Function to backcalculate Rt and the growth rate #116

seabbs opened this issue Mar 6, 2024 · 7 comments · Fixed by #314
Assignees
Labels

Comments

@seabbs
Copy link
Collaborator

seabbs commented Mar 6, 2024

As shown here:

n = epi_model.data.len_gen_int
Rt_denom = [dot(reverse(epi_model.data.gen_int), true_infections[(t - n):(t - 1)])

We need a function to backcalculate Rt and the growth rate from infections generated in an arbitrary model

@seabbs seabbs added the EpiAware label Mar 6, 2024
@seabbs seabbs added this to the EpiAware 0.1.0 milestone Mar 6, 2024
@SamuelBrand1
Copy link
Collaborator

This is a good idea, but not really implementable in an arbitrary model. Do you mean one with a single infected type as per how we have been doing it?

@seabbs
Copy link
Collaborator Author

seabbs commented Mar 7, 2024

yes and I was thinking we would use it in the generated quantities return and make sure it only got called via multiple dispatch when it would work (would need to have some kind of function that it nested in though not sure what to call that given that generated_quantities is taken...) -> maybe situtational_awareness_metrics()?

@seabbs seabbs self-assigned this Apr 17, 2024
@seabbs
Copy link
Collaborator Author

seabbs commented Apr 17, 2024

Handling this as part of #165

@seabbs
Copy link
Collaborator Author

seabbs commented May 30, 2024

backcalculating Rt is handled in #184

@seabbs
Copy link
Collaborator Author

seabbs commented Jun 28, 2024

Is this complete? I don't think we have a function for the growth rate explicitly (though as it can wrap the Rt one perhaps we do)

@seabbs seabbs reopened this Jun 28, 2024
@SamuelBrand1
Copy link
Collaborator

I'm doing this for the pipeline... which means avoiding dealing with multi-groups. Would that close this issue?

@seabbs
Copy link
Collaborator Author

seabbs commented Jun 28, 2024

Shall we just make a expected_growth or similar to match the current expected_Rt in EpiAware and use that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants