1 / 8

New repository for configuration data of official analysis

New repository for configuration data of official analysis. Offline weekly: 15 Jan 09. What for ?. In production mode, analysis results need to be traceable and reproducible Analysis task configuration data should come from a single source

ronli
Download Presentation

New repository for configuration data of official analysis

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. New repository for configuration data of official analysis Offline weekly: 15 Jan 09

  2. What for ? • In production mode, analysis results need to be traceable and reproducible • Analysis task configuration data should come from a single source • Constants used, cuts, control data and reference histograms • Not directly bound to AliRoot release cycle • Analysis configuration data will require much frequent updates • Configuration data should be globally accessible

  3. How to implement • Short discussion this week concluded that a separate SVN repository for analysis configuration data is a good start point • Another option would be sort of ACDB, but harder to start with and would need a much more strict formalism to implement and impose • SVN ideal to handle versioning and keep track of history • Repository data has to be migrated and maintained in parallel in AliEn FC

  4. Proposal • Directory structure of this repository to be agreed • Every PWG would have to maintain its own directory and the consistency of the configuration files needed to run an analysis task at a given time • Complete freedom in what kind of data should be put in what file within task directory • To facilitate inclusion of each task in the official trains, a configuration macro template will be provided • Single entry point for each analysis has to create, configure and attach the task to an existing train (analysis manager)

  5. Proposed directory structure • /AliAnalysis/trains – train macros • /AliAnalysis/jdls – corresponding jdl-s • /AliAnalysis/PWGn – subdirs allowed starting from here • .../PWG2/SPECTRA , .../PWG2/SPECTRA/data • .../PWG4/JETAN/ConfigJetAnalysis.C • A macro would run regularly (nightly builds) and in case of modification, map SVN changes to a parallel directory structure in AliEn FC • Adding version number in the path

  6. Tested so far... • The directory structure (for now in Mihaela's AliEn space) • Copied there configuration and/or data files for all tasks tested in the train • JDL and train macro updated accordingly • Tested with AliRoot v4-16-Rev-03 • Some PWG2 and PWG4 tasks not working with this version due to restructuring of their task code

  7. Problems • Some tasks are compiled run-time with ACliC (PWG2 proton, checkV0, strange and femtoscopy) • Not compiled in an AliRoot library and not migrated with AliRoot in AliEn • Solution: compile these tasks in AliRoot or migrate also .cxx for AliEn • The new repository will not contain source code, but there will be still tight dependencies with AliRoot • Configuration will likely change together with task code = > AliRoot version required need to be known • Configuration and data files have still to be copied in WN workspace

  8. To do's • Template for task inclusion in train: • AliAnalysisTask *AddTaskXXX(const char *type, AliAnalysisDataContainer *top) • Propagate this for all PWG tasks • Creation of new repository • Script to populate AliEn FC with the new structure

More Related