Today at the beamline, we discovered that diag6_flyer1 was generating events with an event.time that corresponded to when the event documents were composed -- after the scan, during the collect() phase -- not when their respective data points were generated.
We worked around this by accessing event.timestamps['diag6_flyer1'] instead of event.time. This PR makes event.time the same value as event.timestamps['diag6_flyer1']. Now get_table and other tools that use event.time will be usable on this data.
Today at the beamline, we discovered that
diag6_flyer1
was generating events with anevent.time
that corresponded to when the event documents were composed -- after the scan, during thecollect()
phase -- not when their respective data points were generated.We worked around this by accessing
event.timestamps['diag6_flyer1']
instead ofevent.time
. This PR makesevent.time
the same value asevent.timestamps['diag6_flyer1']
. Nowget_table
and other tools that useevent.time
will be usable on this data.