Stage

Testing

README

Hey! If you're at this page you're hopefully looking to help out with the CHIME project. Please join us in Slack or on github to join in!

Help needed

In order to ensure the CHIME team can focus on modeling and interacting with stakeholders, we're looking for help filling the following roles:

  • Project / product management: help with organizing the project. Help make sure that work around explaining and improving the CHIME dashboard is well organized. Help us document the project so volunteers can contribute.

  • Devops: help ensure that the dashboard can handle the increase in traffic. Currently we are running on Heroku, but may switch to Linode, since they have provided free resources.

  • Python: help us improve, maintain, and develop the app

Project Activity

Update #4

CHIME 2.0 kickoff!

Due to the model's diminishing returns as the epidemic progresses, the app is going to undergo some model and platform updates so it can continue to be a resource for decision makers!

The next iteration of CHIME development will move to

  1. Make the model it's own package so development of the model happens independently from the platform

  2. Move platform to tech that allows user to import csv

  3. Update model to use better methods of estimating parameters

We're looking for python developers with data modeling (especially Bayesian methods) experience or Dash experience!

Update #3

Getting a lot of requests for updating/improving the code. Need to consider more in-depth frameworks for testing python code and turning app script into modules. Experienced python developers - come thru!

Update #2

Code for Philly set up a fork of the repository today to help manage incoming user and contributor interest: https://github.com/CodeForPhilly/chime

Major efforts in the new repository included:

  • Setting up a documentation site and consolidating knowledge: https://codeforphilly.github.io/chime/
  • Developing a kubernetes deployment: https://github.com/CodeForPhilly/chime/tree/master/k8s
  • Deploying a pre-production version of the application to Linode's LKE managed kubernetes: http://lke.penn-chime.phl.io/

Next up

  • Merge improvements from pennsignal's repository
  • Expand documentation on how to test the Kubernetes deployment locally on minikube
  • Automate building container and deploying to LKE on merge to master with GitHub Action workflow
  • Add documentation on how local groups can set up their own production deployment

Update #1

Chime is officially launched! See this tweet, and accompanying blog post for more details. The team is now focused on two things:

  1. implementing features requested by government and medical system stakeholders
  2. ensuring we can scale to support the traffic coming in

Help needed

In order to ensure the CHIME team can focus on modeling and interacting with stakeholders, we're looking for help filling the following roles:

  • Project / product management: help with organizing the project. Help make sure that work around explaining and improving the CHIME dashboard is well organized. Help us document the project so volunteers can contribute.
  • Devops: help ensure that the dashboard can handle the increase in traffic. Currently we are running on Heroku, but may switch to Linode, since they have provided free resources.