Ticket #2750 (closed: fixed)
Algorithm to shift wall-clock time in events
| Reported by: | Peter Peterson | Owned by: | Janik Zikovsky |
|---|---|---|---|
| Priority: | minor | Milestone: | Iteration 28 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Michael Whitty |
Description
In anticipation of an upcoming pulsed magnet experiment, create a new algorithm that can add a constant to all wall-clock times in a workspace.
Change History
comment:2 Changed 10 years ago by Janik Zikovsky
- Status changed from accepted to verify
- Resolution set to fixed
comment:4 Changed 9 years ago by Michael Whitty
- Status changed from verify to verifying
- Tester set to Michael Whitty
comment:5 Changed 9 years ago by Michael Whitty
- Status changed from verifying to reopened
- Resolution fixed deleted
Load("/MANTID/Test/AutoTestData/CNCS_7860_event.nxs", "CNCS_7860_event")
ChangePulsetime("CNCS_7860_event", "CNCS_7860_event-shift", 100.0)
Rebin("CNCS_7860_event", "CNCS_7860_event", "4.7e4,10,4.9e4")
Rebin("CNCS_7860_event-shift", "CNCS_7860_event-shift", "4.7e4,10,4.9e4")
plotSpectrum(["CNCS_7860_event", "CNCS_7860_event-shift"], 2)
From what I can see, this algorithm doesn't seem to change the events. I would have expected the above script to remove the peak from the "shifted" workspace, but they still match up exactly when plotting it.
comment:6 Changed 9 years ago by Janik Zikovsky
The algorithm shifts the pulse time (wall-clock) of the event, not its time of flight. There are no direct ways to view events pulse time in Mantid; but FilterByTime could be used to show it indirectly.
comment:8 Changed 9 years ago by Janik Zikovsky
- Status changed from accepted to verify
- Resolution set to fixed
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 3597
Note: See
TracTickets for help on using
tickets.
