1 / 20

Monolith

Monolith. Patrick Toale Dan Wharton March 20, 2005. What is this Mysterious Monolith?. 95% DAQ + 5% Hack Consumes TestDAQ Hit data and produces Events Configurable Triggers Event building based on extended times Events contain both InIce and IceTop. Outline. Monolith: Design

cid
Download Presentation

Monolith

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. Monolith Patrick Toale Dan Wharton March 20, 2005

  2. What is this Mysterious Monolith? • 95% DAQ + 5% Hack • Consumes TestDAQ Hit data and produces Events • Configurable Triggers • Event building based on extended times • Events contain both InIce and IceTop Berkeley Collaboration Meeting

  3. Outline • Monolith: • Design • Configuration - Version 2 • Monitoring • InIce Trigger: • Trigger Framework • Existing Triggers Berkeley Collaboration Meeting

  4. Monolith Design • Turn TestDAQ hit data into time-ordered Hit payloads • Buffer all Hits for Event Building • Pass selected Hits to Trigger (InIce/IceTop) • Must be configurable Berkeley Collaboration Meeting

  5. Run Configurations • Local Coincidence: • All DOMs in LC • Triggers: Multiplicity, Minimum Bias • Dark Noise: • No DOMs in LC • Triggers: Minimum Bias • Flasher: • 1 DOM: FB enabled/HV disabled • Triggers: Calibration Berkeley Collaboration Meeting

  6. Default Triggers • Multiplicity: • 8 (10) Hits in 2 s • Event Window: 2 (8) s into Future, 8 (2) s into Past • Minimum Bias: • Every 10,000 Hit • Event Window: 8 s in both directions • Calibration: • Flasher Board Hits • Event Window: 2 s in both directions Berkeley Collaboration Meeting

  7. Monitoring Monolith • Added histogramming to Monolith via JAIDA • Can monitor: • Input Hit stream • Trigger performance • Trigger Output • Event characteristics • All plots from Run 1413 on 3/15 - Local Coincidence Berkeley Collaboration Meeting

  8. Run 1413: DOM Occupancy Berkeley Collaboration Meeting

  9. Run 1413: Hit Rate (kinda) Berkeley Collaboration Meeting

  10. Run 1413: InIce Multiplicity TriggerN=8 T=2 s Berkeley Collaboration Meeting

  11. Run 1413: InIce SMT Rate 6.5 Hz Berkeley Collaboration Meeting

  12. Run 1413: IceTop Multiplicity TriggerN=10 T=2 s Berkeley Collaboration Meeting

  13. Run 1413: IceTop SMT Rate 0.75 Hz Berkeley Collaboration Meeting

  14. Run 1413: Event Rates 7.3 Hz 6.5 kB < 50 kB/s Berkeley Collaboration Meeting

  15. Run 1413: Time - Depth Correlation Berkeley Collaboration Meeting

  16. Run 1413: Time - Depth Correlation (II) 0.31 m/ns Berkeley Collaboration Meeting

  17. Run 552: Flasher Run ~ 350 Hz ~ 40 Hz Berkeley Collaboration Meeting

  18. Run 552: Number of Hits in Flasher Events Berkeley Collaboration Meeting

  19. Run 552: Flasher Delay? Berkeley Collaboration Meeting

  20. Conclusions • Monolith works • Now testing InIce/IceTop simultaneous triggers • We have a working framework for testing/developing triggers • We need to monitor our system Berkeley Collaboration Meeting

More Related