Integrate TRD extra data support in AOD production workflow
This pull request adds TRD extra data support to the AOD production workflow, including calibrated tracklet handling, local gain and noise corrections, and a new TRDsExtra SOA table in AnalysisDataModel.h. The changes introduce an optional runtime flag (--enable-TRD-extra) to control TRD output and extend existing workflow templates and data structures to incorporate TRD-specific quantities for improved reconstruction and analysis.
REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-
+async-label <label1>, <label2>, !<label3> ...
This will add <label1> and <label2> and removes <label3>.
The following labels are available async-2023-pbpb-apass4 async-2023-pp-apass4 async-2024-pp-apass1 async-2022-pp-apass7 async-2024-pp-cpass0 async-2024-PbPb-apass1 async-2024-ppRef-apass1 async-2024-PbPb-apass2 async-2023-PbPb-apass5
Error while checking build/O2/fullCI_slc9 for c1dce5b90fc8ac364f287ee0f9ea0c11feaf263e at 2025-12-24 08:14:
## sw/BUILD/O2-sim-challenge-test-latest/log
./sim-challenge.logDetected critical problem in logfile trdMatch.log
./sim-challenge.logtrdMatch.log:[14959:internal-dpl-ccdb-backend]: [08:14:12][ERROR] Exception while running: Fatal error. Rethrowing.
./sim-challenge.logtrdMatch.log-[14959:internal-dpl-ccdb-backend]: [08:14:12][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-trd-global-tracking, device shutting down. Reason: Fatal error
./sim-challenge.log[14959:internal-dpl-ccdb-backend]: [08:14:12][ERROR] CCDBDownloader CURL transfer error - Timeout was reached
./sim-challenge.log[14959:internal-dpl-ccdb-backend]: [08:14:12][ERROR] CcdbDownloader finished transfer http://alice-ccdb.cern.ch/GLO/Config/GeometryAligned for 1546300800000 (agent_id: o2-trd-global-t/o2-trd-global-tracking@14959 target/Linux_x86_64 init/1766560442703 id/[email protected] session/tuKwjHS3 ) with http code: 0
./sim-challenge.log[14959:internal-dpl-ccdb-backend]: [08:14:12][ERROR] File GLO/Config/GeometryAligned could not be retrieved. No more hosts to try.
./sim-challenge.log[14959:internal-dpl-ccdb-backend]: [08:14:12][FATAL] Unable to find CCDB object GLO/Config/GeometryAligned/1546300800000
./sim-challenge.log[14959:internal-dpl-ccdb-backend]: [08:14:12][ERROR] Exception while running: Fatal error. Rethrowing.
./sim-challenge.log[14959:internal-dpl-ccdb-backend]: [08:14:12][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-trd-global-tracking, device shutting down. Reason: Fatal error
./sim-challenge.log[ERROR] Workflow crashed - PID 14959 (internal-dpl-ccdb-backend) did not exit correctly however it's not clear why. Exit code forced to 128.
./sim-challenge.log[ERROR] - Device internal-dpl-ccdb-backend: pid 14959 (exit 128)
./sim-challenge.log[INFO] - First error: [08:14:12][FATAL] Unable to find CCDB object GLO/Config/GeometryAligned/1546300800000
./sim-challenge.log[ERROR] SEVERE: Device internal-dpl-ccdb-backend (14959) had at least one message above severity 7: Unable to find CCDB object GLO/Config/GeometryAligned/1546300800000
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/45}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/46}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/47}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/48}
./digi.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/49}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/45}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/46}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/47}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/48}
./digi.log[5010:internal-dpl-clock]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/49}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/45}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/46}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/47}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/48}
./digi.log[5039:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/49}
./digi.log[5126:Digitizations]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./digi.log[5126:Digitizations]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./digi.log[5126:Digitizations]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./digi.log[5126:Digitizations]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./digi.log[5126:Digitizations]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
[0 more errors; see full log]
Full log here.
As previously commented, this should be discussed with the analysis work-package (WP4).
Sure, I will present a detailed motivation and computation cost of these additions in the upcoming meeting.
This PR did not have any update in the last 30 days. Is it still needed? Unless further action in will be closed in 5 days.