Run2Support issueshttps://gitlab.cern.ch/lhcb/Run2Support/-/issues2023-09-16T09:19:27+02:00https://gitlab.cern.ch/lhcb/Run2Support/-/issues/14Release Run2Support v2r2p42023-09-16T09:19:27+02:00Gloria CortiRelease Run2Support v2r2p4Dummy release to propagate LHCb [v53r9p5](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p5) release to Gauss Sim10
cc: @adavis, @kreps, @mwhiteheDummy release to propagate LHCb [v53r9p5](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p5) release to Gauss Sim10
cc: @adavis, @kreps, @mwhiteheRun2Support v2r2p4Gloria CortiGloria Cortihttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/13VPDet Test failing in DD4HEP slots2023-08-24T11:24:21+02:00Christopher Rob Jonesjonesc@hep.phy.cam.ac.ukVPDet Test failing in DD4HEP slotsSee e.g.
https://lhcb-nightlies.web.cern.ch/nightly/lhcb-master/2135/Run2Support/x86_64_v2-centos7-gcc12-dbg/tests#VPDet_veloaligncond_updates_yaml_pyconf
Appears to be related to when support for the BeamSpot condition was recently ad...See e.g.
https://lhcb-nightlies.web.cern.ch/nightly/lhcb-master/2135/Run2Support/x86_64_v2-centos7-gcc12-dbg/tests#VPDet_veloaligncond_updates_yaml_pyconf
Appears to be related to when support for the BeamSpot condition was recently added.
```
VeloAlignCond VERBOSE Making transformation matrix for '/VPRight' Correcting for motion system position.
LHCb__DetDesc__TestBeamSpot_11d9... ERROR Wrong DataObjectType : The type expected for /Event/IOVLock is AnyDataWrapper<std::shared_ptr<dd4hep::cond::ConditionsSlice> > and is different from the one of the object in the store which is ICondIOVResource::IOVLock.
LHCb__DetDesc__TestBeamSpot_11d9... ERROR Maximum number of errors ( 'ErrorMax':1) reached.
HLTControlFlowMgr FATAL Event failed in Node LHCb__DetDesc__TestBeamSpot/LHCb__DetDesc__TestBeamSpot_11d983b1 : Error in algorithm execute
```
In an effort to clean in the test results in the nightlies it would be good to address this.
FYI @cattanem @gcorti @rmatev @raaijhttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/12Move Event Model to Run2 namespace for Lamarr use2023-10-20T19:17:51+02:00Adam DavisMove Event Model to Run2 namespace for Lamarr useTo use Lamarr with both Run12 and Run3 event models, must be able to compile and talk to both. This means the porting of
Kernel/LHCbKernel
Event/TrackEvent
Event/DigiEvent
Event/RecEvent
Event/PhysEvent
from LHCb run2-patches to Ru...To use Lamarr with both Run12 and Run3 event models, must be able to compile and talk to both. This means the porting of
Kernel/LHCbKernel
Event/TrackEvent
Event/DigiEvent
Event/RecEvent
Event/PhysEvent
from LHCb run2-patches to Run2Support into the Run2 namespace.
MRs which do this:
- [Run2Support!37 : LHCbKernel and TrackEvent](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/37)
- [Run2Support!38 : DigiEvent](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/38)
- [Run2Support!40 : RecEvent](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/40)
- [Run2Support!41 : PhysEvent](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/41)
- [Run2Support!42 : Top level CMakeLists](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/42)
- [Run2Support!44 : Add Event Packer for Run2 namespace wrapped EDM](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/44)
Already note that LHCb::ParticleID is not ported as there is no difference between master and current. Should this change, it will also need to be ported.
To ensure that the data written with this can be read by older versions of DaVinci (which do not know about the Run2 namespace), one should write the packed event model to DST, at which point downstream software does not need to know about namespacing (@clemenci 's idea).Gloria CortiMichal KrepsAdam DavisLucio AnderliniGloria Corti2023-04-14https://gitlab.cern.ch/lhcb/Run2Support/-/issues/11Release v2r2p32023-02-15T17:01:00+01:00Gloria CortiRelease v2r2p3Dummy release to propagate LHCb [v53r9p4](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p4) release to Gauss Sim10
cc: @adavis, @krepsDummy release to propagate LHCb [v53r9p4](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p4) release to Gauss Sim10
cc: @adavis, @krepsRun2Support v2r2p3https://gitlab.cern.ch/lhcb/Run2Support/-/issues/10Calo not working with Run2Support/DetDesc2023-02-22T16:21:01+01:00Michal MazurekCalo not working with Run2Support/DetDesc@gcorti @sponce
The following discussion from !32 should be addressed:
- [ ] @mimazure started a [discussion](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/32#note_6366790): (+4 comments)
> @sponce
>
> I just...@gcorti @sponce
The following discussion from !32 should be addressed:
- [ ] @mimazure started a [discussion](https://gitlab.cern.ch/lhcb/Run2Support/-/merge_requests/32#note_6366790): (+4 comments)
> @sponce
>
> I just tried running a simulation job with calorimeters/2016 with DetDesc on Run2Support and I get the following error:
>
> ```
> get():: No valid data at '/dd/Structure/LHCb/DownstreamRegion/Prs'
> ```
>
> The same configuration for DetDesc on LHCb works correctly. Is this expected?Sebastien PonceSebastien Poncehttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/9Release v2r2p22023-02-15T16:50:41+01:00Gloria CortiRelease v2r2p2Dummy release to propagate LHCb [v53r9p3](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p3) release to Gauss Sim10
Also explicitly fix full version of LHCb to be used.
cc: @adavis, @krepsDummy release to propagate LHCb [v53r9p3](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p3) release to Gauss Sim10
Also explicitly fix full version of LHCb to be used.
cc: @adavis, @krepsRun2Support v2r2p2https://gitlab.cern.ch/lhcb/Run2Support/-/issues/8Release v2r2p12022-11-17T18:13:15+01:00Gloria CortiRelease v2r2p1Dummy release to propagate LHCb [v53r9p2](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p2) release to Gauss Sim10
cc: @adavis, @kreps, @cattanem, @clemenciDummy release to propagate LHCb [v53r9p2](https://gitlab.cern.ch/lhcb/LHCb/-/releases/v53r9p2) release to Gauss Sim10
cc: @adavis, @kreps, @cattanem, @clemenciRun2Support v2r2p1https://gitlab.cern.ch/lhcb/Run2Support/-/issues/7Review unification of CaloCellID when branching off for Sim102023-10-20T19:19:00+02:00Gloria CortiReview unification of CaloCellID when branching off for Sim10Need to verify if CaloChannelID for Run3 as used here from Detector::Calo is fully compatible with the one needed for Run1&Run2Need to verify if CaloChannelID for Run3 as used here from Detector::Calo is fully compatible with the one needed for Run1&Run2https://gitlab.cern.ch/lhcb/Run2Support/-/issues/6Release v2r22022-08-30T16:13:17+02:00Gloria CortiRelease v2r2Release based on LHCb >= v53r8p1, needed for release of Gauss `Sim10` v56r0.
cc: @kreps, @adavis, @rmatev, @cattanemRelease based on LHCb >= v53r8p1, needed for release of Gauss `Sim10` v56r0.
cc: @kreps, @adavis, @rmatev, @cattanemRun2Support v2r2Gloria CortiGloria Cortihttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/5Port CaloUtils and CaloInterfaces from LHCb as for Run3 they are replaced by ...2022-08-29T19:19:36+02:00Gloria CortiPort CaloUtils and CaloInterfaces from LHCb as for Run3 they are replaced by CaloFutureXXXThe following discussion from lhcb/Gauss!861 should be addressed:
- [ ] @gcorti started a [discussion](https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/861#note_5658416): (+4 comments)
> Something like this will be needed to tar...The following discussion from lhcb/Gauss!861 should be addressed:
- [ ] @gcorti started a [discussion](https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/861#note_5658416): (+4 comments)
> Something like this will be needed to target `Futurev4` for Gauss-on-Gaussino.
>
> Determining now if Gauss will be released on LHCb v53r8p1, so we may not pick this up if it depends on lhcb/LHCb!3860
>
> cc: @kreps, @adavis, @mimazure
These are needed only by Lamarrhttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/4Release v2r12022-03-25T18:11:42+01:00Gloria CortiRelease v2r1Release based on LHCb v53r6, needed for release of Gauss `Sim10` v55r4.
cc: @kreps, @adavis, @rmatev, @cattanemRelease based on LHCb v53r6, needed for release of Gauss `Sim10` v55r4.
cc: @kreps, @adavis, @rmatev, @cattanemRun2Support v2r1Gloria CortiGloria Cortihttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/3Release v2r0 for Gauss v55r22021-11-24T10:58:29+01:00Gloria CortiRelease v2r0 for Gauss v55r2This release against LHCb v53(r1) needs to be made in order to release Gauss v55r2.
It uses the new cmake (mr !12) where the required dependency is for 53.0. Version 53.1 for LHCb will be fixes in lhcbstack.
The version is 2.0/v2r0 du...This release against LHCb v53(r1) needs to be made in order to release Gauss v55r2.
It uses the new cmake (mr !12) where the required dependency is for 53.0. Version 53.1 for LHCb will be fixes in lhcbstack.
The version is 2.0/v2r0 due to the cmake incompatibility with the previous version.
cc: @kreps, @adavis, @clemenci, @rmatevhttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/2Release v1r1 built against LCG_1002021-06-17T14:59:31+02:00Gloria CortiRelease v1r1 built against LCG_100New release of Run2Support for Gauss next release.
Identical to Run2Support but build against
- LHCb v52r1
- Gaudi v35r4
- LCG_100
cc: @adavis, @krepsNew release of Run2Support for Gauss next release.
Identical to Run2Support but build against
- LHCb v52r1
- Gaudi v35r4
- LCG_100
cc: @adavis, @krepshttps://gitlab.cern.ch/lhcb/Run2Support/-/issues/1Release first version of Run2Support2021-03-17T17:13:24+01:00Gloria CortiRelease first version of Run2SupportThe first version of Run2Support should allow at least to merge Lamarr to Gauss reinstating the classes needed and removed from LHCb v51r3.
This could be decoupled with a separate tag - if not a release - allowing the merge of lhcb/LHC...The first version of Run2Support should allow at least to merge Lamarr to Gauss reinstating the classes needed and removed from LHCb v51r3.
This could be decoupled with a separate tag - if not a release - allowing the merge of lhcb/LHCb!2804 incorporating here what is in lhcb/Gauss!664 so that Gauss could be releases against LHCb HEAD (still with LCG_97a_LHCB_N)
cc: @clemenci, @cattanem, @kreps