Brahms Participation in Mock Data Challenge

Brahms and the Mock Data Challenge

The Mock Data Challenge was recommended by the Lehman review in July 97. The charge was though not so clearly defined. The importance was stressed later by the January TAC. Later discussions within the weekly RCF-experiment meeting has clarified some issues, but also shown divergent opinions on others.
Brahms sees the MDC-1 as a tool for RCF to checkout and improved the hardware and software tools in place, in particular in regard to raw data storage and retrieval , and the reconstruction aspects. It serves as an important and useful tool for RCF and the experiments to have a common goal at a set time, but limited time. The first goal is to demonstrate the capabilities of RCF, to pinpoint problem areas, that lead to an evaluation of the future hardware and software path for RHIC offline computing. A second goal is for the experiment to be ready with and checkout significant parts of the analysis chain.
BRAHMS goals

Implementation and operation of analysis chain from generation of simulated events, digitization to track reconstruction, Particle Identification and simple physics analysis.
Test the Full chain of software. Learn and understand how to operate this in an environment of multiple (jobs) users, and different access to data.
Employ software that will (or very likely to) be used in the production analysis code for Brahms.

MDC1 Specifics

This set of detectors selected due to

Tasks to be done in preparation for and during the MDC.

Event generation - This is a fairly trivial task; for the small solid-angle detectors the same simulated events can be used multiple times by coordinate transformation to effectively give a large event sample. Needs 2-5K of central and Min bias Au+Au data. (1-1.5 Gb of data)

Digitized data - This requires running GBRAHMS multiple times for several angles, and magnetic field settings.

PID, Beam-Beam Counters - This has still to be fully written. The cpu needs are modest, but i/o rates reasonable high.

Time scale for implementation