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

Flesh out multiple simulated scenarios vs one long one #52

Closed
seabbs opened this issue Feb 19, 2024 · 5 comments · Fixed by #322
Closed

Flesh out multiple simulated scenarios vs one long one #52

seabbs opened this issue Feb 19, 2024 · 5 comments · Fixed by #322
Assignees

Comments

@seabbs
Copy link
Contributor

seabbs commented Feb 19, 2024

Based on discussion in #34 we need to flesh out that our approach will use multiple simulated scenarios vs one long one because of potential issues at different absolute incidence levels and as it will be easier to communicate.

@seabbs
Copy link
Contributor Author

seabbs commented Feb 21, 2024

@zsusswein I think you had precise thoughts on this. Any chance you have them noted down?

@seabbs seabbs modified the milestone: EpiAware 0.1.0 Feb 29, 2024
@seabbs
Copy link
Contributor Author

seabbs commented Mar 5, 2024

Flagging this is still stuck waiting on notes from @zsusswein

@SamuelBrand1
Copy link
Collaborator

Bump @zsusswein

@zsusswein
Copy link
Collaborator

zsusswein commented Jun 27, 2024

This has become a bit fuzzy with time, but I remember some of the following:

  • We want to put the different modeling approaches through their paces with a few scenarios. These may include a step change in Rt, constant-ish Rt, sinusoidal structure, other stuff. The exact details of these aren't important for this particular discussion.
  • I had originally pitched these different cases as components of one long composite timeseries. I thought (and still think!) it would simplify visualization and presentation a bit. I also generally like the idea of forcing a single model fit to contend with different orders of magnitude of incidence as a "more strenuous" test -- sort of along the lines of bumping true $R_t$ to the high end of a plausible range to make bias more obvious.
  • But @seabbs pointed out the models are non-adaptive and we'd likely face some serious (and largely incidental to our question) model fitting issues. I think that's a fairly convincing argument and evaluation should be on multiple shorter timeseries each of which is an interesting test in some way.

If I remember correctly, both SamA and SamB were in the "multiple shorter timeseries" camp and I've been convinced. So I think we have consensus here and SamA just wanted this issue for documentation.

@seabbs
Copy link
Contributor Author

seabbs commented Jul 2, 2024

@SamuelBrand1 this is the issue were just looking for. Current plan is to look across 4 scenarios (2 outbreak and 2 endemic) with varying levels of complexity.

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

Successfully merging a pull request may close this issue.

3 participants