1 / 4

DAQ Considerations For Increased Rep. Rate

DAQ Considerations For Increased Rep. Rate. J. Leaver 01/12/2009. Target DAQ Considerations. Raw data rates: Potentially 9 channels Beam Intensity, Target Position, Total Beam Loss, Sector 7 Beam Loss, Sector 8 Beam Loss + 4 Beam Position Signals (2 each for Sector 7 Horiz. & Vert.)

gamada
Download Presentation

DAQ Considerations For Increased Rep. Rate

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. DAQ Considerations For Increased Rep. Rate J. Leaver 01/12/2009

  2. Target DAQ Considerations • Raw data rates: • Potentially 9 channels • Beam Intensity, Target Position, Total Beam Loss, Sector 7 Beam Loss, Sector 8 Beam Loss + 4 Beam Position Signals (2 each for Sector 7 Horiz. & Vert.) • 16 bit resolution (may be able to cope with less…) • 5k samples per event • 100 kHz sample rate (may want more…?)  ~ 88 kB per event • Instantaneous data rate: ~8.6 MB/s • For 10 Hz operation, need to read out ~880 kB per second • Trivial… • May need additional buffer memory on custom DAQ board (Stage 3 upgrade) to cope with instantaneous data rate (but this is independent of rep. rate)

  3. Target DAQ Considerations • Maximum event rate with current Target DAQ: • Time to read out an event: ~50 ms • Time to analyse an event: ~4 ms (New ‘integral’ method) • Time to write an event to disk: ~100 ms (Archiving to .gz files) • GUI overheads: ~100 ms • Time to read an event file: ~180 ms • Time for Event Viewer to display an event: ~280 ms  Maximum event rate: ~4 Hz • Target PCs are surprisingly slow (e.g. MICETrackerSoftware package takes 2-3 times longer to compile than on all other control PCs!) • Would need to reduce write time + GUI overheads to < 50 ms for 10 Hz readout – could be possible with a high spec PC • ‘Headless’ DAQ should achieve 10 Hz on a fast PC

  4. MICE DAQ Considerations • Time to transfer a 1000 muon event: 1 s • RF duty factor: 1/1000  To run at 10 Hz, need: • 100 s spills (i.e. efficiency is reduced) • 100 muons per spill • To run at 10 Hz with 1 ms spills, need to worry about RF amplifier cooling • Cooling power, water plant, etc. → potentially expensive!

More Related