DAST

ATLAS Distributed Analysis Shifters Team (AtlasDAST) is a group of experts shifters that provide to user the first point of contact to addressing all distributed analysis questions, including analysis tools related problems, DDM related problems and in some cases offline software problems. Alden Stradling and Farida Fassi currently coordinate this effort for both AN and EU zones respectively. First DAST shifts started in September 2008. Previous Coordinators are Nurcan Ozturk and Mark Slater.

ATLAS Physics Analysis Tools Group

Convenor: Karsten Koeneke, Attila Krasznahorkay

Physics Analysis Tools (PAT) is a project aiming to develop C++/Python based tools appropriate for Physics Analysis. The group is responsible for the Atlas Analysis Model and for the development of class libraries (in C++ and Python), tools and procedures for physics analysis both in a batch and interactive environment.

Reconstruction Integration Group

The role of the Reconstruction Integration Group (RIG) is to make sure that the software reconstruction developments done in systems, combined performance groups, PAT, HLT groups merge into a well integrated, easy to use, performing and robust reconstruction software. The full scope task and organisation document can be seen there.

Although this group has a number of representatives from other working groups, it is entirely open, in particular to any one who wants to contribute to a specific RIG task, and more generally to anyone contributing to a piece of the reconstruction software.

Software Infrastructure Team (SIT)

The ATLAS Software Infrastructure Team (SIT) is responsible for providing an environment that supports software development and promotes the development of robust, efficient software that addresses the needs of the ATLAS experiment. Work areas.

Core Services

ATHENA core software

Detector Description

Mission: to provide a complete, unified, and memory-efficient description of the ATLAS detector for all of the offline software. The most important clients we serve are the simulation, and the reconstruction.

Note: Wiki dates from 2005

Event Management Board

The EMB is the body responsible for change control of the ATLAS data model, and insures that schema evolution does not become unmanageable.

Role:

Adjudicate and control content of standard ATLAS event data products, and changes thereto. This includes addition and removal of classes as well as content (schema) changes to existing classes. The EMB should act as a "clearing house" for proposed changes, ensuring that the impact of proposed changes are understood before the process commences, that the relevant EDM developer(s), Database expert(s) and other appropriate expert(s) are put into contact, that the changes are validated before being put into production and that the relevant tests are updated (e.g. to ensure no inadvertent changes are made in the future). As part of this process the EMB maintains catalogs of the EDM content and sizes, and includes the role of the prior Physics EDM coordinator to ensure that there is overall architectural consistency.

Performance Management Board (PMB)

The PMB is responsible for ensuring that the cpu and memory usage of ATLAS jobs is compatible with the processing requirements and the production system constraints. This compatibility should be maintained throughout ATLAS detector commissioning, initial collisions, and design luminosity involving pile-up and cavern backgrounds. This responsibility includes:

  • The development of, and the incorporation of existing, monitoring and diagnostic tools into the ATLAS software development and production environments.

  • The development of generic techniques for performance optimization that can be applied to all ATLAS applications.

  • Optimizations of the Athena framework and services that apply such optimization techniques.

  • In conjunction with the subsystems, optimizations of subsystem-specific algorithms, tools and services.

  • The PMB should produce regular reports on the cpu and memory usage for typical production jobs, at least for every release and production caches (patch releases). These reports should be at the level of the subsystems or domains (e.g. detector subsystems and combined reconstruction groups), but should incorporate more detailed reports for individual algorithms, tools and services provided by the subsystems themselves using reporting tools developed by the PMB.

The PMB will build upon the prior work of the Performance Task Force.

The identification of subsystem-specific problem areas is a joint responsibility of the PMB and the subsystem software groups, the former providing the monitoring and diagnostics tools, and the latter applying them within their own subsystem algorithm, tools and services to provide a more detailed breakdown.

The PMB has the authority to raise the priority for solving domain-specific problems such that the subsystem software organizations are expected to assign domain-specific software experts to help with necessary re-design and implementation in a timely manner, diverting their effort from other development activities if deemed necessary by the PMB.

The PMB will present regular reports at the SPMB Meetings in a similar manner to the Event Management Board (EMB), and upon request, at TOB meetings.

Simulation

The ATLAS Simulation Project covers the development of all software needed to handle event simulation in the ATLAS Experiment.

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2013-04-23 - RichardMount
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback