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

2. Last checks performed Assumption on the time walk speed Propose of a change in the clusterization algorithm (to do the same as in the previous analyzer) Time Over Threshold information removed from the Tree (it is available in another file devoted to debug or development)  output: SCHO-XX-DD-MM-YYYY_dst.root  output (dbg): SCHO-XX-DD-MM-YYYY.root EEE Analysis Meeting - 28/09/20152

3. Comparison (Time walk=15.8 cm/ns) EEE Analysis Meeting - 28/09/20153 Calibration file from old analyzer 10 ns to cover all the strip length Time difference depend on the clusterization algorithm (See next slides)

4. Comparison (Time walk=9.56 cm/ns) EEE Analysis Meeting - 28/09/20154 Calibration recomputed as in the old analyzer Suggested by Maria Paola The assumption on the time walk is now different in the new analyzer (this leads to an unconsistency with the old analyzer) What is the correct value?

5. The value in the old analyzer looks the one consistent with a length of 158 cm EEE Analysis Meeting - 28/09/20155

6. Comparison between old and new analyzer EEE Analysis Meeting - 28/09/20156 Time_1: 262303531 s 65870190 ns (ntrack = 1) Time_2: 262303531 s 65870190 ns v1) hits: 1 1 1 v2) hits: 1 1 1 v1) clusters: 1 1 1 v2) clusters: 1 1 1 ChiSquare = 1.943134 vs 1.944100 v1) -0.084749 0.034636 0.995800 (local coordinates) v1) -0.076106 -0.050891 0.995800 (global coordinates) v2) -0.076091 -0.050869 0.995802 (global coordinates) Scalar product v1,v2 = 1.000000 1 bottom XY: 18.038286 35.200001 2 bottom XY: 18.036501 35.200001 1 middle XY: 12.359179 35.200001 2 middle XY: 12.357100 35.200001 1 top XY: 10.208530 38.400002 (12.000000) 2 top XY: 10.209300 38.400002 (12.000000) check local coordinates --> -7.829756 : 3.200001 = -0.084749 : 0.034636 (- 2.446798 = -2.446801) Time of Flight: 1) 3.500000 2) 3.500000 DeltaTime: 1) 0.013810 2) 0.013810 TimeBot: 1) 419.250000 2) 419.250000 TimeMid: 1) 424.049988 2) 424.049988 TimeTop: 1) 415.750000 2) 415.750000 Beta: 1) 0.880495 2) 0.880493

7. Time correlation in a cluster EEE Analysis Meeting - 28/09/20157 2 ns looks a reasonable cut. What time? The faster one? What if  t > 2 ns? In the old analyzer we took the always the faster one.

8. Check EEE Analysis Meeting - 28/09/20158 Time_1: 262303583 s 727057221 ns (ntrack = 1) Time_2: 262303583 s 727057209 ns v1) hits: 2 1 2 v2) hits: 1 1 1 v1) clusters: 2 1 2 v2) clusters: 1 1 1 ChiSquare = 0.171081 vs 5.488390 v1) -0.259937 0.299775 0.917915 (global coordinates) v2) -0.259923 0.299795 0.917913 (global coordinates) Scalar product v1,v2 = 1.000000 1 bottom XY: 78.868141 25.600000 2 bottom XY: 72.546501 27.200001 1 middle XY: 84.248993 44.799999 2 middle XY: 84.246902 44.799999 1 top XY: 89.208534 64.000000 (20.000000) 2 top XY: 82.889397 65.599998 (20.500000) TimeBot: 1) 453.799988 2) 436.600006 TimeMid: 1) 422.400024 2) 422.399994 TimeTop: 1) 439.750000 2) 432.850006 Beta: 1) 0.237951 2) 0.891531 Print cluster info BOTTOM hits 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MIDDLE hits 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 TOP hits 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 BOTTOM times (only the first one) 0.0 0.0 0.0 0.0 0.0 0.0 0.0 453.6 436.8 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 454.0 436.4 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 MIDDLE times (only the first one) 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 422.2 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 422.6 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 TOP times (only the first one) 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 439.1 432.6 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 440.4 433.1 0.0 0.0

9. Backup (old material) EEE Analysis Meeting - 28/09/20159

10. 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 - 28/09/201510

11. 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 - 28/09/201511

12. 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 - 28/09/201512

13. 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 - 28/09/201513

14. 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 - 28/09/201514

15. 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 - 28/09/201515

16. Tracker Step 1 6 hits  5 clusters in this example Before clusterization EEE Analysis Meeting - 28/09/201516

17. Tracker Step 1 6 hits  5 clusters in this example After clusterization EEE Analysis Meeting - 28/09/201517

18. 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 - 28/09/201518

19. Tracker Step 3 Tracks are  2 -ordered   2 1 <  2 2 1° candidate 2° candidate EEE Analysis Meeting - 28/09/201519

20. 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 20EEE Analysis Meeting - 28/09/2015

21. 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 - 28/09/201521 as before

22. 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 - 28/09/201522