Changes to L0 PID lines

Changes to the L0->ppi PID calibration HLT2 lines:

• Introduced a fourth line which covers the 1.5-3 GeV proton pT region
• Changed the naming scheme and prescales
  • Low pT -> 0-1.5 (prescale reduced to 0.002)
  • Mid pT -> 1.5-3 (prescale set to 0.01)
  • High pT -> 3-6 (prescale reset)
  • Very High pT -> 6+
• Made the above changes for DD and LL tracks
• Enabled DD lines

added PID hlt2 labels

requested review from @dcervenk

assigned to @imackay

added RTA label

added 1 commit

• b3899041 - Enable DD L0 lines

Compare with previous version

changed title from Draft: Changes to L0 PID line to Draft: Changes to L0 PID lines

changed the description

added 7 commits

• b3899041...eb9f2d9b - 4 commits from branch master
• e959de93 - Add new L0 line and change prescales
• dbe5ace5 - Fixed formatting
• 4e7a9665 - Enable DD L0 lines

Compare with previous version

added 9 commits

• 4e7a9665...da1ed907 - 6 commits from branch master
• c7822ad3 - Add new L0 line and change prescales
• 771e0e8c - Fixed formatting
• 9fbdb803 - Enable DD L0 lines

Compare with previous version

marked this merge request as ready

requested review from @axu

mentioned in issue #574 (closed)

added 11 commits

• 9fbdb803...05ff9ddd - 8 commits from branch master
• 85e5bf02 - Add new L0 line and change prescales
• be3880f1 - Fixed formatting
• 57949b2e - Enable DD L0 lines

Compare with previous version

added 1 commit

• 8c3503a0 - Add upper pt limits to stop double counting; Change pt filter for downstream lines

Compare with previous version

added 1 commit

• 9ef69c10 - Fixed formatting

Compare with previous version

/ci-test

added ci-test-triggered label

• [2023-05-19 08:12] Validation started with lhcb-master-mr#7913
• [2023-06-12 16:12] Validation started with lhcb-master-mr#8222

added hlt2-throughput-increased label

Re:

• Low pT -> 0-1.5 (prescale reduced to 0.002)
• Mid pT -> 1.5-3 (prescale set to 0.01)
• High pT -> 3-6 (prescale reset)
• Very High pT -> 6+

In general, IMO, it is better to 'nest' trigger lines in this type of scenario, i.e. define them as Low: pT>0, Mid: pT>1.5, High: pT>3 and Very High: pT>6. Now, that implies that the newly created overlap(s) is (are) triggered by multiple lines, and if the prescales are independent (which they are by default), this results in higher rates -- but the underlying DeterministicPrescalers of these lines could be configured to use the same SeedName which then results in 'coherent' prescales, ie. the total rate for a set of lines with nested lower bounds will be the same as for a set of lines with non-overlapping lower and higher bounds -- and the nested lower bounds are much easier to use downstream, as one does not have to know the exact (relative) prescales of each subsequent line to properly normalize the spectrum.

Note that this does require a bit of work, as right now the SeedName is always computed from the line name, and one would have to add a bit of code which checks if it is explicitly given, and if so, use that, and only if not use the line name as seed.