Online monitor for L2 CAL upgrade

1. Online monitor for L2 CAL upgrade Giorgio Cortiana • Hardware Monitoring • New Clusters Monitoring Outline: http://www.pd.infn.it/~cortiana/TrigMonOut/TrigMonOut.html

2. Hardware Monitor results: All mezzanine firmware has been recently updated. As a results, the error rate has been further reduced. Error rate is reduced of more than a factor 30! How the monitor looks like: For each run a global pulsar canvas informs about the system status. The code runs online almost every day, and stays inside the PulsarMon package

3. From this information we can easily find out the location and the kind of error from log files: In this case the error is limited to Pulsar 12 and due to ADMEM-DCAS mismatches.

4. Hardware Monitor: results from online running over the week end: Follows a summary report of the online monitor during last week-end. All this is after the mezzanine firmware upgrade: Analyzed runs: 243711, 243712, 243713, 243715, 243730, 243732 Plots and tables will refer to all this runs…

6. Run 243730: Event 19,751,876 phi, eta = (20,20), (20,22), (20,23) ADMEM-DCAS mismatch

7. Hardware Monitor: results from online running over the week end: Analyzed runs: 243711, 243712, 243713, 243715, 243730, 243732 DCAS connector tower phi,eta = 4,0

8. Hardware Monitor: results from online running over the week end: Analyzed runs: 243711, 243712, 243713, 243715, 243730, 243732 DCAS connector tower phi,eta = 4,0 Problem solved by Changing the connection cable DCAS X Pulsar ADMEM-Pulsars OK ADMEM-DCAS BAD ADMEM

9. Hardware Monitor: results from online running over the week end: Analyzed runs: 243711, 243712, 243713, 243715, 243730, 243732 DCAS connectors tower phi,eta = 4,0 ADMEM-DCAS mis-matches

10. Hardware Monitor: results from online running over the week end: Analyzed runs: 243711, 243712, 243713, 243715, 243730, 243732 DCAS connectors tower phi,eta = 4,0 DCAS Pulsar X ADMEM-DCAS mis-matches ADMEM ADMEM-Pulsars BAD ADMEM-DCAS BAD

11. Hardware Monitor: results from online running over the week end: Analyzed runs: 243711, 243712, 243713, 243715, 243730, 243732 DCAS connectors tower phi,eta = 4,0 Control DAQ buffer problem From run 243715, 243730, 243732 Replaced problematic board. ADMEM-DCAS mis-matches

12. Hardware Monitor: current results All hardware problems found during the week end are now solved as demonstrated by the preliminary online monitor results on the current run 243787

13. Clustering algorithm monitor: • We have all the tools to do a massive debugging of the new clustering algorithm. • Follows some plots produced on runs • 243715 (which has a large number of ADMEM-DCAS mismatches), • 243787 (from this night) • for these runs the TL2D bank contains new clusters information. • All the code is ready for online running, • and stays inside the L2GlobalTrigger package. • What we do is essentially to create a simTL2D bank based on DCAS bank and to run the “same” algorithm as the L2CPU. • Up to now, we have a qualitative agreement between simulation and data. We are investigating the sources of the discrepancies.

14. Clustering algorithm monitor: Pass2 run 243715: Real N pass2 Sim N of pass2 clusters Real met X Real met Y Sim met Y Sim met X

15. Clustering algorithm monitor: Pass2 run 243715: The large discrepancies on Npass2, metx and mety are related to ADMEM-DCAS mismatches. Real N pass2 Sim N of pass2 clusters Real met X Real met Y Sim met Y Sim met X

16. Clustering algorithm monitor: Pass2 run 243787: Real N pass2 Sim N of pass2 clusters Real met X Real met Y Sim met Y Sim met X

17. Clustering algorithm monitor: Pass2 run 243787: In this case, there are no ADMEM-DCAS mismatches: There is a qualitative match in the Npass2, but a perfect agreement in metx and mety Real N pass2 Sim N of pass2 clusters Real met X Real met Y Sim met Y Sim met X

18. Clustering algorithm monitor: Pass2 run 243787: In this case, there are no ADMEM-DCAS mismatches: There is a qualitative match in the Npass2, but a perfect agreement in metx and mety Real N pass2 Sim N of pass2 clusters Real met X Real met Y The cluster monitor can track upstream problems and returns consistent results with respect to the hardware monitor Sim met Y Sim met X

19. Clustering algorithm monitor: Pass2 run 243787 Real SeedEta Real Had Real Em Sim Em Sim Had Sim SeedEta Pass2 cluster variables: There is a qualitative match between data and simulation. disagreements probably due to outdated LUTs in the simulation. … investigating. Real SeedPhi Real NTowers Sim SeedPhi Sim NTowers

20. We have all the tools to validate the complete system. The hardware is really stable and with the new mezzanine firmware the error rate is of O(10-6) We have all the methods to debug the information provided by the new clustering algorithm, based on the comparison between real data and the simulation. We are debugging the simulation code, and we expect to finalize it in few days or so. We are ready to start the integration of our monitoring with the default TrigMon in control room. We will start next week. Conclusions and plans

21. - Backup -

22. Inputs for the simulation code We use ADMEM (calorimeter banks) information to compute trigger Tower information. This info are then used to create a simulated Pulsar bank (TP2D) to be used to check the data:

23. Hardware setup M5 used for timing studies. It receive the same data sent to L2CPU Full path up to the CPU is monitored!

24. cable 0 cable 1 Pulsar Board 0 DAQ buffer 1 M0 DAQ buffer 2 cable 3 cable 2 DATAIO 1 L2 CAL system overview Mezzanine M1 CONTROL Mezzanine M2 DATAIO 2 Mezzanine M3 For each LVDS pulsar, All DAQ buffers are monitored Comparing real data to simulation

25. Clustering algorithm monitor: Pass4 N pass4 clusters Em pass4 Iso pass4 Phi pass4 Eta pass4 NTowers pass4