Add a way to set events/duration/etc. for the next scan point without a configure transition
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.configure(events=40), etc. when the daq is already configured should queue up that number for the nextdaq.trigger()without going through a configure transition.- same for duration
Current Behavior
- Requires a configure transition
Possible Solution
- Modify behavior of
configuremethod based on whether or not we're configured already and which arguments are called.
Context
- Required for various slow cam scans
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 reading the configure and trigger entry points and how configured state is tracked. Verify how events and duration are currently handled during a configure transition. Done means calls made while configured queue the requested values for the next daq.trigger() without requiring another configure transition, for both events and duration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100