Targetting locations by location-specific riskiness
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- r
- Domain
- machine-learning
Research direction
Read PR #101 for the setting-specific riskiness work and PR #93 for the far UVC targeting strategies. The issue does not identify files, tests, or a specific implementation target; first determine how those changes represent locations and risk. Done would mean defining and implementing a strategy that targets locations according to their risk, including the intended terminology and scope.
Written by the indexing model from the issue text.
Description
In PR #101 we add "setting-specific" (or "location-specific" -- unsure) riskiness. It would be of interest to include far UVC targetting strategies (see e.g. PR #93) involving installation in locations (or settings) which happen to have higher risk (corresponding to lower ventilation etc.).
- Dominant language
- R
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from petal-code/helios
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
petal-code/helios#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
petal-code/helios#173 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
petal-code/helios#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
petal-code/helios#161 ·
-
run_simulation() is not reproducible from seed: the leisure draw uses dqrng's own RNGPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
petal-code/helios#157 · 1 comment ·
All issues in petal-code/helios
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
atomashevic/transforEmotion#46 ·
Maintainers usually reply within 1 day
-
`pk.calc.time_above()` with lin-up/log-down silently drops segments that end at a negative valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Error when applying yearCohorts() to a cohort created with generateTargetDenominatorCohortSet()Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OHDSI/CohortConstructor#777 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nmfs-ost/stockplotr#445 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day