Improving collaborative documentation in CMS

Lassila-Perini, K.; Salmi, Leena

doi:10.1088/1742-6596/219/8/082011

Cited by 2 publications

(2 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…CMS has about 17000 twikis serving the entire CMS documentation. The usability of this documentation has been tested [8]. The challenge of such an enormous amount of information is to track the information that may be stale or outdated.…”

Section: Documentationmentioning

confidence: 99%

A Perspective of User Support for the CMS Experiment

Malik

Lassila-Perini

Hegner

et al. 2011

J. Phys.: Conf. Ser.

View full text Add to dashboard Cite

The CMS (Compact Muon Solenoid) experiment is one of two large general-purpose particle physics detectors at the LHC (Large Hadron Collider). An international collaboration of nearly 3500 people operates this complex detector whose main goal is to answer the most fundamental questions about our universe. The size and globally diversified nature of the collaboration and the Petabytes/year of data being collected, presents a big challenging task in bringing users up to speed to contribute to the physics analysis. The CMS User Support performs this task by helping users quickly learn about the CMS computing and the needed physics analysis tools. In this presentation we give an overview of its goals, organization and usage of collaborative tools to maintain the software and computing documentation and conduct year around tutorials on several physics tools needed as a prerequisite for physics. We also talk about the user feedback evaluating its work.

show abstract

Section: Documentationmentioning

confidence: 99%

A Perspective of User Support for the CMS Experiment

Malik

Lassila-Perini

Hegner

et al. 2011

J. Phys.: Conf. Ser.

View full text Add to dashboard Cite

show abstract

“…A large experiment such as the Compact Muon Solenoid (CMS) [2] can produce millions of lines of code, much of it interdependent, with a significant fraction under continuous development [3]. From a software engineering perspective, the HEP environment is complex: simulations, reconstruction algorithms and analyses change as an experiment improves its understanding of its experimental hardware, data acquisition systems, and the underlying physics being studied.…”

Section: Introductionmentioning

confidence: 99%

SpackDev: Multi-Package Development with Spack

et al. 2020

View full text Add to dashboard Cite

High Energy Physics (HEP) software environments often involve ∼ hundreds of external packages and libraries, and similar numbers of experiment-specific, science-critical packages—many under continuous development. Managing coherent releases of the external software stack is challenging enough, but managing the highly-collaborative—and distributed—development of a large body of code against such a stack adds even more complexity and room for error. Spack is a popular Python-based package management tool with a specific focus on the needs of High Performance Computing (HPC) systems and system administrators whose strength is orchestrating the discrete download, build, testing, and installation of pre-packaged or tagged third-party software against similarly stable dependencies. As such it is becoming increasingly popular within HEP as that community makes increasing use of HPC facilities, and as efforts to develop future HPC systems utilize Spack to provide scientific software on those platforms [1]. SpackDev is a system to facilitate the simultaneous development of interconnected sets of packages. Intended to handle packages without restriction to one internal build system, SpackDev is integrated with Spack as a command extension in order to leverage features such as dependency calculations and build system configuration, and is generally applicable outside HEP. We describe SpackDev’s features and development over the last two years, initial experience using SpackDev in the context of the LArSoft liquid argon detector toolkit, and work remaining before it can be considered a fully-functional multi-package build system for HEP experiments utilizing Spack.

show abstract

Improving collaborative documentation in CMS

Cited by 2 publications

References 4 publications

A Perspective of User Support for the CMS Experiment

A Perspective of User Support for the CMS Experiment

SpackDev: Multi-Package Development with Spack

Contact Info

Product

Resources

About