- Mar 15, 2024
-
-
CPAlgorithms: distinguish between MC and data when writing output branches
-
- Mar 07, 2024
-
-
Baptiste Ravina authored
-
Ryan Quinn authored
-
- Mar 06, 2024
-
-
Tadej Novak authored
-
- Mar 05, 2024
-
-
CP algorithms: rename the jvt selection name to something more explanatory
-
- Mar 04, 2024
-
-
Tadej Novak authored
-
Tadej Novak authored
-
- Mar 01, 2024
-
-
Nils Erik Krumnack authored
Essentially this ensures that users don't misspell their selection names, or use a selection name they forgot to define. This is only for full selections, for preselections I don't do it, as I usually ask for them before they are defined. I also don't do it for the baseline selection. If that is not present that just happens.
-
- Feb 29, 2024
-
-
Revert "Remove FTAG selectionNmaes that are actually never used." This reverts commit 436ed695.
-
- Feb 27, 2024
-
-
Tadej Novak authored
-
Nils Erik Krumnack authored
This is a followup to !68703 that uses that mechanism to add factories for all components used by the common CP algorithms. This is not necessarily the prettiest way of doing things, but it is what can be practically done right now with little effort. It should probably be replaced by a better mechanism at some point. Command to test/run this: ``` FullCPAlgorithmsTest_eljob.py --data-type data --algorithm-memory --factory-preload 'libComponentFactoryPreloaderDict.so,CP::preloadComponentFactories' --block-config --use-flags ```
-
- Feb 26, 2024
-
-
Nils Erik Krumnack authored
The basic idea here is that dictionaries are fairly heavy when used as a factory. Registering factory functions instead makes the jobs a lot lighter. For the CP algorithm test job (on data) the savings are: ~600 MB in memory ~22s in startup time one major root dependency eliminated The first draft also included a function for preloading all the dictionaries. I removed it to allow the user to define their own.
-
- Feb 24, 2024
-
-
Tadej Novak authored
-
Tadej Novak authored
-
- Feb 23, 2024
-
-
Tadej Novak authored
-
- Feb 18, 2024
-
-
CPAlgorithms: bugfix for PerEventSFBlock
-
- Feb 17, 2024
-
-
Removal of legacy config for DAOD production - part 4 This MR removes much of the legacy DAOD-making configuration code, such that the old-style reductionConf argument to Reco_tf will no longer work. Some of the packages touched here may be completely obsolete and so more deletion may be possible, but for this MR the changes are restricted to DAOD building.
-
- Feb 14, 2024
-
-
Baptiste Ravina authored
-
- Feb 12, 2024
-
-
Baptiste Ravina authored
-
- Feb 10, 2024
-
-
Add FTag event scale factor CP algorithm config
-
- Feb 09, 2024
-
-
Remove deprecated runSelection and globalSF from JetJvtAnalysisConfig
-
CPAlgorithms: refactor the object cutflow
-
AthContainers: Update copy/copyForOutput to work on AuxVectorData. Update the copy/copyForOutput methods of IAuxTypeVectorFactory / AuxTypeRegistry to take AuxVectorData instances rather than bare pointers. Remove the corresponding static methods from AuxTypeVector. Refactoring to make possible dependencies between auxiliary variables, as would be used to support packed links / jagged vectors. Also alter them to operate on ranges, rather than a single element.
-
- Feb 08, 2024
-
-
Tadej Novak authored
Revert "Merge branch 'bugfix_objectcutflow' into 'main'" This reverts merge request !68554
-
introduce a simple per-algorithm memory monitor for EventLoop This will **not** be able to detect memory leaks, but instead it will just monitor how much memory an algorithm allocates during setup. This allows to see if any of the algorithms has a particularly large calibration table or similar. It also contains occasional memory usage printouts during the job. That allows to see whether memory gets consumed in the job setup, or during execute This is mostly meant to allow debugging some current problems with the Top jobs which quickly shoot up to 3.2GB memory consumption.
-
CPAlgorithms: refactor the object cutflow
-
Nils Erik Krumnack authored
The main usage here is that if OR is run before MET we don't want to use the OR selections with MET. A similar issue is expected to come up with fakes/fakeable objects, i.e. some specific baseline cuts should not be applied (in fact they are inverted), but only for very specific users. The mechanism chosen here is to mark the cuts when they are registered and then exclude by name when requesting the selection.
-
- Feb 05, 2024
-
-
TextConfig: add block to add blocks from YAML file Inorder to allow for users to add blocks from the YAML file without editting the python code, a new block was added.
-
CPAlgorithms: expose "excludeNSWFromPrecisionLayers" to the muon config
-
- Feb 02, 2024
-
-
CPAlgorithms: smarter systematic printouts
-
- Feb 01, 2024
-
-
Fix forceFullSimConfig default config for PhotonWorkingPointConfig
-
- Jan 31, 2024
-
-
Baptiste Ravina authored
-
- Jan 29, 2024
-
-
TrigPrescalesAlg: Add option for prescale based on trigger formula The trigger option in the prw tool can be a formula (trigA||trigB): https://gitlab.cern.ch/ATLAS-EGamma/athena/-/blob/main/PhysicsAnalysis/AnalysisCommon/PileupReweighting/Root/PileupReweightingTool.cxx#L484 but current implementation of the alg is not intended for this use and would result in decoration: `m_prescaleDecoration+triger_formula` which can lead to problems because of `||`, spaces and such (not sure decorators allow it?). This MR would change it that instead of passing list of triggers one can pass them as `trigFormula` and the decoration would be only `m_prescaleDecoration`, so it would be much more straighforward to use. Taking advantage of existing implementation so the execute part does not change, only the init.
-
- Jan 26, 2024
-
-
Rework interface for GRL and PRW block configuration in CP algos
-
- Jan 19, 2024
-
-
Add Multiple File Force-Input Capability to FullCPAlgorithmsTest_X.py
-
introduce ExecDriver (plus other updates) As the main feature this introduces ExecDriver. The idea behind ExecDriver is that it runs the actual job in a new executable (replacing the current one). This is meant to release all the memory that gets allocated by our configuration helpers. That is over 1GB (mostly ROOT-python dictionaries), so this is a significant savings. There are a couple more updates that work with this: * on merging, if there is only one file I create a hard link instead of merging, which is a lot more efficient. * BatchDriver now respects maxEvents (in a fashion), which makes it easier to do tests with LocalDriver and ExecDriver.
-
Harmonize trigger naming within TriggerAnalysisConfig to TrigEventSelectorAlg, replace ',' with 'p' and '-' with '_'
-
- Jan 18, 2024
-
-
Added forceFullSimConfig for EGamma analysis configs for testing (ATLASG-2661)
-
- Jan 17, 2024
-
-
CPAlgorithms: add event selectors for large-R jets
-
- Jan 12, 2024
-
-
Updated fast sim property for ElectronPhotonFourMomentumCorrection
-