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

Adding a more realistic testing policy #39

Open
DAM-Philippon opened this issue Jun 7, 2020 · 0 comments
Open

Adding a more realistic testing policy #39

DAM-Philippon opened this issue Jun 7, 2020 · 0 comments
Labels
enhancement New feature or request policy Anything related to the policy part of the model
Milestone

Comments

@DAM-Philippon
Copy link
Contributor

Currently, the testing policy is using three different parameters: the capacity in terms of test per hour, testing only symptomatic people, and allowing tests on the same Individual at different time steps.

While this is useful, it still remains over-simplistic. I've looked at the data in terms of testing (PCR) capacity for Vinh Phuc, and actually, there is none. This does not automatically means that no testing should be performed, but that samples are being sent to another province/clinic.

This "trip" should be represented, as it may induce a delay between the test being performed and the response (i.e. sending the Individual to quarantine, for instance), possibly letting one infectious Individual infecting others.

One possible way would be to keep in memory tests being perform for an Individual in a map, and "release" the answer after X steps (days) have passed. This delay would be added as an attribute of the new DelayedDetectionPolicy.

@DAM-Philippon DAM-Philippon added enhancement New feature or request policy Anything related to the policy part of the model labels Jun 7, 2020
@DAM-Philippon DAM-Philippon added this to the V2 milestone Jun 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request policy Anything related to the policy part of the model
Projects
None yet
Development

No branches or pull requests

1 participant