CodeForPhilly / CodeForPhilly/chime
Chime model & curve behavior
- Lenguaje dominante
- Python
- Estrellas
- 210
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Hello, I am working directly with a hospital from Porto, Portugal. I have been using this amazing tool to simulate the number of UCI which is very important for us. However, I am having some trouble trying to understand a few things.
- First this social interaction reduction. Here, we have to reduce this for almost fifteen days. If I use the current day, it will assume that these changes start now, which is not what's happening. What is the best approach here? Use a different starting day, i.e, the day where the measures kicked in and see how the curve behaves until the current day and afterward?
- The second question is how the curve behaves after that. I can see it goes down for the length of hospital stay that you define and then it goes up indefinitely. Is this the right behavior? It is not easy to explain this phenomenon to someone that will actually use this tool. I would think that it followed a logistic curve and reach the plateau phase in the future or something like that.
- Third, is it possible to use a model implemented by me and then use the tool to calculate the ICU and Ventilation based on my infected case fit?
Congratulations on this amazing tool and for your effort to serve the community in these hard times. I believe you are making an impact and that's a wonderful thing to see. I hope I can keep using it and improve our methodology 😃
My curve:

Guía de contribución
Línea de trabajo
No se identifica ningún archivo fuente, prueba ni punto de entrada. Empieza por localizar los cálculos de reducción de la interacción social y de las curvas de ICU/ventilation, y después reproduce los tiempos indicados y el comportamiento posterior a la estancia hospitalaria. Una resolución útil debería responder a esas preguntas de modelado y determinar si se admiten modelos ajustados personalizados, con un alcance concreto para cualquier implementación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- data
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100