1 / 11

Preparation of the Trigger Menu: status of tests, wish-list for the December run

Preparation of the Trigger Menu: status of tests, wish-list for the December run. Federico Antinori System Run Coordinators’ Meeting 28 Nov 2007. Before the run …. In conjunction with DAQ tests: test triggers : ACORDE pulser random measure read-out times possibly vs size.

betty_james
Télécharger la présentation

Preparation of the Trigger Menu: status of tests, wish-list for the December run

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. Preparation of the Trigger Menu: status of tests,wish-list for the December run Federico Antinori System Run Coordinators’ Meeting 28 Nov 2007

  2. Before the run … • In conjunction with DAQ tests: • test triggers: • ACORDE • pulser • random • measure read-out times • possibly vs size FA - System Run Coordinators' Meeting - 28 November 2007

  3. Status: triggers (i) • ACORDE • hardware • so far, 40 modules operational (out of 60) • read-out • bit pattern only (no ADC) • currently not operational • trigger • triggers are generated • rate: 50 – 70 s-1 (with 40 modules) • Arturo & C currently re-checking the plateaus • during the weekend they plan to: • finish re-checking plateaus • include all modules • fix the readout • online software not available yet FA - System Run Coordinators' Meeting - 28 November 2007

  4. Status: triggers (ii) • pulser • “downscaled bunch-crossing” • tried extensively 100 Hz to 40 MHz, OK • random • quick test, seems OK • more extensive tests require s/w tools • distribution of intervals • autocorrelation FA - System Run Coordinators' Meeting - 28 November 2007

  5. Status: triggers (iii) • Additional points: • past-future protection not tested at Point2 yet • s/w tools need to be improved, e.g.: • access to trigger rates when run not active • change of pulser, random trigger frequency needs expert • ratios, such as (L0 DTbar / L0) • distribution of time intervals between triggers • unpractical time units used for busy (400 µs) • … FA - System Run Coordinators' Meeting - 28 November 2007

  6. Status: read-out times (i) • SPD • tests without front-end (front-end behaviour simulated) • equivalent to 3 % occupancy: ~ 320 µs/ev • equivalent empty: ~ 300 µs/ev • was working fine before, but we could not start the run during the last session of tests • SDD • r/o time dominated by read-out of analog memories • ~ 1020 µs/ev @ 20 Msamples per second • SSD • tests with noise: a few ms/ev (probably dominated by DDL bandwidth) • test with full suppression (empty evts, only headers): ~ 160 µs/ev • limit from baseline restoration? FA - System Run Coordinators' Meeting - 28 November 2007

  7. Status: read-out times (ii) • HMPID • partial control on event size (noise) • 1.44 ms/ev • expected for low mult. evts: ~ 300 µs/ev • TOF • no test with a full LDC possible yet • behaviour not completely understood: • often, cannot start run • read-out time very short (~ 30 µs/ev, they expect more) • at high trigger rate (beyond saturation of event rate), busy asserted for ~ 1/3 events only • at higher rates still, stops working • Muon TRK, Muon TRG could not be tested FA - System Run Coordinators' Meeting - 28 November 2007

  8. Pre-run trigger and r/o tests: still to be done • Trigger • random triggers (autocorrelation) • past-future protection • ACORDE: rate • Read-out • ACORDE • HMPID with low multiplicity events • TRD • Muon TRG, Muon TRK • Next session on Monday 3 (last chance…) FA - System Run Coordinators' Meeting - 28 November 2007

  9. Wish-list for Run (i) • trigger and read-out tests • complete pre-run program, if needed • (quick re-check of individual detectors) • TPC read-out time • not yet fully compliant with DAQ protocols; busy box? • if busy box not available, TPC intend to implement temporary solution adjusting dead time by hand • discussing with Luciano alternative way to measure dead-time • expected: • ~ 1 ms/ev w/o sparsification • ~ 300 µs/ev w/ sparsification • TRD read-out time • according to trigger questionnaire: 5 ms / ev (!) • FMD, V0, T0 read-out time FA - System Run Coordinators' Meeting - 28 November 2007

  10. Wish-list for Run (ii) • measure global performances • as many detectors as possible in partition • in particular TPC, i.e. eliminate event alignment checks (for these tests) • realistic (pp) rates, event sizes • one cluster, one trigger • one cluster, multiple triggers • multiple clusters, one trigger • multiple clusters, multiple triggers • watermarks • trigger signals from detectors • test signals from V0, SPD, TOF FA - System Run Coordinators' Meeting - 28 November 2007

  11. How to plan this? • Trigger Development Sessions • reminder: Trigger Development Sessions foreseen during normal running for: • triggers in Development Phase • measurement of event rates, event sizes, dead times • fine tune trigger settings • trigger implementation • prepare settings for test and production triggers • cross-checks, special settings • any necessary checks, complementary data for production triggers • Start TDSessions during December run • duration ~ 5 hours / session • how many? critically dependent on performance… • a first estimate, assuming things go well: • 3 sessions for read-out time measurements • 3 sessions for global performance measurements • 1 session dedicated to tests of trigger signals FA - System Run Coordinators' Meeting - 28 November 2007

More Related