New APE measurement workflow

[mteroerd]

PR description:

4ec9659 : Added new workflow for measuring APE using DAGMan and HTCondor.
To execute, run, e.g., "python3 apeMeasurement.py -c mc_example.yaml" (should use el8 for this dataset).

fddb4bd : Removing obsolete files that are not used. Mostly old plotting scripts in macros/.

e75e715 : Removing some references to obsolete files.

PR validation:

Ran the workflow with several different configurations. Also replicated a previous MC 2023 APE campaign (as configured in mc_example.yaml) in order to ensure the same results.

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, not sure if backports will be needed (probably not).

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45156/40500

• This PR adds an extra 36KB to repository

[cmsbuild]

A new Pull Request was created by @mteroerd for master.

It involves the following packages:

• Alignment/APEEstimation (alca)

@saumyaphor4252, @perrotta, @consuegs, @cmsbuild can you please review it and eventually sign? Thanks.
@mmusich, @missirol, @yuanchao, @rsreds, @adewit, @tocheng this is something you requested to watch as well.
@rappoccio, @sextonkennedy, @antoniovilela you are the release manager for this.

cms-bot commands are listed here

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45156/40524

• This PR adds an extra 36KB to repository

• There are other open Pull requests which might conflict with changes you have proposed:

  • File Alignment/APEEstimation/python/AlcaRecoSelection_cff.py modified in PR(s): [Dummy] Try creating big-enough cache to cause splitting #44368
  • File Alignment/APEEstimation/python/TriggerSelection_cff.py modified in PR(s): [Dummy] Try creating big-enough cache to cause splitting #44368
  • File Alignment/APEEstimation/test/cfgTemplate/apeEstimator_cfg.py modified in PR(s): [Dummy] Try creating big-enough cache to cause splitting #44368

[cmsbuild]

Pull request #45156 was updated. @saumyaphor4252, @cmsbuild, @perrotta, @consuegs can you please check and sign again.

[mmusich]

@cmsbuild, please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fc7613/39796/summary.html
COMMIT: 6afe75b
CMSSW: CMSSW_14_1_X_2024-06-07-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/45156/39796/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 2 lines to the logs
• Reco comparison results: 6 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3338974
• DQMHistoTests: Total failures: 6
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3338948
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 202 log files, 165 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[perrotta]

@mteroerd this PR adds new test configs: is any unit test foreseen with them?

[mteroerd]

@mteroerd this PR adds new test configs: is any unit test foreseen with them?

I think that these configs would not work in a unit test, as they'd require access to dasgoclient. I agree it makes sense to include a unit test for the new work flow, but since I am short on time to work on this much more and because my contract will end this month, this will probably be a task for my successor, along with the inclusion of a few more features that would make sense.

[perrotta]

+alca

• New test configs added, tested and validated under the responsibility of the Alignment/APE group

[cmsbuild]

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

[rappoccio]

+1