The-Strategy-Unit / The-Strategy-Unit/nhp_data
Improve identification of theatres activity
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- Avg merge
- 17h 57m
- Merged PRs (30d)
- 7
Description
per episode, find the greatest op order per date and select these as individual "theatre" cases
Following meeting with @paulseamer / @tomjemmett / @yiwen-h 10/09/2026 on episode level implementation of capacity conversion
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the episode-level capacity conversion logic in the Python data-processing code and inspect how theatre activity is currently identified. Implement the stated per-episode, per-date selection of the greatest op order as individual theatre cases. Done means the resulting theatre cases match that selection rule; add or update tests if existing coverage is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100