ATLAS ATLAS Week: 25/Feb to 1/Mar 2002 Data Manager Design Status Report http://hepunx.rl.ac.uk/atlasuk/simulation/level2/meetings/ PESA270202/DM.ppt DM.pdf DM.ps John Baines Contents: • Motivation • Use Case • First Design : • Components • Interfaces • RobMaper • Status • Second Design Iteration • Summary
12
Embed
ATLAS ATLAS Week: 25/Feb to 1/Mar 2002 Data Manager Design Status Report DM.pdf.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Motivation• The PESA s/w high level design includes a Data Manager.
• It’s function is to provide the same interface to data for LVL2, EF and offline
• This divides into access to :
•Raw Data
•Reconstructed objects
• Also considered as possibly part of the Data Manager Domain are :
• Access to LVL1 info (but also possibly done from top-level algorithm)
• Packing of LVL2 result and transmission to Data Collection.
ATLAS Week 25/Feb to 1/Mar 2002 3
Use Case &Collaboration Diagram for a
Possible Implimentation
1) Data Manager receives request for data in region specified by Geometrical Volume Descriptor. 2) Data Manager asks RoB Mapper to convert Geometrical Volume into list of RoB IDs. 3) Data Manager checks if all/part of data already present in Event Store. 4) If not, Data Manager requests data from Rob Data Collector. 5) Data Manager stores the data returned in Event Store. 6) Data Manager selects requested data from Event Store
and returns it to requester.
ATLAS Week 25/Feb to 1/Mar 2002 4
Components of the Design• Geometrical Region : describes region either :
• in purely geometrical terms (e.g. cone defined in terms of and or road about a track-helix), or• as mixture of geometrical and detector-specific info. (e.g. an cone plus a list of detector layers).
• Rob Mapper : receives GeometricalRegion and returns list of RoB Identifiers for all RoB that contain detectors lying wholly or partially inside GeometricalRegion.
• Byte Stream To Object Converter : Performs conversion of raw data received from RoS to collections of Digit Objects.
• Rob Data Collector : receives a list of RoB Identifiers and formulates the specific requests to be sent to Data Collection. The Rob Data Collector hides the details of Data Collection from the Data Manager.
• Data Preparation : Converts the raw data to the form requested, e.g. after calibration or SCT cluster-finding.
ATLAS Week 25/Feb to 1/Mar 2002 5
Possible Interfaces
•Gaudi & Athena frameworks use idea that concrete classes can inherit from several interfaces.
•Separate Data Manager interface as follows:
• ITrigEventStoreSvc : Storage and retrieval of intermediate results. Similar to Athena IStoreGateSvc interface. • ITrigDetDataSvc : Retrieval of detector data, either raw or pre-processed. Differs from ITrigEventStoreSvc interface in that the detector identifier and geometrical region for data collection are specified. •ITrigLvl1DataSvc : Retrieval of LVL1 data in the form of a list of RoI.
ATLAS Week 25/Feb to 1/Mar 2002 6
• GeometricalRegion base class defined with 3 derived
classes : EtaPhiCone, HelicalRoad1, and HelicalRoad2 • RobMapperSvc designed by Weidong Li Implemented for SCT and Pixels:
• RoB composed of RobElement (MUR)•Two step search for RobElements in region: • Search for first RobElement inside the geometrical Region (seed RobElement)• Use clustering-type approach to add neighbouring RobElements
• Preliminary timing measurement for mapping a SCT region defined by a pixel seed (800 MHz PIII)