190 likes | 311 Views
Where do we stand? Where do we go?. TDAQ Working group meeting Mainz – 8/9/2011. 2 meetings at the price of 1. Sub-detectors TDAQ. Straws to decide on custom readout in Jan 2012. IRC/SAC to be defined. TDCB - I. Status report by B. Angelucci Pre-production done (total 14 boards exist)
E N D
Where do we stand?Where do we go? TDAQ Working group meetingMainz – 8/9/2011
Sub-detectors TDAQ Straws to decide on custom readout in Jan 2012. IRC/SAC to be defined.
TDCB - I Status report by B. Angelucci Pre-production done (total 14 boards exist) Now: basic tests in Pisa Ready for distribution in ~1 week (cables too) Firmware: basic features working, improvements needed.Complete rewrite and simulation would be advisable if manpower were available.
TDCB - II Sub-detector groups should arrange testing (with TELL1s): RICH: validation in Perugia (M. Piccini)LAV: validation in Frascati (M. Raggi) CEDAR: validation in Birmingham (A. Romano)STRAWS (fallback): validation in CERN (A. Sergi)MUV: ?CHANTI: ?SAC/IRC (if used?): ? Expect validation from sub-detectors(sustainable rate, time resolution, noise, etc.) After tests and validation from the sub-detectors: ready for full production. Default: full production in 2013. No more boards to be produced before final production unless decided otherwise(earlier full production is an option)Test setup for large number of boards to be built in Pisa
TELL1s • TELL1s (either bought or on loan) are now available in: • PisaPerugiaRoma Tor VergataBirminghamCERNMainzNapoliLNF • One still available to loan • Lab setup and TDCB tests possible with TELL1s
TEL62 Status report by E. Pedreschi One more prototype PCB can be mounted on short notice IF somebody is willing to get it and make significant tests before the end of the year Produce 10 boards at the end of 2011, to be used in the Dry/Test runs Default: full production in 2013 (Pisa+Roma TV). No more boards to be produced before final production unless decided otherwise Test procedure: in house/at firm ? Roma TV will produce test vectors Complete procurement of all components by early 2012 Recall: fallback solution for straws not included in component procurement
TEL62 firmware • New framework for TEL62 started. Prioritization of tasks to have basic functionality ready for next year’s runs Manpower issues still presentInvolvement of 1 person per sub-detector needed: • RICH: C. Santoni (Perugia)LAV: M. Raggi (Frascati)CEDAR: M. Krivda (Birmingham)LKr: G. Lamanna (CERN)LKr/L0: A. Salamon (Roma TV)CHANTI: ?MUV: M. Hita-Hochgesand (Mainz)SAC/IRC: ? • Dedicated TEL62 firmware working meeting later today.
Autumn sale 1 TEL62: 3500 € 1 TDCB: 1000 € Set of 4 Cables: 500 € Lower prices expected for final production We ship worldwide with very good rates Boards come with working base firmware and nice color manual in electronic format Instruction courses available on subscription Hotline assistance available Pay with TID to NA62 account T145400routing the document to me for information
Your cart All cables are 6m long, except LAV which are 1.5m long
Dry run / test run ~1 month in June-July 2012 Not yet defined what we want/need in terms of readout/trigger This means: from TDAQ point of view test run = dry run (MY) GOLDEN RULEWhatever (TDAQ electronics) is going to be used in the September test run it must be installed and proven to work in the global infrastructure during the dry run
Dry run / test run: minimal goals - O(100) channels/sub-detector readout in coherent events - Full LKr readout- Conventional CHOD L0 trigger distributed via TTC- Full control of start/end spill (triggers) and special triggers- Parasitic L0 trigger primitives in data- TEL62/TDCB: complete readout, no inter-board communication- Data readout to PCs with no software trigger(s) but rough event building- Indipendent sub-detector initialization “by hand” Baseline plan (equipment, goals, priorities) to be drafted by next meeting. Need to start dedicated planning meetings
Crates Two (slightly) different versions of Wiener crates, both compatible with TEL62 (7700 €) One prototype of each available in NA62:Roma Tor Vergata and Frascati Test with TEL62 in 1 month (fake power-consuming firmware required) Assessment with FE electronics? Ordering and schedule? Full software support from CERN expected
Clock – Sub-detector stuff [Update from M. Krivda] LTU (NA62 version of ALICE board, Birmingham): paid for, ready, available, firmware being developed TTCex (new version, CERN):paid for, built, PLL problem found with new version, solution under investigation, no time estimate
Clock – Common stuff Master clock generator:NA48 one available (no spare) FibresLayout finalized, document being finalized, to be bought (common fund), expect installation at beginning of 2012 SplittersNumber defined, collecting offers for common order TTCit monitor board: production starting in September
L0TP - I Current baseline solution: implementation on a PC with a single existing PCIe card (Altera Stratix IV development board by Terasic) with additional NA62-specific daughter cards. To be proven working ! Stratix IV GXPCIe 8x4 GbE on-boardDDR on-boardClock inputs2 connectors for daughter cards One board bought by Pisa, now being tested in Torino.
L0TP- II Torino group (E. Menichetti) joined the effort Current status/plan:- Ferrara to provide the board firmware- Torino to provide additional daughter cards- L0 trigger-matching code (on PC) not yet covered (1) Is this solution viable in terms of L0 latency? (2) L0TP for 2012 run(s): (a) prototype version of PC-based L0TP OR(b) “patched” temporary solution (e.g. Talk board) Assessment of (2) (and (1)?) by fall 2011
Higher-level triggers (1) Proposal @ Computing WG [J. Kunze]:merge all PC farms into a single one to be used both for L1 and L2 (incl. LKr)- L1 during the spill- L2 during the inter-spill (not starting until then)(all event data in memory during the spill) Looks reasonable (no latency issues)more flexible and possibly less expensiveAssessment? What about 2012? (2) No L1 recipe so far to reach 100 kHzDownscaled/control triggers might (= will) easily saturate ANY trigger bandwidth in NA62: bandwidth allocation proposal needed (also true for L0)
Critical/urgent issues • L0TP: demonstrate we have a viable solution • Online software: start, responsibility? • TEL62 firmware: have basics ready for 2012 • TELL1 radiation tests: (Birmingham) • Crates: validate, buy and get • Simulation: L0 for LKr, L1 and L2 • Data transfer layer SW: common, avoid independent developments • Central repository: for documentation, firmware, software • Finalize specifications: e.g. fine time (sub 25-ns) information with each L0 trigger? [GTK, straws]