1 / 30

 Project Overview & Goals for the summer

This overview provides a brief history and goals for the Pulsar project in the Blackhole room at Fermilab. It discusses system configuration, performance gains, and possible improvements for the summer.

sharondag
Download Presentation

 Project Overview & Goals for the summer

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. Pulsar in Blackhole  Project Overview & Goals for the summer Ted Liu, March 12, 2004 Fermilab, High Rise Blackhole room

  2. Brief history of time … • Last Jan 30th, we had our first meeting here at Blackhole • Back then, people on CDF only knew that Pulsar is something • made in Heaven (Pulsar is now known as a “down-to-earth” project) • Since then, lots have been changed (though not this Blackhole room) • Back then, I had to make plans as most young people were new • This time, young subsystem experts make their own plans • I will only make some general comments Pulsar in Blackhole

  3. No simulation results to guide Pulsar configuration Phase I: System configuration for commissioning Phase II: Issues with 4 PC configuration Overall firmware status General issues with signal splitting Other issues Goals for the summer Pulsar in Blackhole

  4. Phase I: Configuration with single PC Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC L2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT Electron ShowMax (RECES) • L1 trigger bits  muon • PreFred bits  Cluster • Reces: use only 3 Pulsars • Deliver SVT data separately • SVT/L2toTS can be in one Pulsar Merger Pulsar in Blackhole

  5. Phase I: Performance gain for L2 Mostly from fast CPU and SVT on separate path L2 latency (us) ~50 25 3 Run IIa SVX setup digitize SVT processing Long tails load in alpha …… others process&load unpack/algo/TS RunIIb Unpack/algo starts without waiting for SVT others proc& load no SVT info is needed unpack/algo/TS … unpack/algo wait SVT algo/TS SVT info needed Pulsar in Blackhole New L2 latency

  6. From Kristian I - Faster&faster CPU II - “hide” algorithm time for non-SVT triggers behind SVT processing time 1.4GHz Linux PC 500MHz Alpha Long tail After Pulsar Road Warrior & AM++ Current 4/5 From Alex Old 4/4 Pulsar in Blackhole

  7. Other possible improvements • Push algorithm upstream into Pulsar firmware •  track Pt sorting (study by Kristian/Peter) •  track muon matching (needs study) •  track electron matching (needs study) •  …etc • Algorithm code optimization (started by Kristian/Peter) • Aim at L1A ~ 40KHz capacity @ low luminosity • Long tail events should be reduced this way. However, •  tail events tend to increase with luminosity… •  SVT will still have long tails … •  may still need to use 4 PCs with phase II configuration • Try to maintain ~ 40KHz @ high luminosity Pulsar in Blackhole

  8. Phase II: Four CPU System configuration Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon SLINKPCI PCISLINK Merger PC 0 0/3 1/2 PC 3 Cluster SLINK L2 CAL (CLIST/Iso) PreFred PC 1 Merger 0/3 1/2 PC 2 TS Electron ShowMax (RECES) 0 1 2 3 T2toTS 0 1 2 3 SVT To CPU Merger 0/3 1/2 Pulsar in Blackhole

  9. From Phase I to II: the easy part • Pre-processors send two SLINK output on AUX card •  buffer 0&3 and buffer 1&2 • Two Pulsar mergers needed •  each sends two SLINK outputs • based on buffer number •  minor DAQ/monitor code adjustment • SVT Pulsar now sends out four SLINK output on front panel •  hardware change: add 4 SLINK mezzanine cards •  firmware change: minor (all FPGAs see SVT data) • L2toTS Pulsar needs to send L2 decision to TS in L1A order •  hardware change: add 3 SLINK mezzanine cards •  firmware change: minor for L2D in L1A order Pulsar in Blackhole

  10. From Phase I to II: the harder part • Phase I: very similar to the alpha case (easy for commissioning) •  this will be different in Phase II • L1 scalers can be done in Pulsar firmware upstream • Prescale/L2 scalers could be done in L2toTS •  need careful thinking •  may split the tasks between CPU and L2toTS • Major change in software and L2toTS firmware expected • Make sure Phase I is compatible with Phase II Pulsar in Blackhole

  11. Possible firmware solution (in L2toTS) Non- SVT CPU 0 L2D handled in L1A order SVT L2 D Prescale/rate limit triggers CPU 1 HS with TS CPU 2 CPU 3 L2 scalers L2 scalers Pulsar in Blackhole Each CPU makes raw decision only and sends to L2toTS

  12. Overall firmware status: Muon Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT Electron • Input/output DAQ, algorithm all tested in the beam (RunIIa) • Missing S-Link formatter, being implemented now ShowMax (RECES) Merger Pulsar in Blackhole

  13. Overall firmware status: Reces Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT Electron ShowMax (RECES) • Input DAQ working in • standalone mode since Oct.03 • waiting for L2 torture test • & beam test Merger Pulsar in Blackhole

  14. Overall firmware status: Cluster Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT Electron • Input DAQ testing on-going • Clist algorithm code written • Vadim has been working on • cluster Rx firmware ShowMax (RECES) Merger Pulsar in Blackhole

  15. Overall firmware status: Merger Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT Electron • S-Link formatter working • 1st version of Merger firmware • fully tested in standalone mode • DataIO the same for L2toTS • Control the same for cluster ShowMax (RECES) Merger Pulsar in Blackhole

  16. Overall firmware status: SVT Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT • Only Control FPGA is needed • Firmware written and simulated • Ready to be tested (limited • by # of Pulsars) Electron ShowMax (RECES) Merger Pulsar in Blackhole

  17. Overall firmware status: L2toTS Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT • 1st version of L2toTS • implemented and tested • in standalone mode with TS • and L1T, can deliver sparky • triggers in teststand room Electron ShowMax (RECES) Merger Pulsar in Blackhole

  18. Overall firmware status: In good shape Pulsar pre-processors L1 muon L1 XTRP L1 trigger Muon Merger TS PC T2toTS Cluster SLINK L2 CAL (CLIST/Iso) PreFred SVT SVT Electron ShowMax (RECES) • S-Link formatter being plugged • into muon now • RECES to be done • Cluster to be done • Details in Sakari and Vadim’s talk Merger Pulsar in Blackhole

  19. Problem of the month: fiber splitting • The entire commissioning plan based on the assumption that we can reliably split the input signals into L2 (fiber & LVDS) • Initial attempts to split fiber signals for Isolation/Reces/Muon failed badly (on a few channels). • (Clist already splitted, now with better splitters) • Need to FULLY understand this and find a solution soon • Have to go back to the basics • Use hotlink and Taxi receiver self error detection capabilities at hardware level: receiving violation signal • (hotlink: RVS), Taxi (VLTN)  • quickest and reliable way to catch link errors Pulsar in Blackhole

  20. Test Setup to understand fiber splitting issues Taxi Rx Hotlink Rx Taxi Tx Hotlink Tx Power meter splitters Pulsar in Blackhole

  21. Fiber splitting: Hotlink ~16+-1 dBm ~4dB ~4dB • Txs are very • uniform, output power: • 16 +-1 dBm • Rx can take • ~24dBm without single • error in BIST mode for many hours • At ~26 dBm, error occurs in ~ hour • At ~28 dBm, error occurs in ~10s mins splitter Hotlink ~20dBm ~24dBm RVS To scope On Rx mezzanine cards, will tie the configurable LEDs to each “receiving violation signal(RVS)”. When light blinks  link is weak • Optical components: Agilent HFBR-1119T(Tx) • 2119T (Rx): $55 (1300nm) Conclusion: With one splitter, there is enough safety margin (~ 6 dB) for Hotlink (Muon and Clist) Pulsar in Blackhole

  22. Fiber splitting: Muon • Two channels failed in the beam • test with splitting • Spent one week to find the cause • Now understood • The problem follows the fiber, • not Pulsar receiver. Will talk to • Eric and replace the two “weak” • optical transmitters downstair • Also tested all other channels • with 2 splitters daisy chained, • results agree with lab tests: • error occurs at ~26 dBm input. • Details are described in Pulsar e-log L2D crate Pulsar in Blackhole Muon output

  23. Fiber splitting: Taxi • Txs are not so • uniform, output power • in the range: 14-20 dBm • At ~20 dBm, Rx runs • without problem • At ~23 dBm, error occurs in ~ 1 hour or so • At ~26 dBm, error occurs in ~ few mins (SVX splitters  no good) • At ~28 dBm, error occurs in seconds… ~14-20 dBm ~4dB ~4dB splitter Taxi ~18-24dBm ~22-28dBm VLTN To scope On Rx mezzanine cards, will tie the configurable LEDs to each “receiving violation signal (VLTN)”. When light blinks  link is weak Optical components: Agilent HFBR-1414T(Tx) 2416T (Rx): $ 13 (820 nm) Conclusion I: Money talks, you get what you paid for Conclusion II: not enough safety margin for the weak drivers.… Pulsar in Blackhole

  24. Fiber Splitting: Power meter measurements at the input of RECES cards (done with Masa) West 1 West 2 East 1 East 2 ch 0 15.20 dBm 15.50 15.91 15.56 1 16.94 16.86 17.01 15.47 2 17.74 19.41 17.01 15.73 3 14.67 16.00 16.44 15.47 4 19.15 15.12 17.62 18.35 5 13.22 17.07 18.82 15.52 6 17.45 17.21 16.55 19.30 7 15.33 15.69 19.07 15.68 8 16.42 18.29 17.90 18.66* 9 15.08 14.82 16.15 19.27* 10 17.20 16.53 18.2021.22* 11 17.89 17.20 18.40 19.80X * Already splitted with ~4dB & ok X: this channel was splitted once with ~4dB and failed the test Pulsar in Blackhole Results are consistent with what we learned in the lab

  25. Channels “above threshold” Remove splitter effects & sorted Threshold = 19.0 dBm Replace 5 Threshold = 18.0 dBm Replace 10 Threshold = 17.0 dBm Replace 21 Pulsar in Blackhole

  26. Fiber Splitting: What shall we do with Taxi? • Isolation • According to data sheet, output power gains ~4dB • if we use 100/140um fiber instead of 62.5/125 um fiber. • Use 100/140um fibers and splitters? • Reces • One possibility (suggested by JDL) is to replace the weak • drivers on the ShowMax side… (many optical drivers in hand). • Need to measure light output in the collision hall • Have to discuss this with Karen soon • More test to be done • Find the “threshold” (strong vs weak) • by splitting some more channels in the system Pulsar in Blackhole

  27. L2 LVDS signal splitting: L2 Pulsar fanout board • Design&layout done a while ago, design verification done by Wojtek • Need ~2 days Mircea’s time to send it out • Mircea is busy with TDC at the moment … • Wojtek will take care of the board testing  this is his baby Split: L1 trigger / PreFred SVT/XTRP Clist LVDS L2-TS interface Need this board end of April Pulsar in Blackhole

  28. General issues and concerns • Fiber splitting • Pulsar production schedule • Overall L2 software / interface with trigger database • Long term engineering support Pulsar in Blackhole

  29. Goals for summer • Simple & realistic system configuration for commissioning • Subsystem experts come up with commission plan • Plan should cover March June with • Clear achievable goals for each month • Aim at having each path fully tested with beam in June • Next Pulsar meeting in summer to review where we are • Can we have a working system running in parasitic mode • before shutdown in Fall 2004 ? Pulsar in Blackhole

  30. Pulsar Boys with Toys Missing: Paul/Peter/Fritz/Shawn/Wojtek Firmware factory Pulsar in Blackhole

More Related