Note on chopper status recorded in NeXus files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
This may be relevant when performing frame-unwrapping or other chopper-related processing using ScippNeutron:
If the chopper is out of phase from the setpoint, then the device will send an alarm to the EPICS IOC, which in turn will report to NICOS, to inform the user that something is not working as expected
[10:40 AM] Nicklas Holmberg
The exact limits of "how much out of phase is tolerated" before an alarm is set, you will have to ask
@markusolsson
about
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
No file, test, or entry point is identified in the issue. First clarify where this chopper-status note belongs in the ScippNeutron documentation and confirm the tolerated out-of-phase limits with the referenced contact; done means the relevant documentation records the alarm behavior and confirmed limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100