Abstract
Now that CMS has started data taking there is a balance to be struck between software release stability for operations and the need to improve the physics and technical performance of the code. In addition new code may need to be developed to correct for unforeseen data taking conditions, and has to be integrated into the mainstream releases with a minimum risk. To keep the process under control, CMS uses regular (twice a day) Integration Builds. A complex set of validation steps is used to verify the software at various stages, from the regular Integration Builds to running a full software and physics validation suite on the grid for major releases. CMS has adopted a development model that tries to strike the correct balance between the needs of stability and a constant improvement; this paper will describe our experience with this model, and tell the story of how the commissioning of the CMS offline has proceeded through the perspective of the past year's releases.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
