1 / 8

Status of Upgrade releases

Status of Upgrade releases. David Lange Eric Brownson March 22, 2013. More details found in my PPD talk : https :// indico.cern.ch / getFile.py / access?contribId =7&resId=1&materialId= slides&confId =242008 . Release plan has not changed significantly since January workshop.

eman
Download Presentation

Status of Upgrade releases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of Upgrade releases David Lange Eric Brownson March 22, 2013 More details found in my PPD talk: https://indico.cern.ch/getFile.py/access?contribId=7&resId=1&materialId=slides&confId=242008

  2. Release plan has not changed significantly since January workshop • CMSSW_6_1_X will be basis for near-term production in support of upgrade work • Latest and greatest fully validated release • Support for very high pileup digitization (at acceptable memory footprint) • Nominally changes should be validated in CMSSW_6_2_X development release cycle and then backported to CMSSW_6_1_X • Code that is compatible with current and upgraded detector configurations is highly desired but not essential • Compatibility can be maintained via conditions or configuration • A lot of incompatible code will lead to delays in integration. • We don’t have a way to support integration builds for incompatible code

  3. Scenario implementation • We propose to provide configurations indexed by year. E.g.: • 2015: Post LS1 detector • 2017: Add phase 1 pixel detector • 2019: Add phase 1 HCAL detector • Etc…. • This scheme also provides a natural way of handling detector aging parameters. We will provide a simple ES producer to have a central definition of integrated and instantaneous luminosities • So far we are keeping all python configuration changes that depend on geometry in handful of customization functions. • Developing scheme to support these changes within nominal cff structure using tracking use case for initial development

  4. Proposal for release schedule over next months • We anticipate a higher rate of code changes to be integrated given goals over the next months. • Propose to integrate tags into releases based on these deadlines separated by two weeks: • April 5 • April 19 ** latest chance for anything to run in production for June • May 3 • May 17 • Etc… • Expect the corresponding releases to then be available 1 week after these deadlines. Anticipate needing to maintain multiple releases given incompatible codes.

  5. Readiness for CMSSW_6_1_X(as I understand them – apologies for omitting items)

  6. Readiness for CMSSW_6_1_X (2)

  7. Readiness for CMSSW_6_1_X (3)

  8. Readiness for CMSSW_6_1_X (4)

More Related