Commit b0cec48
Let the MCH digitiser accept a timeframe without collisions
This fixes a segmentation fault in MCHDPLDigitizerTask when the collision
context of a timeframe is empty.
- The noise-only signal range was taken from eventRecords.front() and
eventRecords.back(), which is undefined behaviour on an empty vector.
- A timeframe holds no collision whenever the interaction rate is low.
- The range now comes from HBFUtils in that case, so the noise covers the
timeframe that is actually being digitised.
https://its.cern.ch/jira/browse/O2-7132
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 98a5696 commit b0cec48
1 file changed
Lines changed: 15 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
15 | 15 | | |
16 | 16 | | |
17 | 17 | | |
| 18 | + | |
18 | 19 | | |
19 | 20 | | |
20 | 21 | | |
| |||
102 | 103 | | |
103 | 104 | | |
104 | 105 | | |
105 | | - | |
106 | | - | |
107 | | - | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
| 119 | + | |
108 | 120 | | |
109 | 121 | | |
110 | 122 | | |
| |||
0 commit comments