Testing mat end calibration in hlt1

(Very rough first attempt to test including mat end calibration in HLT1, not yet tested)

Apply the same mat end calibration as HLT2, tested in real data (2024, run 297083).

To dos:

• Fix the issue with loading/accessing the mat end contraction parameter vector
• Dump geometry
• Upload dumped geometry somewhere to test in the pipeline
• Test throughput
• Verify output values are as expected

Check with Data:

Direct comparison

Residual Check in Data

FYI: @nibreer

assigned to @isanders

added 1 commit

• 4a52b6a4 - testing mat end calibration in hlt1

Compare with previous version

changed the description

added RTA label

changed the description

Great to see this being tested in HLT1 @isanders. What is the plan for validation on data? Checking signal yields?

added RTA WP4 label

added 1 commit

• cf689900 - testing mat end calibration in hlt1

Compare with previous version

Tagging @msaur to keep an eye on this as maintainer and see how to eventually prioritise things for the data taking after the TS

changed milestone to %RTA/2024.06.03-JuneTS

marked the checklist item Fix the issue with loading/accessing the mat end contraction parameter vector as completed

added backport RTA/2024.06.03 label

The contraction factors are nearly 3 MB of additional data. That amount can only be read from global memory, which is quite likely to hurt performance. If instead of a per-channel correction a few parameters could be stored per mat, that would reduce the amount of memory needed by a factor of a few hundred.

@isanders Do you have a time to finish this?

added 1 commit

• cd665243 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

changed milestone to %RTA/2024.08.12-AugMD

added 37 commits

• cd665243...d07a4be6 - 36 commits from branch 2024-patches
• 2073c610 - testing mat end calibration in hlt1

Compare with previous version

added 1 commit

• f7a82ac2 - testing mat end calibration in hlt1

Compare with previous version