Add caloParams v0_4_2 and v0_4_3

[mitaylor]

PR description:
Add two L1T calo configs: v0_4_2 is currently used in the run, and lowers the jet seed threshold from 4 GeV to 2.5 GeV, and v0_4_3 we plan to switch to now, and has updated centrality thresholds for CENT6 and CENT7 for the UCC triggers.

PR validation:
These files represent L1 configuration to be stored centrally, and are not involved in any central workflows.

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport. Will need to backport to CMSSW_13_2_X.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43046/37239

• This PR adds an extra 20KB to repository

[cmsbuild]

A new Pull Request was created by @mitaylor (Molly Taylor) for master.

It involves the following packages:

• L1Trigger/Configuration (l1)
• L1Trigger/L1TCalorimeter (l1)

@aloeliger, @cmsbuild, @epalencia can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @missirol this is something you requested to watch as well.
@sextonkennedy, @antoniovilela, @rappoccio you are the release manager for this.

cms-bot commands are listed here

[aloeliger]

Hi @mitaylor, we've been asked to stop putting these into central CMSSW (even though I was the person who led the charge on no longer putting them in the L1 fork of CMSSW). Would you be willing to wait just a bit for me to create a repository under our management that these could be inserted into instead?

[mitaylor]

Hi Andrew,

Sure, no problem -- just let me know what to do when it's ready. Also, wouldn't we still need to commit the change to the customiseSettings somewhere? How would that be handled?

Molly

[smuzaffar]

Milestone for this pull request has been moved to CMSSW_14_0_X.Please open a backport if it should also go in to CMSSW_13_3_X.

[mitaylor]

@rohitcms @Cristian-Baldenegro

[aloeliger]

At this point the calo params cleaning project has hit such a stall I don't fell right in leaving this PR hanging. I will sign this and add it into the cleanup project to be continued as we go.

[aloeliger]

+l1

[aloeliger]

Please test

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0d8a02/36911/summary.html
COMMIT: 663e50f
CMSSW: CMSSW_14_0_X_2024-01-18-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43046/36911/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially removed 101 lines from the logs
• Reco comparison results: 14 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3247526
• DQMHistoTests: Total failures: 9
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3247495
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 200 log files, 161 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[rappoccio]

+1