- Jan 19, 2017
-
-
Marco Clemencic authored
See merge request !268
-
- Jan 18, 2017
-
-
Charles Leggett authored
-
- Jan 13, 2017
-
-
Charles Leggett authored
This is a minor MR that introduces more accurate terminology within the graph-based scheduler. In particular, the `ExecutionFlowGraph` is renamed to `PrecedenceRulesGraph`. See merge request !266
-
- Jan 11, 2017
-
-
Charles Leggett authored
Small improvement to `DataObjectHandle` to use System::typeinfoName to extract the type when issuing a mis-match error message. Results in the type being de-mangled from something like ``` ERROR The type provided for /Event/Rec/Track/BestRichDown is 14AnyDataWrapperIN5Gaudi6Range_ISt6vectorIPKN4LHCb5TrackESaIS6_EEN9__gnu_cxx17__normal_iteratorIPKS6_S8_EEEEE and is different form the one of the object in the store. ``` to ``` ERROR The type provided for /Event/Rec/Track/BestRichDown is AnyDataWrapper<Gaudi::Range_<std::vector<LHCb::Track const*,std::allocator<LHCb::Track const*> >,__gnu_cxx::__normal_iterator<LHCb::Track const* const*,std::vector<LHCb::Track const*,std::allocator<LHCb::Track const*> > > > > and is different from the one of the object in the store. ``` Chris See merge request !272
-
- Jan 10, 2017
-
-
Illya Shapoval authored
-
Christopher Rob Jones authored
Improve type information in mis-match error messages to use System::typeinfoName in order to get type demangled
-
- Jan 05, 2017
-
-
Charles Leggett authored
When adding the extra input and output deps to an Algorithm's dependency tree, this was converting the DataObjID to a string, then back to a DataObjID, which has the effect of stripping the separation of ('ClassID','key') into 'ClassID/key', which screws up the ATLAS syntax. Also, it's looping twice over the input/outputDataObjs(), adding the contents back to itself, which seem redundant, unless I'm missing something. Also, the use of tuples is needlessly complicated, making the code much more difficult to comprehend. I don't think we're saving any CPU cycles this way (in fact I'm betting we're loosing a bunch in the creation of the tuple), and instead requiring an extra 15 lines of comments to explain what it's doing! The simple loops in the original version made the code much, much more readable.
-
- Dec 21, 2016
-
-
Illya Shapoval authored
-
Illya Shapoval authored
-
Illya Shapoval authored
-
Illya Shapoval authored
-
Illya Shapoval authored
-
-
Marco Clemencic authored
and postponed removal of deprecated code See merge request !264
-
Marco Clemencic authored
-
-
-
- Dec 19, 2016
-
-
Marco Clemencic authored
-
Marco Clemencic authored
See merge request !256
-
Marco Clemencic authored
Reverse the const enforcement if appropriate compile time flags are used. It also offers a compile time deprecation warning to identify problematic code. if compiled with `-DALLOW_TOOLHANDLE_NONCONSTNESS`, can call non-const methods of a Tool from a const ToolHandle. Also adds a `ToolHandle.unConst()` method which strips the constness of the ToolHandle, but prints a deprecation warning message at compile time. Requires `-DATLAS`. See merge request !253
-
Marco Clemencic authored
1. In all scenarios: * avoid repetitive data input/output declaration each time an algorithm instance is re-used in the graph of precedence rules; 2. In ATLAS MC data reconstruction scenario: * declare as a test; * hide all occurrences of '::' operator used by data types specifications (otherwise such data items are misinterpreted as alternatives); * remove in-place data modification pattern from the data flow graph (all such occurrences were in fact removed earlier, except one, which is now also removed) See merge request !262
-
Marco Clemencic authored
required by the pre-existing `init` method of `ConditionHandles` (ATLAS). See merge request !260
-
Marco Clemencic authored
the method is used in ATLAS code. See merge request !259
-
- Dec 17, 2016
-
-
Illya Shapoval authored
-
Illya Shapoval authored
-
Illya Shapoval authored
hide '::' operator in the ATLAS MC reco data flow graph (to avoid false creation of data alternatives)
-
Illya Shapoval authored
-
Illya Shapoval authored
precedence.py: avoid repetitive data input/output declaration each time an algorithm instance is re-used in the graph of precedence rules
-
- Dec 16, 2016
-
-
Charles Leggett authored
-
-
Charles Leggett authored
-
- Dec 15, 2016
-
-
Charles Leggett authored
-
Sebastien Ponce authored
-
Charles Leggett authored
-
- Dec 14, 2016
-
-
Marco Clemencic authored
See merge request !252
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Marco Clemencic authored
-
Benedikt Hegner authored
See merge request !251
-