Tags: martenole/AliceO2
Tags
Temporarily removing the lzma support from CompStream Dependencies need to be resolved first. Lzma package is included in the software stack already today, but not as a requirement for boost. Furthermore, boost seems to use a different find procedure, as it does not find the package in a non-system place.
Temporarily removing the lzma support from CompStream Dependencies need to be resolved first. Lzma package is included in the software stack already today, but not as a requirement for boost. Furthermore, boost seems to use a different find procedure, as it does not find the package in a non-system place.
Removing obsolete code and some minor cleanup less functor for temporary internal bookkeeping struct removed, std::less is directly using operator<
DPL: saner rate for rate channel logger Since real people are starting to use DPL, it turns out it is not particularly user friendly, especially with many devices and without the GUI, to have so many messages about the performance rate. As a quick fix I hardcoded a saner value than the current one. This should probably be made configurable in an easy way.
DPL: saner rate for rate channel logger Since real people are starting to use DPL, it turns out it is not particularly user friendly, especially with many devices and without the GUI, to have so many messages about the performance rate. As a quick fix I hardcoded a saner value than the current one. This should probably be made configurable in an easy way.
DPL: saner rate for rate channel logger Since real people are starting to use DPL, it turns out it is not particularly user friendly, especially with many devices and without the GUI, to have so many messages about the performance rate. As a quick fix I hardcoded a saner value than the current one. This should probably be made configurable in an easy way.
DPL: adapt to support new FairMQ versions FairMQ changed `FairMQDevice::fDevice` to a shared_ptr from a unique_ptr. This makes sure we can compile DPL with both version and introduces an helper to handle this kind of situations in the future when updating might not be an option.
Use LOG(INFO) instead of Info() This is a bug fix. I found that the Info() API (from ROOT?) interferes with the LOG(INFO) system from FairLogger. Since the latter is also used for control in DPL, some control messages were sometimes not dispatched correctly leading to non-exiting DPL workflows.
DPL: create index of distinct InputRoutes While being just a minor performance improvement, this refactoring will come useful with the coming integration of proper Lifetime for objects.
PreviousNext