1 / 5

LEP Archive working group

Study proposes archiving Long-term LEP data for future analysis, outlining issues, implications, and resources needed. Act now to preserve valuable data and software resources.

laurelg
Download Presentation

LEP Archive working group

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. LEP Archive working group • Formed at request of LEPC • Reporting on 31st March • Purpose: • Study issues pertaining to long term (10-20 years) storage of LEP data • Archive should allow future analysis based on new experimental or theoretical input • Analysis for educational purposes is not a primary objective • Assumption: • No CERNLIB, BOS, GEANT3 etc. • Julia, Alpha, Galeph etc. will not be runnable

  2. The data • No need to archive raw data (do not foresee reprocessing!) • Archive part or all of POT format, plus MINI, both data and MC • Volume is a few TB/expt., small c.f. LHC • Archive all ‘meta-data’ (ADBS, beam spot, run quality etc.) • has to be identified and documented. • Unmaintainable unless in format common to the data • If we do nothing: • Media will become obsolete soon after end of LEP2 analysis • Meta-data will be lost • Knowledge on how to run analysis will be lost • No running software will exist to read the the data • Must decide now. Experienced manpower will be lost already in 2000

  3. Proposal • Start now feasibility studies • Decide what data and meta-data needs to be saved, make sure it is fully documented. Includes MonteCarlo data • Choose SAME storage model as LHC experiments (Objectivity/DB) • Standalone verification that data is correct and complete (e.g. by redoing a simple analysis WITHOUT using any existing Aleph/CERNLIB software) • Save existing Galeph, Julia, Alephlib, Alpha, generators etc. source codes for documentation purposes

  4. Resources needed: • Before 2000 • ~ One person year per experiment • ~ One or two person years from IT division • Licences, storage media • During lifetime of archive • Babysitter to follow technology evolution • NB. Becomes rapidly unusable if there is major change in storage model • Outstanding issues • Ownership of data: who has access, who can publish, what is author list? • Collaborations must decide now • Common ‘4-vector’ format for simple combined analysis? • Wider dissemination • No control over publication

  5. CERN OPEN DAY • Saturday 4th April, 9:00 to 18:00 • Many guides needed (esp. Italian+French speaking) • Sign up now!

More Related