Location in CSD of electronic detector reconstructed events

1. Location inCSD of electronic detector reconstructed events Scanning results from LNGS scanning lab N. D’Ambrosio, N. Di Marco, L.S. Esposito, P. Monacelli and all the shifters that have been working since September

2. Event number: 1064775 CSD ID: 3000370 Brick location: W29/RW9/COL12, rock side SX = -0.0839  0.0013 SY = 0.0259  0.0012 PX = 181.54  0.27 cm PY = -288.03  0.25 cm PZ=-401.82 cm with Dario and Antoine

3. Event number : 1848052 CSD ID: 3000456 Brick location: W28/RW8/COL8, rock side SX = -0.0517  0.0098 SY = 0.3456  0.0016 PX = 238.99  1.21 cm PY = -302.33  0.19 cm PZ = -415.22 cm with Dario and Antoine

4. Event number: 2367442 CSD ID: 3000521 Brick location: W29/RW9/COL8, corridor side SX = -0.0072  0.0029 SY = 0.6137  0.0024 PX = -236.23  0.24 cm PY = -287.03  0.20 cm PZ = -401.821 with Dario and Antoine

5. Brick position in OPERA detector The brick position has been calculated using the nominal geometry

6. Microscope efficiency Double refreshed films exposed to CERN beam in July

7. Scanning, processing and event selection • General scanning 66 cm2 on both CS around the prediction position • Top-bottom linking • MinGrains  7 (actually set up in the microscope DAQ because of the higher fog density that slows the acquisition) • MinSlope = 0 • MergePosTol = 20 mm • MergeSlopeTol = 0.050 • PosTol = 30mm • SlopeTol = 0.050 rad • SlopeTolIncreaseWithSlope = 0.2 • Basetrack quality cut • Sigma<N0.13-1.7 • Event selection • dtan(q)<0.040 respect to the ED prediction • CS connection • dtan(q) < 0.025 && dr < 40 mm && Ntot40

8. Event 1064775 • Scanned area 4.8  4.1 cm2 • Located in emulsion on 18/11/2006 16:54 • Confirmed manually

9. Event 2367442: not located • CSD ID: 3000521 (near edge, big slope) • 6.0 x 3.1 cm2on 29-NOV-06

10. Event 1848052: not located • CSD ID: 3000456 • 6.0 x 6.0 cm2on 17-NOV-06 (surface lost) • 6.0 x 6.0 cm2on 20-NOV-06 • 6.0 x 6.0 cm2on 27-NOV-06 • 9.2 x 9.4 cm2on 29-NOV-06 • CSD ID: 3000235 (near edge) • 6.0 x 3.3 cm2on 23-NOV-06

11. Event 1848052:3 out of 4 microtrack analysis • BatchLink, version 2.0 modified with striplink option • Quality cut for basetrack: Sigma<N0.13-1.7 • Promote microtracks to base-tracks if N9 • Select all tracks if the Dslope  0.200 respect to ED reconstruction • Proceed with the standard analysis • For the connection of a basetrack and a microtrack • 40 mm && 150 mrad && Dslope(basetrack-ED reconstruction)<0.040 • No candidate was found with Cristiano

12. Event 1848052:double measured basetracks • The two 66 cm2 zone in the same CS has been link together according to: • Dslope (basetrack-ED reconstruction) < 0.050 • N20 for at least one basetrack • DSX(bt1-bt2) < 0.020 && DSY(bt1-bt2) < 0.020 • 6 basetracks are selected on CS1, 5 are manually confirmed, no track found in CS2 according to projection • 9 basetracks are selected on CS2, 6 are manually confirmed, no track found in CS1 according to projection

13. August run event beam

14. CS candidates reproducibility We re-measured the 3 August run events that we have in LNGS In case of good tracks the system has a good reproducibility

15. ED-CS connection

16. CS1-CS2 connection Here the mark grid were not measured automatically, it has been corrected in the successive measurements

17. OFFSET Link top-bottom microtracks

18. CSD exposed to cosmic rays • 6 OPERA bricks were exposed to CR in order to fully simulate the OPERA scanning procedure (3000973,3001166,3001025,3000635,3000605,3000681) • CS candidates were sent by mail to European scanning labs • Scanned area: • 4.0  4.0 cm2 in the central zone of 6 CSD • 3.0  9.2 cm2 along the short side of 5 CSD • 193 CSD candidates / 234 cm2  0.82/cm2 • Expected number 100/CS  0.83/cm2

20. Manual check • To have a feeling of reliability of the cut used for the CS candidates selection the manual check has been performed for the tracks of CSD 3000605 This CS candidate has 39 grains In one case a basetrack has been measured with a wrong angle, some test are in progress

21. We have to better use the mark position • Some divergence in the X ray beam

22. CSD scanning driven by DB • All scannings have been driven by DB • Now the machinery works smoothly: • 4 scanning workstations works together • 3 data processing computers • 1 DB server • 1 Batch Manager • It needs easy operations by shifters from scanning workstations: • submit the job • change plate

23. CS scanning: modules Three programs have been written: • CSScanDriver: controls, connects CSD, saves basetracks information in the DB • WideAreaScanDriver: scans areas in strips, manages strip linking, checks quality continuously • BatchLink: links strips optimizing performances • the old StripLink has been replaced by “custom” version of BatchLink in order to benefit for future code developments

24. Input DB tables • TB_PREDICTED_EVENTS • EVENT • ID_PROCESSOPERATION • ID • POSX • POSY • POSZ • TYPE • TB_PREDICTED_TRACKS • ID_EVENT • TRACK • Z • POSX • POSY • SLOPEX • SLOPEY • FRAME • POSTOL1 • POSTOL2 • SLOPETOL1 • SLOPETOL2 • TB_PREDICTED_BRICKS • ID_EVENT • ID_EVENTBRICK • PROBABILITY A simple program that reads ED predictions from a text file and inserts them into the DB with emulsion DB group

25. Output DB tables • TB_CS_CANDIDATES • ID_EVENTBRICK • ID_PROCESSOPERATION • ID_EVENT • TRACK • CANDIDATE • ID • TB_CS_CANDIDATE_TRACKS • ID_EVENTBRICK • ID_CANDIDATE • ID_ZONE • SIDE • ID_MICROTRACK These tables are filled by CSScanDriver and are used to feed the general DB with the information to drive the scanning in the brick with emulsion DB group

26. Conclusions and outlook • CSD measurements driven by DB @ LNGS scanning lab works smoothly • It’s necessary to know OPERA geometry with a better accuracy both for brick position and track reconstruction • Check mark accuracy • Improve microtrack resolution • Take under control emulsion distortions