Merge branch 'develop' into issue_86

Author: lottspot

.github/CODEOWNERS

@@ -4,6 +4,7 @@ url = "https://pypi.org/simple"
 verify_ssl = true
 
 [dev-packages]
+pytest = "*"
 
 [packages]
 streamlit = "*"

Pipfile

@@ -1,22 +1,46 @@
 # Contributing
 
-When contributing to this repository, please first discuss the change you wish to make via [issue](https://github.com/codeforphilly/chime/issues), [Slack chat](https://codeforphilly.org/chat/covid19-chime-penn), or any other method with the owners of this repository before making a change.
+Welcome, grab a cup of coffee, and let's roll our sleeves up! By participating in this project, you agree to abide by our [code of conduct](CODE_OF_CONDUCT.md).
 
-Please note we have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+## What should I work on?
 
-## Active Needs
+As of March 19, help is especially wanted in these areas:
 
-We maintain a list of [issues in the Code for Philly repo](https://github.com/codeforphilly/chime/issues) that encompasses work requested by stakeholders and technologists.  Each issue is designed to be small enough for one person to implement.
+- **Python wizards** for application development ([#chime-app](https://codeforphilly.org/chat?channel=chime-app))
+  - Hardening the code
+  - Making it more flexible
+  - Unit tests!
+- **DevOps heroes** for application hosting ([#chime-ops](https://codeforphilly.org/chat?channel=chime-ops))
+  - Maintaining Penn's instance
+  - Ensuring easy redeploys
+- **Math and stats friends** for model improvements ([#chime-analysis](https://codeforphilly.org/chat?channel=chime-analysis))
+- **Consulting DevOps champs** to help other public agencies set up their own instances ([#chime-help](https://codeforphilly.org/chat?channel=chime-help)
 
-**Developers** If you are new to the project, check out open issues to see if there is any pre-existing work needed that you can handle. We will need to add your git account to the repo to grant write access - contact us on [Slack](https://codeforphilly.org/chat) in the [covid19-chime-penn](https://codeforphilly.org/chat?channel=covid19-chime-penn) channel.
+## Before You Begin
 
-## Change Management
+- Join the [#covid19-chime-penn](https://codeforphilly.org/chat?channel=covid19-chime-penn) channel, and [request write access](https://codeforphilly.slack.com/archives/CV4NGQYMP/p1584665484368300) to the `CodeforPhilly/chime` Github repository.
+- Our highest-priority work is organized in the [Github Project Management board](https://github.com/CodeForPhilly/chime/projects/2). Look for an issue matching your interests & skills in one of the "Ready" columns.
+- Assign yourself to the issue and add a comment to briefly describe your plan.
+- For new ideas, please first discuss the change(s) you wish to make via [issue](https://github.com/codeforphilly/chime/issues) or appropriate Slack channel (platform/app - #chime-app, devops - #chime-ops, modeling - #chime-analysis). 
 
-- Base all work on the latest `develop` branch available in [Code for Philly's fork of the `chime` repository](https://github.com/CodeForPhilly/chime).
-- Submit your work in the form of a pull request against that same branch.
-- Check in on your pull request periodically after you submit it to see if any changes have been requested or any merge conflicts have arisen from other work getting integrated.
-- If a merge conflict arises, please rebase your branch against the latest `develop` branch and force-push the new branch as early as you can. You may need to do this more than once before your changes get merged. Do your best to keep your branch in a mergeable state until it is finished being reviewed and accepted.
+## Making and Submitting Changes
+
+- [Fork](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) the [CodeforPhilly/chime](https://github.com/CodeForPhilly/chime) repo.
+- Base your work on the `develop` branch.
+- Submit pull requests from your fork, also against the `develop` branch of the `CodeforPhilly/chime` repo.
+- Check your pull request periodically to see if any changes have been requested or any merge conflicts have arisen.
+- If a merge conflict arises, rebase against the latest `develop` branch and force-push the new branch as early as you can. You may need to do this more than once before your changes get merged. Do your best to keep your branch in a mergeable state until it is finished being reviewed and accepted.
+- Note: Frequent contributors with write access can submit pull requests from a new branch in the `CodeforPhilly/chime` repository.
+
+## Review & Release
+
+<!-- Currently establishing & clarifying the release process, this is just a skeleton. -->
+
+- Maintainers will review pull requests, asking for changes as needed.
+- Once a PR has 1 approval and passes automated tests, maintainers will merge to release branches.
+  - Exception: Documentation or infrastructure support PRs can be merged directly to master.
+- Deploys to production must be signed off on by @beckerfluffle or @cchivers.
 
 ## Requesting Functionality
 
-**Stakeholders/Users** Find us on [Slack](https://codeforphilly.org/chat) in the [#covid19-chime-penn](https://codeforphilly.org/chat/covid19-chime-penn) channel to see if your need is already being addressed.
+**Stakeholders/Users**: Check the [#covid19-chime-penn](https://codeforphilly.org/chat/covid19-chime-penn) channel on [Slack](https://codeforphilly.org/chat) to see if your need is already being addressed.

Pipfile.lock

@@ -32,7 +32,7 @@
 
 ## Deploying a New CHIME Version
 
-1. [MaCreateke a new release](release-process.md)
+1. [Create a new release](release-process.md)
 2. Wait for the `Docker` GitHub Actions workflow to complete
 3. Verify the new version shows up at the top as "Latest version" here: https://github.com/CodeForPhilly/chime/packages/155340
 4. Run:

__init__.py

@@ -1,9 +1,11 @@
 from typing import Tuple
 
 import numpy as np
+import streamlit as st
 
 
 # The SIR model, one time step
+@st.cache
 def sir(y, beta, gamma, N):
     S, I, R = y
     Sn = (-beta * S * I) + S
@@ -21,6 +23,7 @@ def sir(y, beta, gamma, N):
 
 
 # Run the SIR model forward in time
+@st.cache
 def sim_sir(
     S, I, R, beta, gamma, n_days, beta_decay=0
 ) -> Tuple[np.ndarray, np.ndarray, np.ndarray]:
@@ -37,7 +40,7 @@ def sim_sir(
     s, i, r = np.array(s), np.array(i), np.array(r)
     return s, i, r
 
-
+@st.cache
 def get_hospitalizations(
     infected: np.ndarray, rates: Tuple[float, float, float], market_share: float
 ) -> Tuple[np.ndarray, np.ndarray, np.ndarray]:

docs/CONTRIBUTING.md

@@ -46,7 +46,7 @@ def display_header(
     st.markdown(
         """*This tool was developed by the [Predictive Healthcare team](http://predictivehealthcare.pennmedicine.org/) at
     Penn Medicine. For questions and comments please see our
-    [contact page](http://predictivehealthcare.pennmedicine.org/contact/). Code can be found on [Github](https://github.com/pennsignals/chime).
+    [contact page](http://predictivehealthcare.pennmedicine.org/contact/). Code can be found on [Github](https://github.com/CodeForPhilly/chime).
     Join our [Slack channel](https://codeforphilly.org/chat?channel=covid19-chime-penn) if you would like to get involved!*"""
     )
 

docs/operations/chime-live-cluster.md

@@ -1,7 +1,8 @@
 import numpy as np
 import pandas as pd
+import streamlit as st
 
-
+@st.cache
 def build_admissions_df(n_days, hosp, icu, vent) -> pd.DataFrame:
     days = np.array(range(0, n_days + 1))
     data_dict = dict(zip(["day", "hosp", "icu", "vent"], [days, hosp, icu, vent]))
@@ -12,7 +13,7 @@ def build_admissions_df(n_days, hosp, icu, vent) -> pd.DataFrame:
     projection_admits["day"] = range(projection_admits.shape[0])
     return projection_admits
 
-
+@st.cache
 def build_census_df(projection_admits, hosp_los, icu_los, vent_los) -> pd.DataFrame:
     """ALOS for each category of COVID-19 case (total guesses)"""
     n_days = np.shape(projection_admits)[0]