Versions Compared

Old Version 29

changes.mady.by.user Mikhail Dubrovin

Saved on

compared with

New Version 30

changes.mady.by.user Mikhail Dubrovin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Comments on orientation of epix10ka2m parts from Matt

Code Block
title2018-1011-09 19 orientation schemacollapsetrue
Weaver, Matt 
Tue 10/92018-11-19, 37:0737 PMO'Grady, Paul Christopher;Dubrovin, Mikhail;Damiani, Daniel S.           

Hi Mikhail,
We took radioactive source test
Also, here'sruns sometoday descriptionto ofverify the nominal geometry. 
Pay closeWe attention to the last part that describes the positioning of 
ASICs within an "element".  I think this might be different than before.
-Matt

  //
  //   Hard code the array's geometry for now
  //
  //  (Epix10ka2m)
  //         |
  //  Quad 3 | Quad 0      Quad 1 is rotated  90d clockwise
  //  found that we were rotated by 90
 degrees, which matches the labeling on the back of the detector as well
 as the metrology picture from Chris Kenney. 
The runs are 
/reg/d/psdm/det/detdaq17/e968-r0131   - source unmasked (up to ~ event 10000), then masked vertically after ~ event 15000
/reg/d/psdm/det/detdaq17/e968-r0132   - source masked horizontally at bottom after ~ event 15000.

So, the picture is...
  //  (Epix10ka2m)
  //         |
  //  Quad 0 | Quad 1      Quad 2 is rotated  90d clockwise
  //  -------+--------     Quad 23 is rotated 180d clockwise
  //  Quad 23 | Quad 12      Quad 30 is rotated 270d clockwise
  //         |
  //
  //  (Quad 01)
  //         |
  //  Elem 0 | Elem 1
  //  -------+--------     No rotations
  //  Elem 2 | Elem 3
  //         |
  //
  //  (Elem 0)
  //         |
  //  ASIC 0 | ASIC 3
  //  -------+--------     No rotations
  //  ASIC 1 | ASIC 2
  //         |
Code Block
title2018-11-18 orientation schema
collapsetrue
Weaver, Matt 2018-11-18, 6:14 PMDubrovin, Mikhail;O'Grady, Paul Christopher
Here's the geometry I'm now using (below).  Note that pixel(0,0) 
for each of the elements below is in the lower right hand corner.
We'll know the quadrant layout for sure when we get the radioactive source exposure on Monday.
  //  (Epix10ka2m)  //
  //  (Elem 0-3 pixel array)
  //                    row increasing
  //                          ^
  //         |
  //  Quad 3 | Quad 0      Quad 1 is rotated  90d clockwise |
  //  -------+--------     Quad 2 is rotated 180d clockwise
  //  Quad 2 | Quad 1      Quad|
 3 is// rotated 270dcolumn clockwise
increasing <-- (0,0)

Preliminary geometry

in /reg/g/psdm/detector/data_test/calib/

Code Block
/reg/g/psdm/detector/data_test/calib/Epix10ka2M::CalibV1/NoDetector.0:Epix10ka2M.0/geometry/0-end.data @/         |
  //
  //  (Quad 0)
  //         |
 (epix10ka2m //-  Elem 0 | Elem 1
  //  -------+--------     No rotations
  //  Elem 2 | Elem 3
  //         |
  //
The ASICs did not move. The change is that the (352,384) 
array has pixel (0,0) in the lower right hand corner (in ASIC2).
  //  (Elem 0)
  //         |
  //  ASIC 0 | ASIC 3
  //  -------+--------     No rotations
  //  ASIC 1 | ASIC 2
  //         |
  //
  //  (Elem 0-3 pixel array)
  //                    row increasing
  //                          ^
  //                          |
  //                          |
  //  column increasing <-- (0,0)
Code Block
title2018-11-19 orientation schema
Weaver, Matt 
2018-11-19, 7:37 PMO'Grady, Paul Christopher;Dubrovin, Mikhail             

Hi Mikhail,
We took radioactive source test
 runs today to verify the geometry.  We found that we were rotated by 90
 degrees, which matches the labeling on the back of the detector as well
 as the metrology picture from Chris Kenney. 
The runs are 
/reg/d/psdm/det/detdaq17/e968-r0131   - source unmasked (up to ~ event 10000), then masked vertically after ~ event 15000
/reg/d/psdm/det/detdaq17/e968-r0132   - source masked horizontally at bottom after ~ event 15000.

So, the picture is...
  //  (Epix10ka2m)
  //         |
  //  Quad 0 | Quad 1      Quad 2 is rotated  90d clockwise
  //  -------+--------     Quad 3 is rotated 180d clockwise
  //  Quad 3 | Quad 2      Quad 0 is rotated 270d clockwise
  //         |
  //
  //  (Quad 1)
  //         |
  //  Elem 0 | Elem 1
  //  -------+--------     No rotations
  //  Elem 2 | Elem 3
  //         |
  //
  //  (Elem 0)
  //         |
  //  ASIC 0 | ASIC 3
  //  -------+--------     No rotations
  //  ASIC 1 | ASIC 2
  //         |
  //
  //  (Elem 0-3 pixel array)
  //                    row increasing
  //                          ^
  //                          |
  //                          |
  //  column increasing <-- (0,0)

Preliminary geometry

in /reg/g/psdm/detector/data_test/calib/

...

entire detector)
/reg/g/psdm/detector/data_test/calib/Epix10kaQuad::CalibV1/NoDetector.0:Epix10kaQuad.0/geometry/0-end.data @  (epix10kaquad - one quad)
/reg/g/psdm/detector/data_test/calib/Epix10ka::CalibV1/MecTargetChamber.0:Epix10ka.1/geometry/0-end.data @    (epix10ka - one panel)

copy of geometry files in alignment examples /reg/g/psdm/detector/alignment/

Code Block
/data_test/calib/Epix10kaQuad::CalibV1/NoDetector.0:Epix10kaQuad.0/geometry/0-end.data @  (epix10kaquad - one quad)
/reg/g/psdm/detector/data_testdetector/alignment/epix10ka2m/calib/Epix10kaEpix10ka2M::CalibV1/MecTargetChamberNoDetector.0:Epix10kaEpix10ka2M.10/geometry/0-end.data @    (epix10ka - one panel)

...


/reg/g/psdm/detector/alignment

...

Code Block
/epix10kaquad/calib/Epix10kaQuad::CalibV1/NoDetector.0:Epix10kaQuad.0/geometry/0-end.data
/reg/g/psdm/detector/alignment/epix10ka2mepix10ka/calib/Epix10ka2MEpix10ka::CalibV1/NoDetectorMecTargetChamber.0:Epix10ka2MEpix10ka.01/geometry/0-end.data

Image AddedImage AddedImage Added

Optical metrology processing

Scripts for processing

Code Block
CalibManager/app/
  optical_metrology_check
  optical_metrology_epix10ka2m

Results in

Code Block
/reg/g/psdm/detector/alignment/epix10kaquadepix10ka2m/calib/Epix10kaQuad::CalibV1/NoDetector.0:Epix10kaQuad.0/geometry/0-end.data
/reg/g/psdm/detector/alignment/epix10ka/calib/Epix10ka::CalibV1/MecTargetChamber.0:Epix10ka.1/geometry/0-end.data-mfx-epix10ka2m-01-2018-11-15/
  2018-11-15-Metrology-epix10ka2m.xlsx
  2018-11-15-Metrology-epix10ka2m.txt
  2018-11-15-Metrology-epix10ka2m-corr.txt
  2018-11-15-geometry-epix10ka2m.txt - geometry file accounting for optical metrology data
  README-2018-11-15

Image AddedImage Added

 

 Image RemovedImage RemovedImage Removed

Gain

Code Block
titleGabriel's comments on gain factors
collapsetrue
Blaj, Gabriel 
2018-12-04, 2:08 PMO'Grady, Paul Christopher;Nelson, Silke;Dubrovin, Mikhail;Hart, Philip Adam             

Hi, 
You could try to use the gain files obtained with the pulser. They are not great but might work.

For a better gain calibration, we should use single photon data. 
There is sufficient 1 photon data taken during the first testing at XCS,
but it will take me a few days to calculate the gains.

I would actually advocate returning the number of photons (as we 
discussed in a meeting a few months ago). Even without a calibration it 
can be easily calculated from the (average) gains:

High (FH and AHL): 132 ADU/9.5 keV
Medium (FM and AML): 43 ADU/9.5 keV
Low (FL, AHL, AML): 1.32 ADU/9.5 keV

(Just a note, while the pulser is not great for calibrating gains, it works fine for offset calibration)

Thanks,
Gabriel

...

 /reg/g/psdm/detector/alignment/epix10ka2m/calib-mfx-epix10ka2m-01-2018-11-15