Implementation of the fully hadronic modes using single-muon triggered data

[amlyon]

The main modifications to the code are:

• Adaptation of the framework to be able to run on the single-muon B-parking data set. This includes

  • TrackMerger modified to be able to perform both the dimuon and single-muon trigger cleaning.
  • Events filtered according to the presence of either at least one or at least two trigger muons.

• Implementation of the BTo4TrkBuilder. This builder allows for the reconstruction of B->V(trktrk)V(trktrk) decays. While originally designed to reconstruct Bs->phi(KK)phi(KK) decays, it can be used to reconstruct any decays with the same final state.

• Implementation of the BsToPhiPhiTo4K config file.

• Other modifications to the code:

  • TrkTrk candidates are now sorted in pt in the DiTrackBuilder.
  • The strategy for the loop on the track mass in the DiTrackBuilder was optimised: in case the two tracks have the same mass (e.g. phi->KK decay), does not loop twice on tracks anymore.

The implementation of the Bs->phi(KK)phi(KK) channel was validated against the implementation in the original and independent framework (CPVNano). The validation plots can be found here.

It was thoroughly checked that the modifications to the code do not impact the reconstruction of the decays in the dimuon channel. The validation plots for data can be found here and for mc here.

[amlyon]

Hi @gkaratha,

Here is the PR that imports to the modifications to the code such that it can reconstruct fully-hadronic modes in the single-muon B-parking data sets.

As we discussed, I let you decide when you think it is a good moment to merge this PR and run the code centrally.

Let me know if you have any questions!

[amlyon]

Note: if the code is to be run centrally, the name of the relevant HLT lines will have to be added here.

[gkaratha]

Thanks a lot @amlyon I will have a look. But if you have the code running then it should be ok