Closed jmcarcell closed 6 months ago
Alternative proposal (changes in the last commit): Remove the UniquePtr test which isn't doing anything than the other tests are not doing and set Cardinality to 1 which is how algorithms that can't run in parallel are set, for example: https://gitlab.cern.ch/gaudi/Gaudi/-/blob/master/GaudiKernel/include/GaudiKernel/Algorithm.h#L24
Having some algorithms around is good because not everything will be functional and it also allows to test if they can be mixed together.
If there aren't any more complaints I'll merge this today. I think the plan is to remove GaudiAlg for the version 40 of Gaudi so there is time but there are a few repos that have to be changed
I think this looks good. One thing that is not entirely clear to me: Is the EventContext
usable in any meaningful way for a "normal" algorithm? Or is that just used by the scheduler to make sure to use the right inputs?
I'm not sure I have seen that being used by an algorithm. There is an event number that could be used for seeding I guess but we have that information in the headers
BEGINRELEASENOTES
ENDRELEASENOTES
This can also serve as example for other repos, basically adding a
const EventContext&
in the arguments toexecute
and makingexecute
const and changingGaudiAlgorithm
toGaudi::Algorithm
. Headers change too:GaudiAlg/GaudiAlgorithm.h
toGaudi/Algorithm.h