Runs sometimes have hugely wrong durations
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 9
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 1
Description
Expected Behavior
daq.begin(duration=300) should take approx 5 minutes
Current Behavior
daq.begin(duration=300) sometimes only lasts 3mins 15sec
Tinfoil hat theory: this only happens when record=True, explaining why I can't recreate it.
Possible Solutions
Considering making the python layer start/stop the run timer instead of asking the daq to do it...
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 daq.begin(duration=300) and comparing runs with record=True and record=False, measuring the actual elapsed time. Trace the timing behavior from that entry point; done means the run consistently lasts approximately five minutes or the cause of the shortened duration is identified and covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100