Skip to content
Snippets Groups Projects
Commit 42452656 authored by Rosen Matev's avatar Rosen Matev :sunny:
Browse files

Merge branch 'release-v41r5' into 'master'

Prepare Analysis v41r5

See merge request !960
parents b7fcf509 54c1cd2d
No related branches found
Tags v41r5
1 merge request!960Prepare Analysis v41r5
Pipeline #5211880 passed
......@@ -11,7 +11,7 @@
cmake_minimum_required(VERSION 3.15)
project(Analysis VERSION 41.4
project(Analysis VERSION 41.5
LANGUAGES CXX)
# Enable testing with CTest/CDash
......
2023-03-03 Analysis v41r5
===
This version uses
Rec [v35r5](../../../../Rec/-/tags/v35r5),
Lbcom [v34r5](../../../../Lbcom/-/tags/v34r5),
LHCb [v54r5](../../../../LHCb/-/tags/v54r5),
Gaudi [v36r11](../../../../Gaudi/-/tags/v36r11),
Detector [v1r9](../../../../Detector/-/tags/v1r9) and
LCG [103](http://lcginfo.cern.ch/release/103/) with ROOT 6.28.00.
This version is released on the `master` branch.
Built relative to Analysis [v41r4](/../../tags/v41r4), with the following changes:
### New features ~"new feature"
### Fixes ~"bug fix" ~workaround
### Enhancements ~enhancement
- ~"MC checking" | MCTruthAndBkgCat.py - better settings and logging, !959 (@erodrigu)
- ~Tuples | Add FunTupleEvent algorithm (Replacement for EventTuple), !955 (@amathad)
### Code cleanups and changes to tests ~modernisation ~cleanup ~testing
### Documentation ~Documentation
### Other
- ~Functors ~Tuples | Cleanup TrackIsolation functorcollection, !954 (@tfulghes)
- ~Functors ~Tuples | Add more functors to access neutral CALO information, !952 (@jzhuo)
- ~Functors ~Tuples | Add a PID functor collection, !950 (@pkoppenb)
- ~Functors ~Tuples | Add array input support for the thor functor grammar, !948 (@jzhuo) [gitlab.cern.ch/lhcb/Rec/-/merge_requests/3283#95429,gitlab.cern.ch/lhcb/Rec/-/merge_requests/3283/diffs#95429]
- Release notes upadted for v41r4, !951 (@pkoppenb) [[gitlab.cern.ch/lhcb/Rec/-/merge_requests/3283#95429,gitlab.cern.ch/lhcb/Rec/-/merge_requests/3283/diffs#95429]
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment