1 / 4

IceCube Collaboration Workshop: Configuration and Resource Management Strategies

The IceCube Collaboration Meeting at Berkeley from March 19-23, 2005, focused on developing a streamlined configuration framework for IceTray using ASCII steering files for computing resources and session management. Key discussions included the transition from ASCII configurations to XML schemas, the establishment of a Production Database, and methods for cataloguing and searching processed files. Emphasis was placed on minimal configuration information essential for enhancing data management and optimizing neutrino generator outputs through integration with various batch systems.

morwen
Télécharger la présentation

IceCube Collaboration Workshop: Configuration and Resource Management Strategies

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. @ simulation workshop IceCube Collaboration Meeting Berkeley – 19-23 March 2005

  2. configuration • right now working with • simple ASCII steering file with list of variables for computing resources & second ASCII config file for IceTray-root session (CINT macro) • ASCII steering → config.xml • xml schema defined (config.xsd) • <steering> … </steering> for computing resources settings • <runtime> … </runtime> for IceTray configuration → CINT macro (to be changed) • configuration ↔ unique dataset ID • dataset ID → multiple runs (with same ID ≡ configuration) • keep history of file • Production DB during production • in file header (?) • config.xml file in I3DB (?) • minimal config.xml info to be used for Data Center for searching purposes

  3. Data Center • Store processed files into the Data Center • file-to-be-stored + metadata file • metadata file = <DIF> (cataloguing NSF-req) + <DIF_plus> (search facility) • Cindy willing to provide a search facility in Data Center • need to the <DIF_plus> section of metadata schema • WE need to provide specific schema for <DIF_plus> • our proposal for <DIF_plus>: • <Date> • use <runtime> section of config.xml file • minimal info to search for is : module names, module classes, version • additional info : module parameters and values • reference to config.xml file (URL, dir, I3DB, ?) • Other options:

  4. Work @ UW • Basic Production tools working with PBS • configuration service (xml and parser) under completion (IceTray?) • production DB under design • GUI (implementation to be started) • computing resources (Juan Carlos) • UW GLOW facility testbed: condor clusters throughout Campus • interface Condor-G (Globus toolkit) to variety of batch system • Module implementation (Aya Ishihara) • ANIS neutrino generator • core code can be used with other generators (NUSIM) • plan: • NUSIM neutrino generator • reader for FLUKA shower generator (muons, neutrinos, conventional and prompt) • C++ class to apply physics weights to neutrino generator output

More Related