Include non-zero transition-time from open<->closed in `tof.chopper_cascade`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This is due to a non-zero guide side. See https://pubs.aip.org/aip/rsi/article/85/11/115103/356359/Choppers-to-optimise-the-repetition-rate (https://backend.orbit.dtu.dk/ws/portalfiles/portal/102784335/1.4900958.pdf) Fig. 3 and, e.g., Eq. (6) and (7).
In practice we might also need an option to define a cutoff, e.g., to ignore the tails below a threshold.
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 at the tof.chopper_cascade entry point and read the linked paper, especially Fig. 3 and Eqs. (6) and (7), to understand the non-zero guide-side transition time. Clarify how open-to-closed and closed-to-open tails should be represented and whether a cutoff option is required. Done means the cascade diagrams reflect the agreed transition behavior and any cutoff is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100