-
Notifications
You must be signed in to change notification settings - Fork 0
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
Instantiate infections earlier? #67
Comments
@swo I'm making this issue mostly so I can write out why I have come to think this is a bad idea. The short version is that I think we're already teetering on the edge of ungeneralizable counterfactualism and this would push us over the edge. Right now, we have infections generating the entire vector of times they might end up infecting others. This is only possible in certain kinds of models, like the current density-independent branching process. In a model with a network, or if we want to account for depletion of susceptibles, we cannot do this. In the general sense, this is because the infections caused by individuals are no longer independent. More specifically, we can think of it as being because an individual doesn't have an infection rate, they have an infection rate function, and this function is dependent on other aspects of the state of the population. So the earliest we actually really want to be instantiating an infection is when it's next in the queue, because after we know what the next infection is, we may need to re-generate the entire queue. |
Even if we keep the scope here to just this branching process approach? I've been thinking we keep the scope of this repo to just that question. If we want to do network simulations, we'll do that outside of a widget. This should be simple and purpose-built. |
Yes. We'd have to commit to a subset of branching processes where the infection rate What does "more or less" mean? For a model where there's a dependence on the total number of infections So, besides networks we can't do anything too close to a proper compartmental model, because there But we could do:
|
If you're happy with drawing that box around what this app can do, I've got a branch I can revive where I was working on this before I had these thoughts. |
Per this thread
The text was updated successfully, but these errors were encountered: