1. Update on the new reconstruction software F. Noferini E. Fermi center INFN CNAF EEE Analysis Meeting - 14/09/20151

2. Current status for the output format EEE Analysis Meeting - 14/09/20152 OLD ANALYZERNEW ANALYZER Not yet inside Time Over Threshold added It is not clear to me what is the meaning of the Status. I added the id of the GPS event used to compute the time.

3. Gps events stored in a separate tree EEE Analysis Meeting - 14/09/20153

4. Time Over Threshold EEE Analysis Meeting - 14/09/20154 Such variables are not used. However it would be nice to have them to perform some check for future developments. Typical tot distribution Correlation left – right side: the TOF are strongly correlated (it could help to match the two signal) Such information may help us to understand the behavior of the MRPC (tot vs position) also for other applications (ALICE-TOF)

5. The new header EEE Analysis Meeting - 14/09/20155 Available only for new GPS models

6. Some checks (macro committed) EEE Analysis Meeting - 14/09/20156 noferini@noferini-VirtualBox:~/Soft/EEE_Analyzer/eeeroot$ root -b -q -l compare.C root [0] Processing compare.C... n1 = 48316 -- n2 = 50000 Time_1: 265545621 s 11147885 ns (ntrack = 1) Time_2: 265545621 s 11147885 ns v1) -0.274683 -0.180669 0.944409 (local coordinates) v1) -0.003819 -0.328752 0.944409 (global coordinates) v2) -0.015587 -0.352731 0.935595 (global coordinates) Scalar product v1,v2 = 0.999802 ChiSquare = 3.206481 vs 3.408720 1 bottom XY: 99.134689 40.000000 2 bottom XY: 101.207001 40.525002 1 middle XY: 82.360046 28.800001 2 middle XY: 82.823402 28.799999 1 top XY: 72.376282 22.400000 2 top XY: 71.594704 22.400000 check local coordinates --> -26.758408 : -17.600000 = -0.274683 : -0.180669 (1.520364 = 1.520364) Time_1: 265545621 s 27075344 ns (ntrack = 1) Time_2: 265545621 s 27075344 ns v1) 0.349200 -0.386074 0.853818 (local coordinates) v1) 0.515340 0.073610 0.853818 (global coordinates) v2) 0.509380 0.061092 0.858370 (global coordinates) Scalar product v1,v2 = 0.999947 ChiSquare = 46.678795 vs 46.693600 1 bottom XY: 106.639664 76.800003 2 bottom XY: 107.527000 76.800003 1 middle XY: 64.189903 73.599998 2 middle XY: 64.653198 73.599998 1 top XY: 144.266342 35.200001 2 top XY: 143.485001 35.200001 check local coordinates --> 37.626678 : -41.600002 = 0.349200 : -0.386074 (-0.904487 = -0.904489) 1 = NEW 2 = OLD In the new approach GPS events are stored separately, in the old one a GPS event is stored twice In the new approach currently local coordinates Calibration applied in a similar way also in the new analyzer

7. Histo checks EEE Analysis Meeting - 14/09/20157 Both in old calibration scheme SAVO-01

8. Calibration strip by strip (single run) EEE Analysis Meeting - 14/09/20158

9. Histo checks EEE Analysis Meeting - 14/09/20159 New calibrated strip by strip SAVO-01

10. Typical output during a reconstruction 10 BOLO-01 2015-08-27> eeereco.exe -b -d -r -c BOLO-01-2015-08-27-00001.bin run with -h to get the help list batch mode Info in : Calibration step requested (max 50000 events) Info in : default calibration loaded! Info in : BOLO-01) FEA types: 3/3 - 3/3 - 3/3 Info in : cable: BL = 700.000000 -- BR = 700.000000 Info in : cable: ML = 700.000000 -- MR = 700.000000 Info in : cable: TL = 700.000000 -- TR = 700.000000 Info in : Time delay = 1.395000e-06 s Info in : Geometry loaded Info in : Weather station info: Tin=29.000000, Tout=27.200001, P=1012.000000 … Info in : Calibration for single strip written Info in : calibration step performed (run again to get results) Info in : Calibration found! Info in : BOLO-01) FEA types: 3/3 - 3/3 - 3/3 Info in : cable: BL = 700.000000 -- BR = 700.000000 Info in : cable: ML = 700.000000 -- MR = 700.000000 Info in : cable: TL = 700.000000 -- TR = 700.000000 Info in : Time delay = 1.395000e-06 s Info in : Geometry loaded Info in : Weather station info: Tin=29.000000, Tout=27.200001, P=1012.000000 Info in : Number of visible satellites = 14 (gps=1) Info in : Number of visible satellites = 12 (gps=428) Info in : Number of visible satellites = 14 (gps=429) Info in : Number of visible satellites = 12 (gps=434) Info in : Number of visible satellites = 14 (gps=436) Info in : Number of visible satellites = 12 (gps=438) Info in : Number of visible satellites = 14 (gps=444) Info in : Number of visible satellites = 0 (gps=917) Info in : Number of visible satellites = 12 (gps=921) Info in : Number of visible satellites = 14 (gps=922) Info in : Number of visible satellites = 10 (gps=927) Info in : Number of visible satellites = 14 (gps=928) Info in : Number of visible satellites = 12 (gps=973) Info in : Number of visible satellites = 14 (gps=974) Info in : Lat.= 44.500866, Long.= 11.357333, Alt.=38.000000 Calibration step reconstruction Wall time 5.795 s

11. Future devolpments Interface to Corsika root format Interface to our DB … EEE Analysis Meeting - 14/09/201511

12. Backup (old material) EEE Analysis Meeting - 14/09/201512

13. Requirements Linux machine ROOT should be installed (in principle any version is fine) Windows ROOT should be installed (the same version used by us to compile the code because we will provide directly the executables obtained with Visual Studio 10) EEE Analysis Meeting - 14/09/201513

14. Software repository The new code will be available under github in the same repository of the current analyzer. https://github.com/centrofermi/EEE_Analyzer Currently the version under test is in the «dev» branch: Windows executable (under bin dir) EEE Analysis Meeting - 14/09/201514

15. Running under windows 8 The code developed in a linux machine is able to run also on windows (tested with root v5.34.24). The executable will be available in the github repository (compiled with Visual Studio). The only requirement is the root installation (the installer for the proper root version will be provided). Reconstruction can be trigger in windows also as a double click in the.bin file. EEE Analysis Meeting - 14/09/201515

16. The structure Basically the new software is organized in c++ classes to have a more modular structure and to benefit of ROOT functionalities. However the output is written via simple ROOT trees (as in the current version of the Analyzer). The main differences in the output is the fact that the number of tracks per event is not limited. EEE Analysis Meeting - 14/09/201516

17. Event time The event time will be computed in the same way as before (reported in the documentation). The only difference is that now the total TDC counts are computed in the current second and not in the one before. Nanoseconds are extracted from here, f x 10 9, and then corrected for other effects. TDC counts in the two TDCs for the current event TDC counts in the two TDCs in between two GPS events EEE Analysis Meeting - 14/09/201517

18. The Tracker 1.It selects hits in both sides of each chamber and it fills arrays with hit candidates for tracks: strip#[nHit#], deltat#[nHit#], timeAv#[nHit#] where #=,T, M, B (Top, Middle, Bottom chambers). In case two hits are close in space they are clusterized. 2.A pre-selection of candidate tracks is performed applying this cut: a track is interpolated using each top and bottom hits combination opening a window of three strips around the extrapolation in the middle chamber to accept the third hit (in the middle chamber)  this introduces a cut on  2 around 25. 3.All the track candidates passing the pre-selection are then  2 - ordered 4.The final round in the track selection consists in a loop on all the candidates starting from the best  2. The tracks is accepted if its hits were not used from previous (better) tracks. In this way a hit cannot be used to construct more than one track. EEE Analysis Meeting - 14/09/201518

19. Tracker Step 1 6 hits  5 clusters in this example Before clusterization EEE Analysis Meeting - 14/09/201519

20. Tracker Step 1 6 hits  5 clusters in this example After clusterization EEE Analysis Meeting - 14/09/201520

21. Tracker Step 2 All Top-Bottom combinations are explored and if there is a cluster matchable in the middle chamber the triplet becomes a track candidate (2 candidate in the example). EEE Analysis Meeting - 14/09/201521

22. Tracker Step 3 Tracks are  2 -ordered   2 1 <  2 2 1° candidate 2° candidate EEE Analysis Meeting - 14/09/201522

23. Tracker Step 4 The first candidate is accepted and its cluster are exlcuded for the other tracks. Then the next candidate is considered… In this case the 2° candidate is excluded because it looses one of its clusters in previous associations  its remaining clusters are available to form other tracks (no other candidates in this case). 1° track 2° candidate  no track 23EEE Analysis Meeting - 14/09/2015

24. Calibration Calibration is performed in a similar way as before but the possibility to calibrate strip by strip was added (it can help in case one strip has a big noise). EEE Analysis Meeting - 14/09/201524 as before

25. Analysis The way to analysis data will be similar to the previous case (now multi-track info are available). Alternatively the framework will allow to access data in a more elegant way: EEEEventReader reader("TORI-04-2015-03-27-00001.root"); if(reader.Init()) return; EEEHeader *header = reader.GetHeader(); header->GetSchool(); header->GetYear(); // header->… Int_t n = reader.GetEntries(); // number of events EEERecoEvent *event; EEETrack *trk; for(Int_t i=0;i < n;i++){ // loop over the events event = (EEERecoEvent *) reader.GetEvent(i); event->Seconds(); event->NanoSeconds(); Int_t ntrk = event->GetNTracks(); // number of tracks in the event Int_t ngoodtrk = 0; for(Int_t j=0;j < ntrk;j++){ // loop over the tracks trk = event->GetTrack(j); if(trk->Chi2() Phi(); trk->PhiLocal(); } EEE Analysis Meeting - 14/09/201525