Add new spruce test file

Add new input files for Sprucing BW tests.

The files are produced by running all Hlt2 Full stream lines as of July 13rd 2023, including the following in hlt2_pp_commissioning

from Hlt2Conf.lines.topological_b import all_lines as topological_b_lines
from Hlt2Conf.lines.inclusive_detached_dilepton import all_lines as inclusive_detached_dilepton_lines
from Hlt2Conf.lines.charmonium_to_dimuon_detached import all_lines as charmonium_to_dimuon_detached_lines
from Hlt2Conf.lines.qee import hlt2_full_lines as qee_full_lines

def make_lines():
    lines = []
    lines += [builder() for builder in topological_b_lines.values()]
    lines += [builder() for builder in inclusive_detached_dilepton_lines.values()]
    lines += [builder() for builder in charmonium_to_dimuon_detached_lines.values()]
    lines += [builder() for builder in qee_full_lines.values()]
    return lines

The input file of Hlt2 stage is upgrade_minbias_hlt1_filtered in TestFileDB, its input rate is assumed to be 1 MHz.

By inspecting the output logs, the overall efficiency is around 17.5%, so the input rate of these Spurcing files is assumed to be 175 kHz.

Needed by lhcb/Moore!2510 (merged).

assigned to @nskidmor and @shunan

mentioned in merge request lhcb/Moore!2510 (merged)

changed the description

mentioned in issue lhcb/Moore#612 (closed)

• [2023-07-14 07:52] Validation started with lhcb-master-mr#8544

Hi, sorry to jump in late, for radiative sprucing lines we also rely on the lines in https://gitlab.cern.ch/lhcb/Moore/-/blob/master/Hlt/Hlt2Conf/python/Hlt2Conf/lines/rd/rad_incl.py
It doesn't need to be in this iteration but it would be nice to have them as well when possible.
Actually after lhcb/Moore!2325 (merged) we will have rd_full_lines (including rad ones) defined same as qee, we can switch to that after it gets in

added 1 commit

• 7f1abbf3 - use new input for sprucing throughput test

Compare with previous version

added 1 commit

• e29bd017 - update input rate of throughput test

Compare with previous version

unassigned @shunan

resolved all threads

mentioned in commit 9cdd5817

merged

Hello @shunan, @nskidmor, may I suggest that in the future you email WP1 (also MM if you fancy) for such changes that have a clear impact on rates/bandwidths analysts see, so that the communication of relevant matters is more efficient? I cannot think of anyone going to complain that we tell them basically "Do not be surprised by changes in rates/... because we are now using a more realistic test/'denominator'".

I reckon these small mattters do matter as QoL improvements :).

Thanks a lot.