Figure 3 - available via license: Creative Commons Attribution 3.0 Unported
Content may be subject to copyright.
ROOT package map and its functionality within ROOT.

ROOT package map and its functionality within ROOT.

Source publication
Full-text available
ROOT is a large code base with a complex set of build-time dependencies; there is a significant difference in compilation time between the “core” of ROOT and the full-fledged deployment. We present results on a “delayed build” for internal ROOT packages and external packages. This gives the ability to offer a “lightweight” core of ROOT, later exten...

Context in source publication

Context 1
... enable this feature, we introduces the ROOT package map. On Figure 3 is shown a simplified example of ROOT package map, allowing to enable Base, IO sub-packages together with its dependencies, step by step. ...


... This mindset is becoming ever more popular in HEP as well, among established tools as well as new ones. New developments in ROOT, for instance, emphasize interoperability [12] and ease of installation [13] (e.g. in conda-forge). It's be- Figure 6: Familiarity and usage of data science tools (top) and HEP data analysis tools (bottom) from the same survey as Figure 5. ...
Full-text available
This paper was prepared by the HEP Software Foundation (HSF) PyHEP Working Group as input to the second phase of the LHCC review of High-Luminosity LHC (HL-LHC) computing, which took place in November, 2021. It describes the adoption of Python and data science tools in HEP, discusses the likelihood of future scenarios, and recommendations for action by the HEP community.