1 / 10

Linear Collider DAQ

Linear Collider DAQ. JJRussell. High Level Issues. Duty Cycle Warm vs Cold Machine To Trigger or not to Trigger Not just a DAQ question Buildability Testability Social Aspects. Duty Cycle. Each machine presents different challenges Warm Machine

hesper
Download Presentation

Linear Collider DAQ

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. Linear Collider DAQ JJRussell NLC - Victoria

  2. High Level Issues • Duty Cycle • Warm vs Cold Machine • To Trigger or not to Trigger • Not just a DAQ question • Buildability • Testability • Social Aspects NLC - Victoria

  3. Duty Cycle • Each machine presents different challenges • Warm Machine • @ 1.4 nsecs bunch separation, more of a front-end problem • Cold Machine • 2820 bunches mean larger buffers than the 192 of a warm machine • Both machines are in tune with a acquisition phase during the spill and a between spill analysis phase • At this stage of thinking, these are details • Talk about bigger issues.. NLC - Victoria

  4. Triggering • Not just a DAQ readout issue • Carries through • Detectors • Can they run at the accelerator’s duty cycle? • Readout Electronics • Is heat an issue? • What about the bandwidth off the front-ends to data collection points? NLC - Victoria

  5. Triggering, continued • Once you’ve made the decision not to trigger, there is likely no turning back • It is a contract everyone must keep • Trigger signals are often used as online feedback to monitor accelerator performance • Heavily buffered acquisition systems flies in the face of this usage NLC - Victoria

  6. Triggering, continued • What about long-lived objects? • Long-lived is defined as the decay does not occur within the beam crossing’s normal acquisition cycle. • If this is a requirement, it drastically changes the DAQ approach. NLC - Victoria

  7. Buildability • One must not only produce a system that satisfies the goals of a running experiment • There must a path to go from nothing to that final goal • Testability • Subsystems will always want pieces of the DAQ to test with • Means portions of the DAQ must be delivered far in advance • Always a strain on the software • Usually want more flexibility and features during testing phase • Be wary of transition solutions, both in hardware and software • Leads to building a parallel acquisition system NLC - Victoria

  8. Buildability, continued • Some of the pitfalls • Large centralized pieces, which look good in the finished piece are • Schedule killers - usually complex • Cost killers - everyone wants one, but they are generally expensive • Monolothic DAQ systems • Once assembled, still wish to preserve the ability to run the components separately. NLC - Victoria

  9. Buildability, continued • Some ‘solutions’ • Avoid big centralized pieces • Provide enough interconnections to be able to separate diverse traffic • Make sure the final system is partitionable NLC - Victoria

  10. Social Issues • With the number of people and institutions, this is bound to be a problem. • It is the usual thing • Conflicting ideas • Conflicting schedules • Differing priorities • These issues are just as tough as the technical stuff, and not nearly as much fun NLC - Victoria

More Related