ClusteringSpatial: assignment of trigger timestamp assumes events built around TLU
[ClusteringSpatial]
type="MIMOSA26"
use_trigger_timestamp=true
Currently, when the option use_trigger_timestamp
is used, the timestamp of the first trigger in the clipboard event is assigned to each cluster of the specified device (in our case mimosa26).
This is correctly handled iff clipboard events are built around TLU (i.e. one mimosa frame per clipboard event). If there are two mimosa frames within a clipboard event, the data from the second frame is assigned the timestamp of the trigger of the first frame.
For the trigger timestamps to be correctly assigned to the different mimosa frames, some information about which trigger IDs correspond to which pixels needs to be retained from the EventLoaderEUDAQ2
. We should think about the best way to do this.