Ticket #3377 (closed: fixed)
Add a function to shift a log time by some number of proton pulses
Reported by: | Russell Taylor | Owned by: | Peter Peterson |
---|---|---|---|
Priority: | major | Milestone: | Iteration 30 |
Component: | Mantid | Keywords: | |
Cc: | granrothge@… | Blocked By: | |
Blocking: | Tester: | Michael Reuter |
Description
From Garrett:
I need a function that changes a log time by a number of n proton pulses. This is not equivalent to shift by an amount of time as the time between proton pulses is not constant as the source frequency varies.
Attachments
Change History
comment:1 Changed 9 years ago by Russell Taylor
- Status changed from new to assigned
- Owner set to Peter Peterson
- Cc granrothge@… added
comment:5 Changed 9 years ago by Peter Peterson
- Status changed from accepted to verify
- Resolution set to fixed
As far as I know the last commit fixed it.
comment:6 Changed 9 years ago by Vickie Lynch
- Status changed from verify to verifying
- Tester set to Vickie Lynch
comment:7 Changed 9 years ago by Vickie Lynch
When I execute ShiftLogTime, the resulting log starts at the same time, but is shorted by 7813 indices. Maybe I did something wrong since the test works. See attached screenshot.
comment:8 Changed 9 years ago by Vickie Lynch
- Status changed from verifying to verify
- Tester Vickie Lynch deleted
comment:9 Changed 9 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
comment:10 Changed 9 years ago by Michael Reuter
- Status changed from verifying to closed
I discussed this with Pete and this is the exact behavior expected from the algorithm.
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 4224
Note: See
TracTickets for help on using
tickets.
For info, the script that Garrett is currently using to diagnose this. Apparently, Jim also has some code that does what's required.