1 / 11

Athena on Cosmic Ray Data

Athena on Cosmic Ray Data. March 31, 2005 LNF Maura Barone. EventStorage. Data are written by DataFlow’s EventStorage package. The data blocks written to files are event fragments formatted w/ the event format library

akina
Download Presentation

Athena on Cosmic Ray Data

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. Athena on Cosmic Ray Data March 31, 2005 LNF Maura Barone

  2. EventStorage • Data are written by DataFlow’s EventStorage package. • The data blocks written to files are event fragments formatted w/ the event format library • Fragments are: data from a ROD, ROB or ROS, all the data from a single sub-detector (barrel MDT) • They are ROS fragments • New eformat package, as defined in “The raw event format in the ATLAS trigger & DAQ”, ATL-DAQ-98-129 • This is major version 2.4 • Updated version: 23 feb 2004

  3. General format of a full event ROD fragments: header + data + trailer

  4. Full Event • In general, a Full event is an aggregation of sub-det fragments, and each sub-det fragm is an aggregation of ROS fragms. • Each ROS fragm is an aggreg. of ROB fragms, each one mapping onto one or more ROD fragments • Each fragm (exc ROD) has a header w/ event formatting info • In our case: • there is only 1 sub-det: MDT barrel A side (ID = 0x61) • 1 ROS (module type: 02) • 1 ROB (module type: 01) • 1 ROD (module type: 00) • A fake FullEventFragment is created (ByteStreamCnvSvc) • ROS source id 0x26100  0x66100 6 = SFI Module Type • Dump of ROD fragments inside ATHENA  correct

  5. Dump w/ StorageReader. Run 1012 ROS ROD ROB

  6. Run 1012 - Source ID ROS: 2 / 61 / 00 ROD: 0 / 61 / 00 ROB: 1 / 61 / 01

  7. Run 1012 - ROD fragment ROD trailer ROD header TCM data Output format compatible with Design Specifications of CSM-1 “CSM-1 & CSM Design Manual”, UMHE-02-10 Output format not compatible with MROD Data Format “The MROD data format and tower partitioning of the MDT chambers”, HEN-434

  8. H8 TB 2004 Output format compatible with MROD Data Format “The MROD data format and tower partitioning of the MDT chambers”, HEN-434

  9. H8 TB 2004 Output format compatible with MROD Data Format “The MROD data format and tower partitioning of the MDT chambers”, HEN-434

  10. Open Questions - Online Enrico: “ il problema non e’ nell’event format, ma nel modo in cui Athena si aspetta il frammento dei mu dentro il rod fragment, che non e’ una specifica daq, ma deriva dall’hw.” • What is a “daq specification” and what is not? • Is there any specification (and what are they) for writing data inside the ROD fragment? • How does the “hardware” specify the ROD event fragments? • How was it done for the TB data? • How was it done for the cosmic data? • Who did take care of providing the “hw” specs to the MROD emulator? • Which one is the right way to do it? • TB? Cosmic? Both of them? None of them? • What are the requirements for ATLAS? • What is the MROD emulator supposed to do ?

  11. Open Questions - Offline • Who provided the specifications or the documentation for data reading and conversion in Athena ? • Where are they documented? • What is the format expected for the data in the ROD fragment? • TB like? Cosmic data like? Both of them? None of them? • Map of the electronics • Geometry database (MuonGeoModel & NOVA)

More Related