CodeForPhilly / CodeForPhilly/chime

["model"] Results from running files (models, __init__, parameters, constants, base, validators) from develop branch in notebook differ from CHIME web app census csv download

オープン
#495 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
models
主要言語
Python
スター
210
フォーク
153
PR マージ指標
30日以内にマージされた PR はありません

説明

### Summary
I work for a data science team at a health system, we have limited knowledge/prior experience running docker containers etc so we downloaded (via urllib.request) the files in the src/pnn_chime folder to run locally and output csvs for patient census in each one of our regions our health system covers. code is in attached notebook. fyi, was having problems getting the relative imports to run so I regexed them out so the file could be run by exec().

The output from doing this direct file download and running is different than the output from the CHIME web app even though the same files should be running in both examples

### Additional details
ex row of region data:
Pop | current_hosp | date first hosp | doubling_time | initial_infections | hosp_rate | icu_rate | vent_rate | hosp_los | icu_los | vent_los | market_share
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
604227 | 14 | 3-18-2020 | 7 | 61 | 0.025 | 0.01 | 0.0075 | 7 | 9 | 10 | 0.233

output for that region
[2020-04-05_projected_census.xlsx](https://github.com/CodeForPhilly/chime/files/4435710/2020-04-05_projected_census.xlsx)

python notebook file as text file:
[automated_notebook_to_text.txt](https://github.com/CodeForPhilly/chime/files/4435713/automated_notebook_to_text.txt)

### Suggested fix
unknown

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

Start with the attached automated_notebook_to_text.txt and the files under src/pnn_chime, including models, __init__, parameters, constants, base, and validators. Reproduce the local execution and compare its projected census CSV or XLSX with the CHIME web app download for the provided region; done means the discrepancy is explained and a suggested fix is identified.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
python
領域
data
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
20/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。