Pad placement #3493

mitrankova · 2025-03-24T17:40:12Z

Types of changes

Bug fix (non-breaking change which fixes an issue)
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)
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, ...)

If there are no errors, before merging this PR TPC_FEE_CHANNEL_MAP should be updated with /sphenix/user/mitrankova/PadPlane_Readout/map/TPCPadPlaneCDBTTree.root

TPC QA plots don’t look correct as TPC_FEE_CHANNEL_MAP (that is used in simulation/g4simulation/g4tpc/PHG4TpcDetector.cc and offline/packages/tpc/TpcCombinedRawDataUnpacker.cc) should be updated with /sphenix/user/mitrankova/PadPlane_Readout/map/TPCPadPlaneCDBTTree.root
 QA plots with the correct map can be found /sphenix/user/mitrankova/sim_qa_checks/macros/detectors/sPHENIX
_CorrectMap.root - plots with the changes from this PR, with locally updated path to the correct TPC_FEE_CHANNEL_MAP(std::string calibdir = "/sphenix/user/mitrankova/PadPlane_Readout/map/TPCPadPlaneCDBTTree.root";) _def.root - plots with current build of core software *_WrongMap.root - plots with the changes from this PR, but with TPC_FEE_CHANNEL_MAP that is currently in CDB

TODOs (if applicable)

If there are no errors, before merging this PR TPC_FEE_CHANNEL_MAP should be updated with /sphenix/user/mitrankova/PadPlane_Readout/map/TPCPadPlaneCDBTTree.root

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

sphenix-jenkins-ci · 2025-03-25T02:16:09Z

Build & test report

Report for commit 79ce572560c34061528a354ea9bdc2b3b88074b4:

builds and tests overall are FAILURE.
Build with configuration of alma9.2-gcc-14.2.0 / clang is SUCCESS, 📊clang report (full)/(new), build log
Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
Build with configuration of alma9.2-gcc-14.2.0 / scan is FAILURE, 📊scan-build report (full)/(new), build log
Build with configuration of gcc-12.1.0 / new is SUCCESS, 📊Compiler report (full)/(new), build log
- Generating DST and readback: build is SUCCESS
- system gcc-12.1.0, build new: run the default sPHENIX macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the default TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the overlap check for sPHENIX macro: build is SUCCESS, output
clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

Automatically generated by sPHENIX Jenkins continuous integration

sphenix-jenkins-ci · 2025-03-25T05:40:40Z

Build & test report

Report for commit a31efaeddc6c0746d9d331f2948fb8ec821d73ac:

builds and tests overall are FAILURE.
Build with configuration of alma9.2-gcc-14.2.0 / clang is SUCCESS, 📊clang report (full)/(new), build log
Build with configuration of alma9.2-gcc-14.2.0 / new is FAILURE, 📊Compiler report (full)/(new), build log
- Generating DST and readback: build is SUCCESS
- Calorimeter QA: build is SUCCESS, 📊 trends
  - 📊 QA-calorimeter for e- at p_T=4GeV : combined Chi2/nDoF = 14.182 / 72, and combined p-Value = 1
  - 📊 QA-calorimeter for pi+ at p_T=30GeV : combined Chi2/nDoF = 46.0581 / 72, and combined p-Value = 0.992606
  - 📊 QA-calorimetric-jet for e- at p_T=4GeV : combined Chi2/nDoF = 28.6655 / 42, and combined p-Value = 0.941883
  - 📊 QA-calorimetric-jet for pi+ at p_T=30GeV : combined Chi2/nDoF = 9.21446 / 42, and combined p-Value = 1
- Tracking QA with Distortions: build is SUCCESS, 📊 trends
  - 📊 QA-distortions
- Tracking QA at low occupancy: build is SUCCESS, 📊 trends
  - 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
  - 📊 QA-Micromegas : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
  - 📊 QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
  - 📊 QA-Tpc : combined Chi2/nDoF = 979.857 / 56, and combined p-Value = 7.04577e-169
  - 📊 QA-tracking : combined Chi2/nDoF = 2257.25 / 56, and combined p-Value = 0
  - 📊 QA-vertexing : combined Chi2/nDoF = 403.179 / 112, and combined p-Value = 1.69871e-34
- Tracking QA for Pythia D0-jet: build is SUCCESS, 📊 trends
  - 📊 QA-Intt : combined Chi2/nDoF = -0 / 72, and combined p-Value = 1
  - 📊 QA-Micromegas : combined Chi2/nDoF = -0 / 20, and combined p-Value = 1
  - 📊 QA-Mvtx : combined Chi2/nDoF = -0 / 54, and combined p-Value = 1
  - 📊 QA-Tpc : combined Chi2/nDoF = 809.482 / 56, and combined p-Value = 4.07261e-134
  - 📊 QA-tracking : combined Chi2/nDoF = 387.529 / 50, and combined p-Value = 1.01895e-53
  - 📊 QA-vertexing : combined Chi2/nDoF = 176.351 / 112, and combined p-Value = 0.000100517
- system alma9.2-gcc-14.2.0, build new: run the default sPHENIX macro: build is SUCCESS, output, trends 📊
- system alma9.2-gcc-14.2.0, build new: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends 📊
- system alma9.2-gcc-14.2.0, build new: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends 📊
- system alma9.2-gcc-14.2.0, build new: run the default TrackingProduction/Fun4All_PRDFReconstruction.C macro: build is FAILURE, output, trends 📊
- system alma9.2-gcc-14.2.0, build new: run the default TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C macro: build is SUCCESS, output, trends 📊
- system alma9.2-gcc-14.2.0, build new: Valgrind test of CaloProduction/Fun4All_Year2.C: build is SUCCESS, 📊valgrind report, trends 📊
- system alma9.2-gcc-14.2.0, build new: Valgrind test of StreamingProduction/Fun4All_Stream_Combiner.C: build is SUCCESS, 📊valgrind report, trends 📊
- system alma9.2-gcc-14.2.0, build new: Valgrind test of TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C: build is SUCCESS, 📊valgrind report, trends 📊
- system alma9.2-gcc-14.2.0, build new: run the overlap check for sPHENIX macro: build is SUCCESS, output
- system alma9.2-gcc-14.2.0, build new: Valgrind test: build is UNSTABLE, 📊valgrind report, trends 📊
Build with configuration of alma9.2-gcc-14.2.0 / scan is SUCCESS, 📊scan-build report (full)/(new), build log
Build with configuration of gcc-12.1.0 / new is SUCCESS, 📊Compiler report (full)/(new), build log
- Generating DST and readback: build is SUCCESS
- system gcc-12.1.0, build new: run the default sPHENIX macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the default TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C macro: build is SUCCESS, output, trends 📊
- system gcc-12.1.0, build new: run the overlap check for sPHENIX macro: build is SUCCESS, output
clang-tidy is SUCCESS, 📊clang-tidy report (full)/(new)
cpp-check is SUCCESS, 📊cppcheck report (full)/(new)

Automatically generated by sPHENIX Jenkins continuous integration

pinkenburg · 2025-03-25T10:57:10Z

The valgrind error is just a suppression issue (the line with the known suppressed leak has changed, will update the suppression. The tracking production crashes after printing
Failed to find silicon surface for hitsetkey 66576 tmpkey 66576
which I have seen in other PRs - so likely unrelated to this one