RIX paths don't match reality
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 9
- Avg merge
- 7d 14h
- Merged PRs (30d)
- 1
Description
Expected Behavior
- RIX, being one beam pipe, should (probably?) have one beam path associated with it, even if there are 2 endstations
- RIX hutch python should load a lightpath object
Current Behavior
- Currently split into CRIX and QRIX, along K1 and K2 which doesn't quite match the reality of where these endstations are
- RIX hutch python doesn't know which one to load, nor can it without some modifications
Possible Solution
Discuss and collaborate with RIX to figure out the correct/best way to show these
- Combine lightpath to 1?
- Split hutch python into 2? (and fix the start/end points for lightpath)
Context
This broke the lightpath device loading in rix hutch python because hutch is set to "rix" and we only have lightpath configs for "crix" and "qrix"
Your Environment
pcds-5.7.1
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
Start by reproducing the RIX hutch Python lightpath device-loading failure and reviewing the existing CRIX and QRIX lightpath configurations. Work with RIX to decide whether to combine the lightpaths or split the hutch configuration, then verify that RIX loads correctly and its beam paths match the endstation layout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100