Matti Kortelainen

assign core,geometry

I found out that C++20 actually makes the signed-integer bit shifts fully defined (and indeed with `-std=c++20` the UBSAN no longer complaints from `(((int64_t)47669215288941) > 63)`). So _maybe_ this will...

+core (no `core` actions in teh end)

@cmsbuild, please close

+core Nothing to add.

@namapane > served depending on the conditions (magnet current). Hardcoding a piece of implementation elsewhere will break this dependence, and one may at some point have a very hard time...

> > The challenge is that the existing magnetic field infrastructure is not usable in GPU, which is what I believe @lecriste et al would need to do (in one...

@namapane Do I understand correctly that your preference would be to replicate this logic (plus the surrounding code it needs) https://github.com/cms-sw/cmssw/blob/2e5dc6dfc7a5b5c7fc69b46f79859ee02b97e3b3/MagneticField/ParametrizedEngine/plugins/AutoParametrizedMagneticFieldProducer.cc#L74-L85 for obtaining the parameters into a separate ESProducer that...

> > Shall we get [these four parameters values](https://github.com/cms-sw/cmssw/blob/2e5dc6dfc7a5b5c7fc69b46f79859ee02b97e3b3/MagneticField/ParametrizedEngine/plugins/AutoParametrizedMagneticFieldProducer.cc#L75-L78) from [this namespace](https://github.com/cms-sw/cmssw/pull/44360/files#diff-c481998af768915e7f11642e2bd9481b5b591301b35e9d8fc77bce3890982043) rather than hardcoding them again? > > Fine for me providing that this does not require to move...

FYI @Dr15Jones