D2HH lines: add monitoring and update selections

This MR updates the

$D^0\rightarrow hh$

lines. The changes are:

• Add monitoring variables to be used during bandwidth division
• Add a selections on decay time
  $ct$
  of the
  $D^0$

Should me merged after !1225 (merged)

added RTA label

added 1 commit

• 6035e4a6 - Fixed formatting

Compare with previous version

added 1 commit

• a9d29107 - Fixed formatting

Compare with previous version

added 1 commit

• a10987d3 - Update CI references

Compare with previous version

added 6 commits

• a10987d3...8e7f97cc - 2 commits from branch master
• c8bb9421 - First commit for line update
• 8318e9f9 - Fixed formatting
• 41789584 - Fixed formatting
• 7d35ffcf - Update CI references

Compare with previous version

added 1 commit

• 2404f873 - Update CI references

Compare with previous version

changed the description

added 29 commits

• 2404f873...5660a587 - 23 commits from branch master
• f57b29d0 - First commit for line update
• a002f363 - Fixed formatting
• 3c3eb65d - Fixed formatting
• 207d913a - Update CI references
• 22b429ce - Update CI references
• 6058ff3d - Insert scaling between IP anc ct selections

Compare with previous version

added 1 commit

• 4deab452 - Fixed formatting

Compare with previous version

changed the description

added 1 commit

• 11bb9e22 - More monitoring comments

Compare with previous version

added 1 commit

• 28233f96 - Fixed formatting

Compare with previous version

Hi @tevans , I've implemented monitoring for bandwidth division. Do you think it works? Do you have any suggestion? Thanks.

added 1 commit

• 9854ed23 - Add monitoring_types everywhere and remove decision from monitoring

Compare with previous version

marked this merge request as ready

resolved all threads

mentioned in issue Moore#558 (closed)

mentioned in issue Moore#563 (closed)

added 49 commits

• 9854ed23...eaea0fdc - 40 commits from branch master
• 12469788 - First commit for line update
• d52a4661 - Fixed formatting
• 0a86fec9 - Fixed formatting
• ef861f30 - Update CI references
• 1b16279f - Insert scaling between IP anc ct selections
• 1e7e5a9c - Fixed formatting
• edf5089d - More monitoring comments
• 5ecf5eb8 - Fixed formatting
• e78146b6 - Add monitoring_types everywhere and remove decision from monitoring

Compare with previous version

added 1 commit

• ce5b5ae0 - Update CI references

Compare with previous version

What is the improvement in efficiency obtained by introducing the IP selection in addition to the IPchi2 in the FilterTracks stage? It would be good to know the trade-off between the gain in physics and the slight decrease in throughput.

added 1 commit

• f25b7688 - Higher pT and lower IP in FilterTracks

Compare with previous version

The proposal here is for commissioning stage, and it is intentionally loose. Further studies are ongoing, in particular in conjunction with the twin line on D0-KSHH decays (from @mamartin).

For the exclusive D0-HH line we could set a tighter cut at the pre-filter level with no significant consequences. Nico already demonstrated that we can afford values up to IP>90microns with Run-3 design luminosity. The threshold at 60 microns is for commissioning and it is driven by studies performed in the past assuming a pT threshold for all HLT1 reconstructed tracks of 500 MeV (see https://indico.cern.ch/event/1118175/ ).

While this pT threshold is ok for the D0-HH line, it might be too tight for the D0-KsHH, where both from Run 2 and 2022 data, we already know that low momentum tracks for this channel are of fundamental importance for efficiency. In conclusions, we believe that for commissioning stage the requirement in the FilterTracks —> “(pt>200MeV && IPCHI2>2) OR (pt>200MeV && IP>60microns)” would allow us performing all studies on both lines in preparation of high-lumi runs.

I expect that the pT threshold could chance when luminosity will increase and it will be placed somewhere, between 200 and 500 MeV. This will depends on many factors, not only from the two exclusive lines mentioned in this MR. The IPCHI2 (and consequently the IP) cut will be accordingly modified to stay in the allowed throughput limits.

Finally, I conclude by saying that these two exclusive lines do not have the primary goal of increasing the efficiency and the purity of the D0->hh and D0->KShh decay modes. For this we will exploit TrackMVA and TwoTrackMVA [this is especially true for the two-body line, while for the D0->KShh there might be some room to improve]. Here, the goal is to have a robust line, with no cuts on CHI2-like variables, and with a negligible correlation between D0 momentum and proper decay time, which is very dangerous for high-precision time-dependent measurements (DeltaY, yCP, bin-flip KsPiPi, D->Kpi WS/RS, lifetimes(?), …). We expect these lines to be almost completely overlapped with TrackMVA lines and not to disturb the data taking (I have also in mind the final output of the corresponding HLT2 lines). If that should be the case, we can just tight our requirements on pT and IP.

mentioned in issue Moore#574 (closed)

/ci-test

added ci-test-triggered label

• [2023-05-16 15:51] Validation started with lhcb-master-mr#7878
• [2023-05-19 08:13] Validation started with lhcb-master-mr#7914

added 1 commit

• 3c158113 - Test FilterTracks throughput

Compare with previous version

added 1 commit

• 5506f891 - Test FilterTracks throughput

Compare with previous version

added 1 commit

• b27580a3 - Test FilterTracks throughput

Compare with previous version

added 1 commit

• 640a66d9 - Test FilterTracks throughput

Compare with previous version

added 1 commit

• 24f35658 - Test FilterTracks throughput

Compare with previous version

added 49 commits

• 24f35658...7a81656a - 32 commits from branch master
• 33234521 - First commit for line update
• bbb097c9 - Fixed formatting
• 079a8434 - Fixed formatting
• 51a06980 - Update CI references
• 78ae4312 - Insert scaling between IP anc ct selections
• ea934859 - Fixed formatting
• fdf039e4 - More monitoring comments
• 0d32e5d5 - Fixed formatting
• f6860575 - Add monitoring_types everywhere and remove decision from monitoring
• 6cb04b85 - Update CI references
• 1cbe7321 - Higher pT and lower IP in FilterTracks
• 2f638971 - Test FilterTracks throughput
• 04185df3 - Test FilterTracks throughput
• ea537906 - Test FilterTracks throughput
• 684dcfb2 - Test FilterTracks throughput
• ac0ad8f0 - Test FilterTracks throughput
• a4a5154b - Test FilterTracks throughput

Compare with previous version

added hlt1-throughput-decreased label

added 1 commit

• 0550700c - Test FilterTracks throughput

Compare with previous version

added 1 commit

• 9da1e520 - Test FilterTracks throughput

Compare with previous version

removed hlt1-throughput-decreased label

added 1 commit

• cc7673b5 - Test FilterTracks throughput

Compare with previous version

added hlt1-throughput-decreased label

/ci-test

added 1 commit

• 9587405b - Testing throughput update

Compare with previous version

removed hlt1-throughput-decreased label

added hlt1-throughput-increased label

added 1 commit

• 8a8fc5f7 - Testing throughput

Compare with previous version

added 1 commit

• 1060b656 - Testing throughput

Compare with previous version

added hlt1-throughput-decreased label

added 31 commits

• 1060b656...3fbb19f4 - 8 commits from branch master
• 8afaa79c - First commit for line update
• e325d84e - Fixed formatting
• 4720fb2c - Fixed formatting
• 2dcbf128 - Update CI references
• 88b9d205 - Insert scaling between IP anc ct selections
• 7defcb35 - Fixed formatting
• a8f5bc29 - More monitoring comments
• c990bdad - Fixed formatting
• cbf06a8a - Add monitoring_types everywhere and remove decision from monitoring
• 84fdcd31 - Update CI references
• cfbf5240 - Higher pT and lower IP in FilterTracks
• 4eb80230 - Test FilterTracks throughput
• bb6b8439 - Test FilterTracks throughput
• 26d74bd1 - Test FilterTracks throughput
• 64c88b08 - Test FilterTracks throughput
• 5d503924 - Test FilterTracks throughput
• a1ef42db - Test FilterTracks throughput
• 6ce7c8d7 - Test FilterTracks throughput
• 818e8286 - Test FilterTracks throughput
• d19950f0 - Test FilterTracks throughput
• 7292ec22 - Testing throughput update
• 621985d8 - Testing throughput
• 26395a02 - Testing throughput

Compare with previous version

/ci-test

• [2023-05-22 16:11] Validation started with lhcb-master-mr#7971