Ticket #1617 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

Switch TofEvents to use an absolute time instead of frame index

Reported by: Janik Zikovsky Owned by: Janik Zikovsky
Priority: major Milestone: Iteration 25
Component: Mantid Keywords:
Cc: pf9@… Blocked By:
Blocking: Tester: Michael Reuter

Description

Each event currently has a pulse id (aka frame index) and a vector in EventWorkspace holds the corresponding real-world time.

Convert the frame_index to a boost::int64_t ticks representing the number of ticks (1 nanosecond if boost supports that) since a specified epoch. I'll use the GPS epoch of Jan 1, 1990.

This gives 1 ns resolution up to +- 292 years around 1990. Should be enough.

Change History

comment:1 Changed 10 years ago by Janik Zikovsky

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Janik Zikovsky

(In [6143]) Refs #1617: Using the absolute pulse time in events instead of a frame index value that needs to be looked up. This also refs #1513, addressing issues of merging disparate runs.

comment:3 Changed 10 years ago by Janik Zikovsky

  • Status changed from accepted to verify
  • Resolution set to fixed
  • Component set to Mantid

comment:4 Changed 10 years ago by Michael Reuter

  • Status changed from verify to verifying
  • Tester set to Michael Reuter

comment:5 Changed 10 years ago by Michael Reuter

  • Status changed from verifying to closed

This looks like is has been done correctly.

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​2464

Note: See TracTickets for help on using tickets.