1 / 7

Migration to SL5: Insights from James Bellinger at University of Wisconsin-Madison

On April 21, 2010, James Bellinger from the University of Wisconsin-Madison discussed the migration to SL5, highlighting the recent releases of versions 6.1.6, 6.1.4mc, and 6.1.4. While some minor glitches were noted, the essential packages appeared intact. Bellinger emphasized the need for validation in future releases, particularly version 7.0.1, and the importance of ensuring interoperability with older ROOT files. The conversation touched on challenges with development distribution, user support, and coding practices, indicating ongoing efforts in refining the software.

bisa
Télécharger la présentation

Migration to SL5: Insights from James Bellinger at University of Wisconsin-Madison

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. Migration to SL5 James Bellinger University of Wisconsin at Madison 21-Apr-2010 21-Apr-2010 1

  2. Milestone Migration to SL5 • Announced releases 6.1.6.m, 6.1.4mc.m, and 6.1.4.m last week • Minor glitches but everything seems to be there • Some packages (JointPhysics) still needed fiddling • Well done

  3. What’s Next? • development • Not an ordinary release • No validation: packaging and compilation only • Which external packages should be default? • 7.0.1 • Validation required • Uses root v5_14_00g –q GCC_3_4_3 • Event display gripes but works • Are root files interoperable with old version? • Something is screwed up with the distribution • New release

  4. development • Need to be able to compile/link everything • Not sure we need to have binaries distributed • Not going to be many customers for pulling a development distribution in the first place • Leave development-lite structure alone?

  5. 7.0.1.m Validation • 10K test OK for verifying code • We already verified the system libraries • Verifying new root may need more effort: not a simple matrix • Write 616/SL3 • read 701/SL5 and rewrite and compare • Re-read 616/SL3 and rewrite and compare • Re-read 701/SL4 and compare • Trying to find out what was already done • Murat says they’ve been running successfully, doesn’t remember validation procedures

  6. New Release Desirable • Reprocessing may be in the cards • Claim of 60% more top with modified b-tagging! • Safe to bet that new compilers will call errors what are now just warnings • Extensive minor changes needed, probably not automatable. • Unified Production/MC/ntuple release makes maintenance easier • Probably 7.0.1 follow-on is better than 6.1.7

  7. What next? Offloading products? • The less we support, the better? • Can we use native • python? • perl? • need to maintain oracle interface, so probably not • dddebugger? • gtools? • bison and f2c don’t seem to bundle with SL5, rest do • gsl? • http://www.hep.wisc.edu/~jnb/cdfcode/current/ExternalProducts.xls

More Related