Add Module to Build Trigger Clusters

[ruse-traveler]

This PR introduces a module a construct Trigger Clusters, various jet trigger patches saved to RawCluster objects for easier downstream analysis. For example, this will enable a user to easily look up the towers which went into a patch that fired a given trigger.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work for users)
• [ ] Requiring change in macros repository (Please provide links to the macros pull request in the last section)
• [x] I am a member of GitHub organization of sPHENIX Collaboration, EIC, or ECCE (contact Chris Pinkenburg to join)

What kind of change does this PR introduce? (Bug fix, feature, ...)

This PR adds a new feature.

TODOs (if applicable)

• [ ] Finish process_event
  • [ ] Loop over each jet patch
  • [ ] For each patch which fired trigger, construct a RawCluster.
• [ ] Add piping for saving clusters to node tree
• [ ] Finish piping for saving clusters to TTree

Links to other PRs in macros and calibration repositories (if applicable)

[sphenix-jenkins-ci[bot]]

Build & test report

Report for commit aafc65a71af97cf201dd42ed56e25bd0be606cbf:

• builds and tests overall are FAILURE.
• Build with configuration of gcc-12.1.0 / clang is FAILURE, :bar_chart:clang report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is FAILURE, :bar_chart:Compiler report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / scan is FAILURE, :bar_chart:scan-build report (full)/(new), build log
• clang-tidy is UNSTABLE, :bar_chart:clang-tidy report (full)/(new)
• cpp-check is SUCCESS, :bar_chart:cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration            

[sphenix-jenkins-ci[bot]]

Build & test report

Report for commit b16970bda518b07b4977f8a15f08ec4d99eb5109:

• builds and tests overall are SUCCESS.
• Build with configuration of gcc-12.1.0 / clang is SUCCESS, :bar_chart:clang report (full)/(new), build log
• Build with configuration of gcc-12.1.0 / new is SUCCESS, :bar_chart:Compiler report (full)/(new), build log
  • Generating DST and readback: build is SUCCESS
  • Calorimeter QA: build is SUCCESS, :bar_chart: trends
    • :bar_chart: QA-calorimeter for e- at p_T=4GeV : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • :bar_chart: QA-calorimeter for pi+ at p_T=30GeV : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • :bar_chart: QA-calorimetric-jet for e- at p_T=4GeV : combined Chi2/nDoF = -0 / 42, and combined p-Value = 1
    • :bar_chart: QA-calorimetric-jet for pi+ at p_T=30GeV : combined Chi2/nDoF = -0 / 42, and combined p-Value = 1
  • Tracking QA with Distortions: build is SUCCESS, :bar_chart: trends
    • :bar_chart: QA-distortions
  • Tracking QA at low occupancy: build is SUCCESS, :bar_chart: trends
    • :bar_chart: QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • :bar_chart: QA-Micromegas : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
    • :bar_chart: QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
    • :bar_chart: QA-Tpc : combined Chi2/nDoF = -0 / 56, and combined p-Value = 1
    • :bar_chart: QA-tracking : combined Chi2/nDoF = -0 / 56, and combined p-Value = 1
    • :bar_chart: QA-vertexing : combined Chi2/nDoF = 30 / 112, and combined p-Value = 1
  • Tracking QA for Pythia D0-jet: build is SUCCESS, :bar_chart: trends
    • :bar_chart: QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
    • :bar_chart: QA-Micromegas : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
    • :bar_chart: QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
    • :bar_chart: QA-Tpc : combined Chi2/nDoF = -0 / 56, and combined p-Value = 1
    • :bar_chart: QA-tracking : combined Chi2/nDoF = 0.00147402 / 50, and combined p-Value = 1
    • :bar_chart: QA-vertexing : combined Chi2/nDoF = 30 / 112, and combined p-Value = 1
  • system gcc-12.1.0, build new: run the default sPHENIX macro: build is SUCCESS, output, trends :bar_chart:
  • system gcc-12.1.0, build new: run the default CaloProduction/Fun4All_Year1.C macro: build is SUCCESS, output, trends :bar_chart:
  • system gcc-12.1.0, build new: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends :bar_chart:
  • system gcc-12.1.0, build new: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends :bar_chart:
  • system gcc-12.1.0, build new: run the default TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C macro: build is SUCCESS, output, trends :bar_chart:
  • system gcc-12.1.0, build new: Valgrind test of CaloProduction/Fun4All_Year1.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:
  • system gcc-12.1.0, build new: Valgrind test of CaloProduction/Fun4All_Year2.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:
  • system gcc-12.1.0, build new: Valgrind test of StreamingProduction/Fun4All_Stream_Combiner.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:
  • system gcc-12.1.0, build new: Valgrind test of TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:
  • system gcc-12.1.0, build new: run the overlap check for sPHENIX macro: build is SUCCESS, output
  • system gcc-12.1.0, build new: Valgrind test: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:
• Build with configuration of gcc-12.1.0 / scan is SUCCESS, :bar_chart:scan-build report (full)/(new), build log
• clang-tidy is SUCCESS, :bar_chart:clang-tidy report (full)/(new)
• cpp-check is SUCCESS, :bar_chart:cppcheck report (full)/(new)

---

Automatically generated by sPHENIX Jenkins continuous integration            

[ruse-traveler]

I'm going to go ahead and close this: it's been a while, and I think I might to need to do some refactoring to account for upstream software changes.