Integration test for Flavour Tagging variables
This integration test aims to determine if the flavour tagging variables are available in the ntuples.
The input is Upgrade Bd->DPi simulation in xdigi
format (used in B2DX early measurements).
Afterwards, a Moore job runs HLT1 and saves the result as a dst
file. Next, Moore is used to apply an exclusive flavour tagging HLT2 line, BdToDmPi_DmToPimPimKp
, saving all long and upstream particles as extra_outputs
and saving it to a dst
file.
Finally, Davinci is run to produce a root
file from this and check if the resulting nTuple contains flavour tagging variables.
Each step of the chain is run using the Utilitites/logscript.sh
script that saves the corresponding stdout and stderr.
The stderr is then used for step validation by means of the Utilities/validator.sh
script ensuring no error is
dumped in the stderr.
For the final ntuple, an additional validation is performed using the Tupling_FT/validator_tuple_FT.py
script, checking that
the DecayTree is not empty and contains all the expected flavour tagging branches.
Only the SSPion
variables are available to check for now, but this will be expanded later.1
Another feature to add later is checking whether the values of the flavour tagging variables remain the same.
Will be used in:
- Repurpose tagging_particles line option (@sesen Moore!2300 (merged))
This MR is dependent on option files in Davinci and Moore:
-
Add options file for LHCbIntegrationTest (@jobutter DaVinci!948 (merged)) -
Options for flavour tagging integration test (@jobutter Moore!2643 (merged))
Tested with x86_64_v2-centos7-gcc12+detdesc-opt
from the stack
folder using:
make fast/LHCbIntegrationTests/test ARGS="-R 31,37"