this is the second version of alignment done by Alexander Schmah, in the following called "real" alignment.


Method:

  1. plane I: using the photomodeler 5 the chambers are aligned with respect to each other
  2. plane II: using the photomodeler 5 the chambers are aligned with respect to each other
  3. using cosmic rays the pyramids of plane I chambers and plane II chambers are aligned with respect to each other
  4. target alignment using hits from plane I and II
  5. outer chambers: using hits from inner chambers pointing towards outer, the outer chambers are aligned individually and not as a "package" (straight tracks, B=0)


general settings:
  • xdir and ydir are not used anymore for the alignment
  • minimization: distance
  • file used for alignment of drift chambers and 3 segmented target, no magnetic field:be04242033720.hld
  • calibration used: see slopes and offsets, same as for alignment version before

Problems with:

  • target position for one sector of the inner chambers can not be well adjusted
  • inner mdcs sector 3: when trying to reconstruct the target, one has problems with sector 3, the resolution is worse, reason unknown
  • Sector 1 plane IV: chamber has hardware problems. thus few hits available, in the middle of the chamebrs there are no hits. nevertheless a position is determined. from Jan04 alignment is applied
  • Sector 3 plane III: hardware problems, but alignment position could be found


Full Target Position

target position not checked for full target with file, no magnetic field, because last time it turned out that the target position for 3-seg-target and full target is the same


Difference old alignment and new alignment version

(difference only in translation, no rotation check)

Sector: 0 Module: 0 :   0.70356 2.462 -1.515
Sector: 0 Module: 1 :   1.8 2.4 -2.5
Sector: 0 Module: 2 :   4.60273 1.03 -5.993
Sector: 0 Module: 3 :   4.10549 0.21 -6.06
Sector: 1 Module: 0 :   1.231 0.784 -2.649
Sector: 1 Module: 1 :   1.589 1.198 -3.234
Sector: 1 Module: 2 :   3.67 9.641 -3.122
Sector: 1 Module: 3 :   6.24 9.561 -3.08
Sector: 2 Module: 0 :   1.919 0.686 -2.675
Sector: 2 Module: 1 :   2.166 1.176 -3
Sector: 2 Module: 2 :   4.691 2.283 -1.834
Sector: 2 Module: 3 :   0 0 0
Sector: 3 Module: 0 :   2.41457 0.791 -2.073
Sector: 3 Module: 1 :   2.68771 1.594 -2.821
Sector: 3 Module: 2 :   4.92016 3.96 -4.463
Sector: 3 Module: 3 :   6.27013 4.83 -5.51
Sector: 4 Module: 0 :   2.455 2.095 -1.549
Sector: 4 Module: 1 :   2.827 1.23 -1.985
Sector: 4 Module: 2 :   10.079 3.118 -8.637
Sector: 4 Module: 3 :   10.51 3.573 -9.84
Sector: 5 Module: 0 :   1.82 2.444 -1.095
Sector: 5 Module: 1 :   2.563 1.786 -2.033
Sector: 5 Module: 2 :   1.174 -3.868 -10.321
Sector: 5 Module: 3 :   0 0 0

reason for this difference:
  • inner: absolut difference (planeI-planeII) is below 1 mm, thus fine.
  • outer: large differences - in the old alignment version the outer chambers were aligned using xdir and ydir, which is not well reconstruceted by the tracking software, in the new version the minimization is done using only the distance (residuals)

status: 5.8.05


META Detectors

(responsible Y.C.Pachmayer)
Alignment with respect to magnetic field and meta alignment not yet available.
how to position the meta detectors:


Positioning Meta Detectors

taking the information of the difference in old alignment version and real/new alignment version into account the meta detectors are shifted - only in z!

e. g. zideal-zreal
if >0 --> znew<zold --> meta shifted by -(zold-znew)
if <0 --> znew>zold --> meta shifted by +(zold-znew)


Overlap Checker

extrusions exist, overlaps with stones and one magent coil (very little):

=== Overlaps for HadesGeom ===
* extrusion ov00/SEC4_x_2: vol=SEC4 node=DR3M_4 extr=1.27093
* extrusion ov01/SEC3_x_2: vol=SEC3 node=DR3M_3 extr=1.18151
* extrusion ov02/SEC2_x_3: vol=SEC2 node=DR4M_2 extr=0.970099
* extrusion ov03/SEC2_x_2: vol=SEC2 node=DR3M_2 extr=0.957793
* extrusion ov04/SEC1_x_2: vol=SEC1 node=DR3M_1 extr=0.920536
* extrusion ov05/SEC2_x_0: vol=SEC2 node=DR1M_2 extr=0.752909
* extrusion ov06/SEC5_x_0: vol=SEC5 node=DR1M_5 extr=0.504054
* extrusion ov07/SEC1_x_0: vol=SEC1 node=DR1M_1 extr=0.43521
* extrusion ov08/SEC4_x_0: vol=SEC4 node=DR1M_4 extr=0.39858
* extrusion ov09/SEC6_x_0: vol=SEC6 node=DR1M_6 extr=0.375588
* extrusion ov10/SEC5_x_2: vol=SEC5 node=DR3M_5 extr=0.246999
* extrusion ov11/SEC3_x_0: vol=SEC3 node=DR1M_3 extr=0.241662
* extrusion ov12/SEC4_x_3: vol=SEC4 node=DR4M_4 extr=0.228075
* extrusion ov13/SEC3_x_1: vol=SEC3 node=DR2M_3 extr=0.213249
* extrusion ov14/SEC2_x_1: vol=SEC2 node=DR2M_2 extr=0.141417
* extrusion ov15/SEC6_x_2: vol=SEC6 node=DR3M_6 extr=0.127258
* extrusion ov16/SEC6_x_1: vol=SEC6 node=DR2M_6 extr=0.0764353
* extrusion ov17/SEC1_x_1: vol=SEC1 node=DR2M_1 extr=0.057768
* extrusion ov18/SEC4_x_1: vol=SEC4 node=DR2M_4 extr=0.042473
* extrusion ov19/RMET_x_0: vol=RMET node=RPAS_1 extr=0.000163955
* extrusion ov20/RMET_x_2: vol=RMET node=RPAS_3 extr=0.000163955
* extrusion ov21/RMET_x_3: vol=RMET node=RPAS_4 extr=0.000163955
* extrusion ov22/RMET_x_5: vol=RMET node=RPAS_6 extr=0.000163955
* extrusion ov23/RMET_x_29: vol=RMET node=RPCS_4 extr=0.000114818
* extrusion ov24/RMET_x_28: vol=RMET node=RPCS_3 extr=0.000114818
* extrusion ov25/RMET_x_26: vol=RMET node=RPCS_1 extr=0.000114818
* extrusion ov26/RMET_x_31: vol=RMET node=RPCS_6 extr=0.000114818
* extrusion ov27/RMET_x_27: vol=RMET node=RPCS_2 extr=0.000108614
* extrusion ov28/RMET_x_30: vol=RMET node=RPCS_5 extr=0.000108614
* overlap ov29/SEC3_o_0_14: vol=SEC3 FD1S_3> ovlp=0.401536
* overlap ov30/SEC2_o_0_15: vol=SEC2 FD1S_2> ovlp=0.399886
* overlap ov31/SEC6_o_1_16: vol=SEC6 FD2S_6> ovlp=0.361169
* overlap ov32/SEC2_o_1_17: vol=SEC2 FD2S_2> ovlp=0.340658
* overlap ov33/SEC4_o_0_15: vol=SEC4 FD1S_4> ovlp=0.309137
* overlap ov34/SEC5_o_0_15: vol=SEC5 FD1S_5> ovlp=0.302885
* overlap ov35/SEC1_o_0_15: vol=SEC1 FD1S_1> ovlp=0.210068
* overlap ov36/SEC6_o_0_14: vol=SEC6 FD1S_6> ovlp=0.143357
* overlap ov37/SEC4_o_1_4: vol=SEC4 CKIV_4> ovlp=0.0936402
* overlap ov38/SEC5_o_1_17: vol=SEC5 FD2S_5> ovlp=0.0781408
* overlap ov39/SEC1_o_1_17: vol=SEC1 FD2S_1> ovlp=0.0774991
* overlap ov40/SEC3_o_1_16: vol=SEC3 FD2S_3> ovlp=0.0387692

All detectors shifted

to remove overlap of mdc II4 with coil case all detetctors and target are shifted by 2mm


For geometry files for simulation

  • FD stones (mdc stabilization stones) shifted
  • sector geometry enlarged by target shift: 32mm (towards accelerator)

thus only these overlaps remain:
* overlap ov35/TFN2_o_0_1: vol=TFN2 T24F_2> ovlp=0.0001003
* overlap ov36/TFN2_o_2_3: vol=TFN2 T26F_2> ovlp=0.0001003
* overlap ov37/TFN3_o_0_1: vol=TFN3 T24F_3> ovlp=0.0001003
* overlap ov38/TFN3_o_2_3: vol=TFN3 T26F_3> ovlp=0.0001003
* overlap ov39/TFN5_o_0_1: vol=TFN5 T24F_5> ovlp=0.0001003
* overlap ov40/TFN5_o_2_3: vol=TFN5 T26F_5> ovlp=0.0001003
* overlap ov41/TFN6_o_0_1: vol=TFN6 T24F_6> ovlp=0.0001003
* overlap ov42/TFN6_o_2_3: vol=TFN6 T26F_6> ovlp=0.0001003

geo files can be found here: /u/hadalign/aug04/macro/geofiles/aug04/fulltarget


RICH Optic Correction

according to Thomas the 2 mm shift of the target towards the accelerator can be neglected, thus parameters can be put to oracle for simulation and experiment

8.8.05 Y.C.Pachmayer

-- YvonnePachmayer - 14 Aug 2005
Topic revision: r3 - 24 Aug 2005, YvonnePachmayer
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)