mbluj

> > * This can suggest that covariance packing schema is a kind of global > > this is by design. Thanks @slava77 for explanation. It means that version of...

I would really make configurable a version of the track covariance packing in `DeepBoostedJetTagInfoProducer` module. It will make visible the fact that the covariance packing is used in the HLT...

> > +reconstruction Unless we decide to support running HLT + RECO in the same step, this is not an issue that will be addressed. > > Sorry, no, it...

> PackedCandidate interface does not support a switch between variants during runtime; there is a `call_once`. Yes, true. But, variant can be at least set consistently for all modules using...

Previously used `constexpr static const int` replaced by more compact `static constexpr int` with same meaning.

It compiles fine with non-DBG IB, explicitly checked with CMSSW_14_1_DBG_X_2024-05-09-2300 and el8_amd64_gcc12. What is difference between regular and DBG releases? The `L1Trigger/L1TMuonOverlapPhase2` package was recently added to CMSSW, could it...

Thank you @smuzaffar I confirm that usage of `constexpr` fixes issues within OMTF code, but I think I am not able to fix them in header from AMD. How to...

OK, so I prepare PR with CMSSW fixes. What concerns the external package I cannot comment, but at least from a quick look it is still recommended by Xylinx/AMD in...

> @mbluj It looks like in constructing the PR to CMSSW, some items were forgotten from #43687, in particular, a python configuration `L1Trigger/L1TMuonOverlapPhase2`. > > Could you please take a...

I have checked and actually it is this PR which introduces a call to `L1Trigger.L1TMuonOverlapPhase2` package (not yet existing in the official CMSSW) here: https://github.com/cms-sw/cmssw/pull/44498/files#diff-c0b64ac0c0be97495049537672bca975f5be0de08e90cb72bd6000e8496bbf4cR133 I guess that before the...