ENH: Support grouping devices
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 9
- Avg merge
- 7d 14h
- Merged PRs (30d)
- 1
Description
Expected Behavior
Support devices that are tightly coupled together, and may possibly affect multiple beam paths.
Current Behavior
Currently each device is expected to reside on a single branch, unless it is itself a branching device.
To address this problem, we simply made copies of the offending device and dropped it into each beam path. This made the device visible in all the paths, but the duplicate devices could cause confusion down the line
Possible Solution
Group devices together, and implement veto logic?
Context
Inspired by this ticket, and the case where mec_yag0 was close enough to mr1l4 to block beam for all FEH hutches.
Your Environment
pcds-5.6.0
Contributor guide
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
No files, tests, or entry points are named. Start by tracing how devices are assigned to branches and how beam-path status is calculated, using the mec_yag0/mr1l4 case as context. Clarify the grouping and veto semantics before implementation; done should mean coupled devices are represented without confusing duplicates and affect all relevant beam paths correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100