Differences

This shows you the differences between two versions of the page.

--- daq:decomp_calibrations [2017/02/27 11:23]
peter_bender created
+++ daq:decomp_calibrations [2017/02/27 12:26]
peter_bender
@@ Line 1: / Line 1: @@
-==== Decomp Calibrations ====
+====== Decomp Calibrations ======
+== detmap files ==
+The calibration procedure starts with a detmap file.  Such a file exists for each quad.  Each file is a plain text list of the offset and gain of each channel of the quad respectively.  The channels are seperated by new lines. The order of the channels is in the the daq order (i.e the order they arrive at the digitizer, remember Q1 is different).   The naming scheme of the files is important for the rest of the scripts to work; current convention is **detmap_Q1.txt**, where the 1 could be replaced by any quad number.
+A truncated example of a detmap file:
+<code>
+.282147                        0.293645
+-0.455952                       0.292579
+-0.281072                       0.294927
+-0.579122                       0.293367
+-0.391375                       0.314109
+.106291                        0.295857
+-0.20183                        0.295819
+-0.294165                       0.286083
+-0.323898                       0.300403
+.101371                        0.308178
+</code>
+Above are the first ten channels of the one detmap file.  The first column is the offset, the second column is the gain. The channel is indicted by the row number.
+== Splitting the detmap files ==
+After the creation of the detmap files, they must be split into the corresponding cores and segments.  Assuming the above formatted file and standard file convention; this can be done with the script:
+<code>
+~analysis/packages/Calibrations/split_cal.py
+</code>
+This is script is run by passing it the detmap file to be split:
+<code>
+~analysis/packages/Calibrations/split_cal.py  detmap_Q1.txt
+</code>
+which will create files **detmap_Q1CC.txt** and **detmap_Q1Seg.txt**.
+== Shaofei's mapping scripts ==
+Once all detmap files are split into their CC and Seg components, we can than use Shaofei's mapping scripts to create the rest of the need decomp files. **The order these scripts are run in is very important.** In order with example arguments:
+<code>
+~analysis/packages/benderCal/merge_detmap . detmap
+</code>
+This script creates **detmap_Q1pos[1-4]_CC[9-39]Cal.txt** and **detmap_Q1Seg.txt** file for each quad
+<code>
+~analysis/packages/benderCal/get_detmap ~gretina/DecompParam/detmaps_170209/ detmap . detmap
+</code>
+This script gets the header file need to map daq ordered channels to decomp mode2 order channels.  The file **detmap_Q1pos[1-4]_CC[9-39].txt** will be created. These files should now look like:
+<code>
+x3     0       0       0       0.282147        0.293645
+x3     1       0       1       -0.455952       0.292579
+x3     2       0       2       -0.281072       0.294927
+x3     3       0       3       -0.579122       0.293367
+x3     4       0       4       -0.391375       0.314109
+x3     5       0       5       0.106291        0.295857
+x3     6       0       6       -0.20183        0.295819
+x3     7       0       7       -0.294165       0.286083
+x3     8       0       8       -0.323898       0.300403
+x3     9       0       36      0.101371        0.308178
+x4     0       0       9       -0.0101913      0.324076
+x4     1       0       10      0.404754        0.300472
+x4     2       0       11      -0.346688       0.295173
+x4     3       0       12      0.397739        0.326801
+x4     4       0       13      -0.0799647      0.231865
+x4     5       0       14      -0.53801        0.319978
+x4     6       0       15      -0.485629       0.305327
+x4     7       0       16      -0.346114       0.295598
+x4     8       0       17      -0.385398       0.295361
+x5     0       0       18      -0.354487       0.322502
+x5     1       0       19      -0.253475       0.298176
+x5     2       0       20      -0.403024       0.314914
+x5     3       0       21      -0.441589       0.318274
+x5     4       0       22      -0.235985       0.287324
+x5     5       0       23      -0.0343097      0.306376
+x5     6       0       24      -0.533586       0.293114
+x5     7       0       25      0.509689        0.297238
+x5     8       0       26      -0.179804       0.303876
+x6     0       0       27      -0.0729594      0.217916
+x6     1       0       28      -0.516658       0.298321
+x6     2       0       29      -0.771099       0.290957
+x6     3       0       30      -0.375356       0.297646
+x6     4       0       31      0.175389        0.298985
+x6     5       0       32      -0.354584       0.308682
+x6     6       0       33      -0.792392       0.314499
+x6     7       0       34      -0.365302       0.289866
+x6     8       0       35      -0.942629       0.294357
+</code>
+These are the calibrations files actually loaded by the GRETINA Decomp process.
+== Trace gain files ==
+After the calibration files have been made using the above steps, we must make the trace gain files.  This is a two step procedure and we assume here we are still using the standard naming procedure.
+The first step requires running a root script:
+<code>
+> root -lb
+root [0] .L ~analysis/packages/benderCal/GT2Cal_Bender.cpp
+root [1] get_tr_gain(".","detmap")
+</code>
+This script will output the trace gains to the screen as they are calculated. One must hit enter after each Q for the script to continue or simply hold enter down, the script only takes a few seconds to run. Once this is done we need to quit root.
+<code>
+root [2] .q
+</code>
+This script will have created files **detmap_Q[1-10]CC_tr_gain.txt** and files **detmap_Q[1-10]Seg_tr_gain.txt** for each quad.  After creating these files they must be merged into their trace gain files for their respective gain ranges:
+<code>
+~analysis/packages/benderCal/merge_detmap_tr . detmap
+</code>
+which will produce files ** tr_gain_Q[1-10]pos[1-4]_CC[9-39].txt**.  These are the trace gains actually loaded by the GRETINA Decomp process.  At this point bad channels must be edited to a large value for the gain range which will be loaded by the DAQ.  For example, the **Q4P2** has a bad segment and we plan to use the 10 MeV range (first digitizer) - so file **tr_gain_Q4pos2_CC9.txt** must be edited from something which looks like:
+<code>
+.83885843
+.82833356
+.79647750
+.86153644
+.82199061
+.85602087
+.82397383
+.88007176
+.95295018
+.83846498
+.83268768
+.81359202
+.84887129
+.84606075
+.82328838
+.92762762
+.90537167
+.84306300
+.84145373
+.83354926
+.84602684
+.82818270
+.84309858
+.84301353
+.35928223
+.83807576
+.84559876
+.83149475
+.82677245
+.84563261
+.84975672
+.85358042
+.85946518
+.84654522
+.92021245
+.85450613
+.88523686
+</code>
+to:
+<code>
+.83885843
+.82833356
+.79647750
+.86153644
+.82199061
+.85602087
+.82397383
+.88007176
+.95295018
+.83846498
+.83268768
+.81359202
+.84887129
+.84606075
+.82328838
+.92762762
+.90537167
+.84306300
+.84145373
+.83354926
+.84602684
+.82818270
+.84309858
+.84301353
+.000
+.83807576
+.84559876
+.83149475
+.82677245
+.84563261
+.84975672
+.85358042
+.85946518
+.84654522
+.92021245
+.85450613
+.88523686
+</code>

Trace:

Differences

Search

Toolbox

QR Code