Far UVC coverage for leisure venues?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- r
- Domain
- machine-learning
Research direction
Start by reading generate_setting_far_uvc_switches and trace how it assigns far UVC to leisure venues. Check how leisure attendance is represented and whether individuals' weekly attendance is fixed or redrawn. The issue is resolved when the leisure venue targeting accounts for attendance rather than venue size, with the attendance behavior clarified.
Written by the indexing model from the issue text.
Description
In generate_setting_far_uvc_switches we have particular targetting approaches for all settings.
I think that there might be a relevant difference about the leisure venue which means that we need a different approach. In particular, leisure venues do not have fixed occupancy. So for example you could set far UVC to be on in the biggest leisure venues, but perhaps those venues happen not to be the most attended.
Also, to clarify, individuals have the same leisure attendance each week right? It's not redrawn? If so that'd be another complication.
Let me know if this doesn't make sense and I can make it clearer (if I am correct).
- 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 ·
-
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 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tidymodels/censored#414 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
waldronlab/bugphyzz#256 ·
-
dbRemoveTable() fails on SQLite with 'near "TRUNCATE": syntax error' and leaves the table in placePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OHDSI/DatabaseConnector#348 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100