Run Number Incorrect for 2nd DAQ
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 9
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 1
Description
Expected Behavior
When connected to second DAQ, we get run numbers from second DAQ
Current Behavior
We always get run numbers from first DAQ
Possible Solution
Investigate the get_lastRun bash script we're running to get the run numbers
Steps to Reproduce (for bugs)
- Go to the secondary daq machine
- Open hutch python
- check
daq.run_number(), compare to primary and secondary experiments
Context
Caused confusion in CXI
Your Environment
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 inspecting the get_lastRun bash script and the daq.run_number() entry point used from hutch Python. Reproduce the comparison on the primary and secondary DAQ machines, then trace which DAQ each invocation queries. Done means the secondary DAQ returns its own run number rather than the primary DAQ's value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100