- Jan 06, 2023
-
-
Marco Clemencic authored
Closes #249 See merge request !1404
-
Marco Clemencic authored
See merge request !1403
-
Marco Clemencic authored
See merge request !1395
-
- Nov 29, 2022
-
-
-
patch generated by https://gitlab.cern.ch/vavolkl/Gaudi/-/jobs/26119972
-
- Nov 28, 2022
-
-
Valentin Volkl authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Valentin Volkl authored
-
- Nov 26, 2022
-
-
Valentin Volkl authored
-
- Nov 21, 2022
-
-
Marco Clemencic authored
See merge request !1402
-
Marco Clemencic authored
-
Marco Clemencic authored
See merge request gaudi/Gaudi!1380
-
Marco Clemencic authored
-
- Nov 17, 2022
-
-
Frank Winklmeier authored
`DECLARE_COMPONENT_PROPERTY( MyComponent, "myprop", "value" )` can be used to set properties on already declared components.
-
Marco Clemencic authored
See merge request gaudi/Gaudi!1396
-
Frank Winklmeier authored
Sometimes it is useful to be able to deprecate components, i.e. to make sure a particular job does not use a certain set of components (e.g. a multi-threaded job should not use components that are known to be not thread-safe). This can now be achieved by setting the "deprecated" property in the plugin registry: ``` Registry::instance().addProperty( "MyTool", "deprecated", "optional message" ); ``` In addition, the warning can be turned into an error using the new `setError` method.
-
Marco Clemencic authored
See merge request !1400
-
Marco Clemencic authored
See merge request !1399
-
Marco Clemencic authored
Closes lhcb/Gaudi#3 See merge request !1397
-
Marco Clemencic authored
See merge request !1381
-
- Nov 16, 2022
-
-
Marco Clemencic authored
-
Michal Mazurek authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Marco Clemencic authored
Closes #236 See merge request !1398
-
Marco Clemencic authored
See merge request gaudi/Gaudi!1394
-
Marco Clemencic authored
Closes #240 See merge request !1392
-
- Nov 15, 2022
-
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Chris Burr authored
-
Chris Burr authored
Previously the basket size configuration could only be coarsely applied to all branches but in most real world files the size of the data in each branch varies significantly. Setting a small value causes large branches to be packed into individual baskets and prevents effective compression. Setting a large value improves the compression ratio of large branches but causes excessive memory usage. Instead we change the parameters to only specifiy the maximum and minimum branch size and provide a target for the number of events to pack into each basket. We then use the first event to estimate the size of the branch. This makes the branching very sensitive to the first event size however this seems to work okay in practice. If needed the basket sizes could be refined after several events to give a more precise estimate.
-
-
Marco Clemencic authored
See merge request !1391
-
Marco Clemencic authored
See merge request !1393
-
- Nov 14, 2022
-
-
Marco Clemencic authored
See merge request !1390
-
Marco Clemencic authored
See merge request !1389
-