1 / 4

“Computing requests for Dry/Technical Runs”

“Computing requests for Dry/Technical Runs”. Gianluca Lamanna (CERN) 23.05.2012 Computing WG. Overview of 2012 runs TDAQ hardware. Bandwidth and space for 2012. The LKr is the main data source

liona
Download Presentation

“Computing requests for Dry/Technical Runs”

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. “Computing requests for Dry/Technical Runs” GianlucaLamanna (CERN) 23.05.2012 Computing WG

  2. Overview of 2012 runs TDAQ hardware

  3. Bandwidth and space for 2012 • The LKr is the main data source • The maximum readout rate, for the LKr, is 10 kHz. In case of higher rates the LKr readout will be downscaled, but still it dominates. • 5000 cells x 8 samples x 12 b = 480 kb/event  600 MB/s (@10 kHz) • Duty cycle factor 0.25  125 MB/s (w/o zero suppression) • Assuming 3 weeks of data taking  order of 100 TB disk space required

  4. Other stuffs… • CDR • the 10 Gb/s fiber will be not ready for the dry run, still isn’t clear if the 1 Gb/s is still available. • 2 missed pieces: from PC room to starpoint, from 918 to the previous building. Probably will be ready for TR (Collignon is worrying of that). • One person should be identified to follow the software (learn scripts) part • Buffer: for the TR we need 50h of buffer (disk server mounted in NFS for this year, increase the quantity of disk in the readout PC,…) • Reconstruction and event display: • something is ready in the NA62 framework, but some pieces of decoding and digitization is missing

More Related