location in csd of electronic detector reconstructed events scanning results from lngs scanning lab...

26
Location in CSD 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

Post on 21-Dec-2015

217 views

Category:

Documents


1 download

TRANSCRIPT

Location in CSD 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

Event number: 1064775 CSD ID: 3000370Brick location: W29/RW9/COL12, rock sideSX = -0.0839 0.0013 SY = 0.0259 0.0012PX = 181.54 0.27 cm PY = -288.03 0.25 cm PZ=-401.82 cm

with Dario and Antoine

Event number : 1848052 CSD ID: 3000456Brick location: W28/RW8/COL8, rock sideSX = -0.0517 0.0098 SY = 0.3456 0.0016PX = 238.99 1.21 cm PY = -302.33 0.19 cm PZ = -415.22 cm

with Dario and Antoine

Event number: 2367442 CSD ID: 3000521Brick location: W29/RW9/COL8, corridor sideSX = -0.0072 0.0029 SY = 0.6137 0.0024PX = -236.23 0.24 cm PY = -287.03 0.20 cm PZ = -401.821

with Dario and Antoine

Brick position in OPERA detector

ID POSITION SIDE MINX (mm) MAXX (mm) MINY (mm) MAXY (mm) MINZ (mm) MAXZ (mm)

3000521 W29/RW9/COL8 corridor -2432400 -2307300 -2965700 -2865900 -4018510 -4018210

3000370 W29/RW9/COL12 rock 1794900 1920000 -2965700 -2865900 -4018510 -4018210

3000235 W29/RW8/COL8 rock 2307300 2432400 -3071000 -2971200 -4018510 -4018210

3000456 W28/RW8/COL8 rock 2307300 2432400 -3071000 -2971200 -4152510 -4152210

The brick position has been calculated using the nominalgeometry

Microscope efficiency

Double refreshed films exposed to CERN beam in July

Scanning, processing and event selection1. General scanning 66 cm2 on both CS around the prediction position2. 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

3. Basetrack quality cut– Sigma<N0.13-1.7

4. Event selection tan(<0.040 respect to the ED prediction

5. CS connection tan( < 0.025 && r < 40 mm && Ntot40

Event 1064775

• Scanned area 4.8 4.1 cm2

• Located in emulsion on 18/11/2006 16:54

• Confirmed manually

CS N POSX (mm) POSY (mm) SLOPEX SLOPEY SIGMA1 26 1809743.4 -2880310.7 -0.0984 0.0001 0.722 21 1809777.0 -2880311.4 -0.0951 0.0023 0.42

CS1-CS2 DX (mm) DY (mm) DSX DSY-4.1 0.7 -0.0033 -0.0022

ED-CSD DX (cm) DY (cm) DSX DSY-0.5 0 -0.014 -0.026

Event 2367442: not located

• CSD ID: 3000521 (near edge, big slope)– 6.0 x 3.1 cm2 on 29-NOV-06

Event 1848052: not located

• CSD ID: 3000456– 6.0 x 6.0 cm2 on 17-NOV-06 (surface lost)– 6.0 x 6.0 cm2 on 20-NOV-06– 6.0 x 6.0 cm2 on 27-NOV-06– 9.2 x 9.4 cm2 on 29-NOV-06

• CSD ID: 3000235 (near edge)– 6.0 x 3.3 cm2 on 23-NOV-06

Event 1848052:3 out of 4 microtrack analysis

• BatchLink, version 2.0 modified with striplink option• Quality cut for basetrack: Sigma<N0.13-1.7• Promote microtracks to base-tracks if N9• Select all tracks if the slope 0.200 respect to ED

reconstruction• Proceed with the standard analysis

– For the connection of a basetrack and a microtrack– 40 mm && 150 mrad && slope(basetrack-ED

reconstruction)<0.040 • No candidate was found

with Cristiano

Event 1848052:double measured basetracks

• The two 66 cm2 zone in the same CS has been link together according to: slope (basetrack-ED reconstruction) < 0.050– N20 for at least one basetrack SX(bt1-bt2) < 0.020 && SY(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

August run event beamEvent Event type g exposure X(cm) Y(cm) SX SY raw col Location Result@LNGS

90834 rock 14h -142.7 -121.0 -0.004 0.166 14 12 LNGS->NGY FOUND

124528 n-int 14h -106.5 -213.1 -0.067 -0.177 5 9 NGY

174969 rock 14h -249.6 -252.6 -0.134 0.013 2 20 NGY->LNGS NOT FOUND

937379 n-int no -222.8 -210.9 -0.078 0.042 6 18 LNGS FOUND

2836561 n-int -87.8 -183.6 0.193 0.011 8 7 NA->LNGS NOT FOUND

3874834 rock 4h -81.8 -145.9 -0.055 0.164 12 7 LNGS->NGY FOUND

4191558 rock -164.8 -225.2 0.023 0.031 4 13 NGY

4379516 rock -146.9 -131.3 -0.067 0.075 13 12 LNGS FOUND

4641055 rock -112.0 -264.8 0.109 0.057 1 9 NA->LNGS NOT FOUND

4814867 rock 16h -236.7 -154.5 -0.020 0.089 11 19 LNGS->NGY FOUND

8947651 rock no -73.8 -249.3 0.070 0.024 2 6 LNGS NOT FOUND

9507801 n-int -12.4 -129.5 0.084 0.068 13 1 NGY

9516652 rock no -26.9 -189.5 0.027 0.109 8 3 NGY->LNGS FOUND

CS candidates reproducibility

EVENT MEASURED FOUND

4379516 9 9

937379 10 10

9516652 10 10

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

ED-CS connection

CS1-CS2 connectionHere the mark grid were not measured automatically, it has been corrected in the successive measurements

Link top-bottom microtracks

OFFSET

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

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

SELECTION CSD candidate Confirmed only CS1 only CS2 Not confirmedFull 45 45N40 8 1 7pos>40 mm 1 1slope >0.025 3 2 1

This CS candidate has 39 grains

In one case a basetrack has been measured with a wrong angle, some test are in progress

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

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

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

Input DB tables

TB_PREDICTED_BRICKS•ID_EVENT•ID_EVENTBRICK•PROBABILITY

TB_PREDICTED_TRACKS•ID_EVENT•TRACK•Z•POSX•POSY•SLOPEX•SLOPEY•FRAME•POSTOL1•POSTOL2•SLOPETOL1•SLOPETOL2

A simple program that reads ED predictions from a text file and inserts them into the DB

TB_PREDICTED_EVENTS•EVENT•ID_PROCESSOPERATION•ID•POSX•POSY•POSZ•TYPE

with emulsion DB group

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 thescanning in the brick

with emulsion DB group

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