1 / 41

GMT Status and Plans

GMT Status and Plans. Recent progress Logic design completed Functionality improved added provision for Beam Halo Trigger during normal operation Performance in barrel/endcap overlap region improved  DT/CSC cancel-out unit conversion unit for f foreseen Documentation

guyp
Download Presentation

GMT Status and Plans

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. GMT Status and Plans • Recent progress • Logic design completed • Functionality improved • added provision for Beam Halo Trigger during normal operation • Performance in barrel/endcap overlap region improved  DT/CSC cancel-out unit • conversion unit for f foreseen • Documentation • CMS Note 2002/024: H.Sakulin, “A Robust Solution to the Ghosting Problems of the CMS Level-1 Muon Trigger in the Barrel/Endcap Overlap Region” • Logic design document & drawings • Thesis H. Sakulin ready this week • Plans for 2002/2003 • continue VHDL simulation of FPGA chips • VHDL simulation of GMT board • Synthesis / design of FPGAs

  2. Global Muon Trigger Board

  3. GMT Logic FPGA

  4. old solution: cancel-out at DT and CSC track finder level confirmation by RPC in Global Muon Trigger maximum over-all efficiency is limited to the one of the RPC new solution: duplication allowed at track finder level DT/CSC cancel-out unit in GMT ghosts are reduced independent of RPC more robust some (tolerable) ghosting remains DT/CSC cancel-out unit

  5. Single muon trigger efficiency vs h |h| < 2.1 ORCA_6_2_2 (*)efficiency to find muon of any pT in flat pT sample

  6. L1 single muon trigger rates

  7. L1 single & di-muon trigger rates Trigger rates in kHz |h| < 2.1 18, 8;8eW =84.9 %eZ =99.7 %eBsmm = 7.2 % 20, 5;5eW =82.3 %eZ =99.7 %eBsmm =15.1 % 14, -;-eW =89.6 %eZ =99.8 %eBsmm =27.1 % 25, 4;4eW =74.2 %eZ =99.5 %eBsmm =18.4 % working points compatible with current L1 pT binning L = 1034cm-2s-1 L = 2x1033cm-2s-1

  8. Bs -> mm: Example of Topological Trigger Topological conditions: Dh < 1.5, D < 2 rad, opposite muon charges Gain by topological conditions and requiring no threshold on second muon with respect to working point 20 GeV; 5 GeV, 5 GeV: 1 kHz rate, 7.8%efficiency (15.1% without, 22.9% with topological conditions).

  9. Df between Muon System and Vertex • Hardware change: f-conversion unit is now foreseen

  10. Bs -> mm: Example of Topological Trigger Generated m m at GMT MB/WZ Bs -> mm

  11. GMT Milestones • Milestone Dec. 2001:Logic design done -> Done • Milestone Dec. 2002:FPGA design done -> Delayed to Dec. 2003 • Milestone Dec. 2003:VME board production done -> Delayed to June 2004 • Milestone June 2004:VME board tested (GMT ready) -> Delayed to Oct. 2004 • Milestone Jan. 2005:GMT integration tests done -> Planned on time

  12. Global Trigger Boards PSB (Pipeline Synchronizing Buffer) Input synchronization (7 boards including GMT) GTL (Global Trigger Logic) Logic calculation (1-2 boards) FDL (Final Decision Logic) L1A decision (1 board) TCS (Trigger Control System Modeule) Central Trigger Control (1 board) L1A (Level-1 Accept Module) Delivery of L1A (1 board) TIM (Timing Board) Timing (1 board) GTFE (Global Trigger Frontend) Readout (1 board)

  13. Layout of Global Trigger 9U Crate

  14. Global Trigger Rack

  15. Global Trigger Logic Prototype Board GTL-6U Automatic chip design and setup procedure developed. Layout for a 20 channel GTL (4 , 4 isol. e/, 4 central jets, 4 fwd jets, SET, ETmiss, 8 jet multiplicities; other quadruplets can be connected alternatively for tests) has been finished and the board has been received end of October! Algo chips Condition chips

  16. GTL-6U Prototype Schematics Design simplified, board tested by June 2003

  17. New: HT Global Trigger Logic Board GTL-9U A redefinition of jet input groups has been done. The present best 4 central jets, 4 forward jets and 4 t-jets are kept. A new quantity HT giving the transverse energy sum of all good jets above threshold and 4 jet multiplicities have been added. The exact definition of how to calculate the jet multiplicities (h-range, thresholds) still has to be taken at the level of the calorimeter trigger.

  18. GT Conversion Board A conversion board to be used later in final 9U-crate with GTL-6U prototype is ready. It contains also memories in FPGA’s to send simulated test data to the GTL-6U board.

  19. Final Decision Logic FDL-9U FPGA design has started. Board available by June 2003. • Monitoring of all algorithm and L1A bits • Prescaling of all algorithms • Trigger Mask • 8 L1A’s in parallel for partition modes • Input of up to 64 technical trigger bits from PSB possible

  20. FDL-9U

  21. Timing Board TIM-6U • TIM-6U The board contains a TTCrx chip and provides all timing signals for the GT crate. It will also be used in the Drift Tube Track Finder crates. An FPGA provides all necessary test functions to run the crate without the central TTC clock. It simulates also L1A requests for monitoring or to test the readout chain. The schematic design is finished. After deciding to go ahead as planned with mezzanine TTCrx solution, the layout is now finished. The final Timing Board will be 6U (previously 9U) and is expected for June 2003.

  22. TIM-6U

  23. Central Trigger Control System Board TCS-9U • TCS-9U • Its functions and the input / output cables are defined. Design of schematics and the TCS chip is in progress. The board is expected by April 2003. • Trigger Partitions: The maximum number of subsystems is fixed (32). An agreement about the output to the DAQ Event Manager has been reached. The input format of Fast Signals is fixed. 4 coded bits per subsystem, sent as LVDS parallel data, and RJ45 connectors are proposed. The TCS board provides data for the ”TTCci” (new CMS-TTCvi). A L1A driver module to be used with the TTCci has been conceived.

  24. TCS within Global Trigger New: 8 DAQ partitions (asynchronous TTS)

  25. TCS board schematics VME L1A,BGo...to TTCci Clk,L1A,BC0...to 8 emulators TCS_fastsigs to 8DAQ_part TCS chip Clock PLL TCS monitoring chip

  26. FDL GT event record for Event Manager Subdetector partitions are combined in groups connected to a DAQ partition. Only 1 DAQ partition triggers at a time due to DAQ restrictions. The same trigger type is valid for all members (=subdetector partitions) of this DAQ-partition.*) Begin of event BOR Identifier// Begin of record 32 bits Trigger number Nr of all L1Asent since begin of run (8h with 100kHz =ABA9 5000hex) 32 bits DAQ partition number 3 bits (30..28) , + Trigger Type 4bits (19..16), + Bunch crossing number 12 bits (11..0)32 bits Subdetector partitions // bit nn=1  Subd.-part. nn is connected to this DAQ-partition. 32 bits Event Number // since last ‚Reset Event Counter‘; 28 bits (27-0) **) 32 bits Orbit number // since last ‚Reset Orbit Counter‘; (29 bits=13.5h) **)32 bits GPS time 64 bits Algo bits_0 Physics trigger algorithm bits 0...31 32 bits Algo bits_1 Physics trigger algorithm bits32...63 32 bits Algo bits_2 Physics trigger algorithm bits64...95 32 bits Algo bits_3 Physics trigger algorithm bits96...127 32 bits Algo bits_4 reserved for optional upgrade 32 bits Algo bits_5 reserved for optional upgrade 32 bits Technical trigger bits bits 31...0//also used for external test trigger signals 32 bits End of Event EOR Identifier// End of record 32 bits TCS GTFE *) Therefore TCS does not send a (redundant) dedicated trigger type for each subdetector partition. **) Reset Event/Orbit Counter can be sent at different times to each single DAQ-partition. Data sources in Global Trigger crate: FDL = Final Decision board TCS = Central Trigger Control board

  27. Global Trigger Setup Program Environment Task of GT Setup Program: Configure chips - via VME, JTAG (or from PROM) 2) Load registers, LUTs, memories - via VME Remarks: - For standard datataking, the trigger menu, setup of logic and thresholds from database (e.g. .xml) files, which are converted to HW format by custom or HAL device drivers. - For testing configuration files can also be loaded directly with Altera/Xilinx (e.g. MasterBlaster/ByteBlaster) hardware. - Run Control interfacing to be done. - JTAG programming not yet explored

  28. Setup for GT Logic Configuration VME-MXI-2 Crate Controller VME-MXI-2 GTL-Conversion Card VME-Bus MXI Cable VME Crate Linux PC running XDAQ equipped with PCI-MXI Card Thanks to J. Gutleber for help with XDAQ!

  29. Crate for Global Trigger Tests PSB-6U GTL Conversion Board VME MXI-2 Crate Controller

  30. Global Trigger Milestones • - No milestone changes since spring 2002! • Oct. 2002 (orig. March 2002):System Test -> Delayed to June 2003 • This includes the backplane-6U, the PSB-6U, GTL-6U, FDL-9U and TIM-6U. The GTFE and the GMT are not included. • Oct. 2002:Backplane-9U tested -> Delayed to March 2003 • Oct. 2002 (orig. July 2002):TCS-9U tested -> Delayed to April 2003 • June 2003:GTFE-9U tested -> Delayed to Dec. 2003 • Dec. 2003:20-channel Global Trigger tested -> Delayed to June 2004 • Milestone Dec. 2003:GMT ready -> Delayed to Jun. 2004 • July 2004:12-channel PSB-9U available • Nov. 2004:Complete 32-channel Global Trigger available • Includes GTL-9U module with all input channels(4 , 4 isol. e/, 4 non-isol. e/ , 12 jet channels, HT , SET, ETmiss, jet multiplicities).

  31. Global Trigger Hardware Status Nov. 2002 • Custom Backplane for VME 9U crate • 6U Prototype: Channel Links ...existsMS 3/02* • 9U Backplane: 80MHz GTLp and Channel Links, ...design in progress MS 10/02 03/03 • PSB Input board (synchronisation, monitoring) • 6 channel 6U Prototype: Channel Link receivers... board tested MS 3/02* • 12 channel board: memories inside FPGAs ...conceptual designMS 7/04 • GTL Logic board: • Conversion board for prototype ... board testedMS 3/02* • GTL6U prototype: 20 channels …board producedMS 3/02*  06/03 • 4, 4 isol. e/, 4 central jets, 4 fwd jets, SET, ET miss, 8 nrs_of jets • other quadruplets can be connected alternatively for tests • GTL9U board: 32 channels ...conceptual designMS 11/04 • 4, 4 isol. e/, 4e/, 4 central jets, 4 fwd jets, 4 t-jets, SET, ET miss, HT, 12 nrs_of jets • TIM Timing board... layout doneMS 3/02 06/03 • 6U size, TTCrx, clock and L1A distribution, also used by DTTF • FDL-9U Final Decision board... design in progress MS 3/02 06/03 • TCS-9U Central Trigger Control board... design in progress MS 7/02 04/03 • GTFE-9U Readout board...conceptual design MS 6/03 12/03 *) Milestone (MS) Mar-02: All prototype boards except GTFE+GMT

  32. Progress • GTL-6U board:layout done, board received • GTL Conversion board:produced and tested • Test program written in CVI with GUI • Configuration programimplemented using XDAQ • TIM board:FPGA and board design done, layout done • TCS board: • Final definition of functions and IO-signals done, • Schematic and FPGA design in progress • FDL board: • Final definition of functions and IO-signals done, • Schematic and FPGA design in progress • Definition of requirements for the GT setup program in progress

  33. GT-PROTOTYPE BACK-6U ok PSB-6U ok GTconv ok GTL-6U Milestone 6/03 TIM-6U Chain Test with GCT (mid 2003) Plans for Production and Tests GT GTL-6U  11/02 TIM-6U  12/02 TCS-9U  2/03 GMT FPGA design  12/03 BACK-9U  3/03 FDL-9U  4/03 GTFE  12/03 Installation and commissioning in pit planned in phase with other subsystems (GCT, regional muon trigger systems). PSB-9U  3/04 Board production  6/04 System test of 20-channel GT  06/04 GTL-9U  12/04 GMT system tests 1/05 GMT integration 1/05 GT system tests  6/05 Integration with DAQ 1/06

  34. GT and GMT Manpower • Physicists • A. Taurok (GT/GMT project engineer), C.-E. Wulz (GT coordinator) • H. Sakulin (logic and hardware design of GMT, simulation, on-line software) • J. Strauss (on-line software) • A. Jeitler, N. Neumeister, P. Porth, H. Rohringer (simulation, partly working on other activities) • L. Boldizsár, P. Hidas (GT simulation, about 2 months per year) • Technical staff (shared with DTTF) • H. Bergauer (50%), M. Padrta, K. Kastner - in Vienna • Ch. Deldicque - at CERN • 1 person based in Vienna needed for on-line software • Students • S. Kostner (20%)

  35. Luminosity 2x1033 cm-2s-1 • TRIDAS scenario 50 kHz • 8 physics channels studied (A-H) • A: Smuons at Snowmass point 1a - mLmL with mL -> m • B: Chargino-neutralino at Snowmass point 1a -  • with  -> and  -> ;  -> ;  -> e • C: Gluino-squark at Snowmass point 2 • gg, gq, qq • D: Gluino-squark at Snowmass point 1a • E: WW with W -> mn • F: Sparticles from JetMet mSUGRA4 • G: Sparticles from JetMet mSUGRA5 • H: Sparticles from JetMet mSUGRA6 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ SUSY Trigger Efficiency Studies

  36. Parameter choice Snowmass point 1a Snowmass point 2 tan  = 10

  37. Preliminary efficiencies A-E

  38. Preliminary efficiencies F-H

  39. Conclusions Global Muon Trigger Logic design finished Increased functionality and performance in overlap region FPGA design in progress Global Trigger GTL board received, other boards well advanced Work on software requirements and solutions started SUSY simulation studies performed Trigger Control System • Interfaces to subsystems including Event Manager and partition handling defined

  40. Conclusions • Detailed information about the Global Trigger and the Global Muon Trigger is available on the HEPHY Vienna web sites: • http://wwwhephy.oeaw.ac.at/p3w/cms/trigger/globalTrigger • http://wwwhephy.oeaw.ac.at/p3w/cms/trigger/globalMuonTrigger This talk can be found at: http://wwwhephy.oeaw.ac.at/p3w/cms/trigger/globalTrigger/trans/ wulz_CPTweek_nov2002.ppt

More Related