User Tools

Site Tools


tuning_the_s800_xdt

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
tuning_the_s800_xdt [2015/10/29 12:49]
pereira [Timing setup]
tuning_the_s800_xdt [2017/05/26 16:06]
pereira [Timing setup]
Line 68: Line 68:
  
   * Set trigger to “s800 trigger”    * Set trigger to “s800 trigger” 
-      * Ensure that the **[[s800 daq tools#trigger GUI|trigger GUI]]** application is ready. Otherwise, open it by clicking button **[[s800 daq tools#Run Control Window|Launch ULM GUI]]** in ReadoutGUI +      * Ensure that the **[[s800 daq tools#trigger GUI|trigger GUI]]** application is ready. Otherwise, open it by clicking button ''Launch ULM GUI'' in [[#ReadoutGUI|ReadoutGUI]] 
           * Under trigger tab select **s800 trigger** (which is E1 up by definition)           * Under trigger tab select **s800 trigger** (which is E1 up by definition)
           * Deselect experiment trigger           * Deselect experiment trigger
Line 74: Line 74:
           * End and Begin **[[s800 daq tools#Run Control Window|ReadoutGUI]]** to assert new trigger condition           * End and Begin **[[s800 daq tools#Run Control Window|ReadoutGUI]]** to assert new trigger condition
  
-  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_SCINT.win** in directory **/user/s800/operations/spectcl/Windows**+  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_SCINT.win** in directory **/user/s800/operations/spectcl/s800v7/Windows**. (NOTE: Spectra definition files can be found in directory **/user/s800/operations/spectcl/s800v7/Definitions**. A good file with useful spectra is **s800xdt.tcl**) 
  
   * Adjust **[[hv bias|bias]]** looking at 2D spectra **e1.deup_e1.dedown** (showing the parameters s800.fp.e1.de_down vs. s800.fp.e1.de_up) for the FP E1 scintillator   * Adjust **[[hv bias|bias]]** looking at 2D spectra **e1.deup_e1.dedown** (showing the parameters s800.fp.e1.de_down vs. s800.fp.e1.de_up) for the FP E1 scintillator
Line 94: Line 95:
  
  
-  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_IC.win** in directory **/user/s800/operations/spectcl/Windows** +  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_IC.win** 
  
   * Adjust pad gains   * Adjust pad gains
Line 127: Line 127:
       * Count rate is a little higher than on scintillator due to noise or thresholds       * Count rate is a little higher than on scintillator due to noise or thresholds
  
-  * Check **[[s800 SpecTcl|Spectcl]]** window **S800_CRDCS.win** in directory **/user/s800/operations/spectcl/Windows** (see figure below) to verify the good performance of the detectors. (The spectra for each CRDC can be checked separatelly in windows **s800_CRDC1.win** and **S800_CRDC2.win**)+  * Check **[[s800 SpecTcl|Spectcl]]** window **S800_CRDCS.win** (see figure below) to verify the good performance of the detectors. (The spectra for each CRDC can be checked separatelly in windows **s800_CRDC1.win** and **S800_CRDC2.win**)
  
       * Spectra **crdc1.raws** and **crdc2.raws** (top and middle spectra in the leftmost (first) column)       * Spectra **crdc1.raws** and **crdc2.raws** (top and middle spectra in the leftmost (first) column)
Line 171: Line 171:
       * The two spectra in the fifth row corresponds to the MTDC summary spectra of OBJ-FP and XFP-FP ToFs (zoomed in). The spectra show the ToF (vertical axis) vs. hit number (horizontal axis). Note that in a unreacted-beam setting, the first hit typically provides the "good" ToF (i.e. start and stop signals come from the same event). This is not the case in a reaction setting, where the rates in the XFP and OBJ detectors are much higher than in the FP SCI        * The two spectra in the fifth row corresponds to the MTDC summary spectra of OBJ-FP and XFP-FP ToFs (zoomed in). The spectra show the ToF (vertical axis) vs. hit number (horizontal axis). Note that in a unreacted-beam setting, the first hit typically provides the "good" ToF (i.e. start and stop signals come from the same event). This is not the case in a reaction setting, where the rates in the XFP and OBJ detectors are much higher than in the FP SCI 
       * An empty ToF spectrum means that either the delays are not right (and need to be adjusted) or the spectrum range is too narrow        * An empty ToF spectrum means that either the delays are not right (and need to be adjusted) or the spectrum range is too narrow 
-      * The MTDC spectra should never be empty because the matching window is sufficiently wide (around 4000 ns)+      * The MTDC delays should never need to be adjusted because the matching window is sufficiently wide (around 4000 ns)
  
 {{:wiki:SpecTcl-e14019-run103.jpg?850|S800_ToF.win page}} {{:wiki:SpecTcl-e14019-run103.jpg?850|S800_ToF.win page}}
Line 177: Line 177:
   * Due to the multi-hit capability of the MTDC, we need to select the "good" MTDC ToF peak so that SpecTcl can search for the right hit (more details can be found [[Timing#MTDC|here]]):   * Due to the multi-hit capability of the MTDC, we need to select the "good" MTDC ToF peak so that SpecTcl can search for the right hit (more details can be found [[Timing#MTDC|here]]):
       * Use the spectra **TOF.MTDC_RF**, **TOF.MTDC_OBJ**, and **TOF.MTDC_XFP** (second row in figure above)        * Use the spectra **TOF.MTDC_RF**, **TOF.MTDC_OBJ**, and **TOF.MTDC_XFP** (second row in figure above) 
-      * Using the cursor mouse, check the lower and higher limits defining the region in the MTDC ToF spectra with the "good" ToF peak. Do it of the three ToFs: RF-FP, OBJ-FP, and XFP-FP+      * Using the cursor mouse, check the lower and higher limits defining the region in the MTDC ToF spectra with the "good" ToF peak. Do it for the three ToFs: RF-FP, OBJ-FP, and XFP-FP
       * Go to the **Variables** page in SpecTcl GUI and assign the limits to the following variables:        * Go to the **Variables** page in SpecTcl GUI and assign the limits to the following variables: 
-              * s800.fp.vmetdc.mtdc_objlow and s800.fp.vmetdc.mtdc_rfhigh for RF-XFP +              * **s800.fp.vmetdc.mtdc_rflow** and **s800.fp.vmetdc.mtdc_rfhigh** for RF-XFP 
-              * s800.fp.vmetdc.mtdc_objlow and s800.fp.vmetdc.mtdc_rfhigh for OBJ-XFP +              * **s800.fp.vmetdc.mtdc_objlow** and **s800.fp.vmetdc.mtdc_objhigh** for OBJ-XFP 
-              * s800.fp.vmetdc.mtdc_xfplow and s800.fp.vmetdc.mtdc_xfphigh for XFP-XFP+              * **s800.fp.vmetdc.mtdc_xfplow** and **s800.fp.vmetdc.mtdc_xfphigh** for XFP-XFP
       * For each ToF, SpecTcl will search the hit number that fits in the selected region. The new MTDC ToF parameters are **s800.fp.vmetdc.mtdc_rf**, **s800.fp.vmetdc.mtdc_obj**, and **s800.fp.vmetdc.mtdc_xfp**        * For each ToF, SpecTcl will search the hit number that fits in the selected region. The new MTDC ToF parameters are **s800.fp.vmetdc.mtdc_rf**, **s800.fp.vmetdc.mtdc_obj**, and **s800.fp.vmetdc.mtdc_xfp** 
  
-  * If necessary, adjust delays: +  * If necessary, adjust delays of Phillips TDC (in principle, the TACs delays don't need to be adjusted)
-      * Using the [[S800 DAQ tools#Trigger GUI|ULM trigger GUI]] assign TDC-start to one of the Inspect Trigger channels and trigger the scope with it +      * Using the [[S800 DAQ tools#Trigger GUI|ULM trigger GUI]] assign TDC-start to one of the Inspect Trigger channels (patch panel #55 - #58) and trigger the scope with it (be aware that the TDC-start signal seen in the scope has an additional delay of ~200 ns due to the length of the cables between the ULM module in S3 vault and dataU6 patch panel) 
-      * Select the timing signals (Delay inspect channels) E1 up, OBJ and XFP with the [[S800 DAQ tools#Delay Window|Delay GUI]] and look at them in the scope +      * Connect the XFP and/or OBJ signals going to the Phillips TDC (via cables plugged to patch #66 and #67, respectively) to the scope 
-      * Adjust the TDC delays of OBJ and XFP using the delay boxes connected to the CANBERRA CFD 454 in data U6 +      * Adjust the TDC delays of OBJ and/or XFP with respect to the TDC start, using the delay boxes connected to the CANBERRA CFD 454 in data U6 
-      * Adjust the TDC delays of E1 updown using the Delay GUI +      * Be aware that the after adjusting OBJ and XFP delays in the scope, the signal will be further delayed by ~200 ns due to the length of the cable between dataU6 patch panel and the Phillips TDC in the S3 vault. 
-      * In principle, the TACs delays don't need to be adjusted+ 
 +  * Check the efficiencies of the Phillips TDCTACs, and MTDC for the OBJ-FP and XFP-FP ToFs: 
 +      * Make a gate on spectrum **IC.SUM** selecting the region of interestand call it "IC" 
 +      * Looking at the ToF spectra gated on "IC" compare the recorded events in the spectra with the number of events in the gate 
 +      * The window file **S800_TOF_EFFICIENCY.win** includes all the spectra needed 
  
 ==== Checking Particle ID and rate at S800 FP ==== ==== Checking Particle ID and rate at S800 FP ====
  
-  * Select SpecTcl window **S800_PID.win** in directory **/user/s800/operations/spectcl/Windows** +  * Select SpecTcl window **S800_PID.win** 
       * The three columns correspond to the PID determined with the **RF-FP** ToF (left), **OBJ-FP** (center), and **XFP-FP** (right)       * The three columns correspond to the PID determined with the **RF-FP** ToF (left), **OBJ-FP** (center), and **XFP-FP** (right)
       * The first (top) row corresponds to PID spectra using the Phillips TDC       * The first (top) row corresponds to PID spectra using the Phillips TDC
       * The second row corresponds to PID spectra using the MTDC with __just the first hit included__       * The second row corresponds to PID spectra using the MTDC with __just the first hit included__
-      * The third row corresponds to PID spectra using the MTDC gated on the "good" ToF peak   +      * The third row corresponds to PID spectra using the MTDC including the correct hit corresponding to the good ToF peak (see previous section) 
-      * The fourth row corresponds to PID spectra using the ORTEC TACs. Note that there is not **RF-FP TAC**+      * The fourth row corresponds to PID spectra using the MTDC gated on the "good" ToF peak   
 +      * The fifth row corresponds to PID spectra using the ORTEC TACs. Note that there is not **RF-FP TAC**
       * You might need to adjust the limits of the spectra to get a good resolution       * You might need to adjust the limits of the spectra to get a good resolution
  
Line 205: Line 211:
  
   * Establish PID and measure rate   * Establish PID and measure rate
-      * Determine the blob that corresponds to the unreacted beam (refer to information on setting from A1900 FP)+      * Choose your favorite PID spectrum and determine the blob that corresponds to the unreacted beam (refer to information on setting from A1900 FP). Note: the PID using the first MTDC hit might be missing good events
       * Take gates around the fragment of interest       * Take gates around the fragment of interest
       * Measure the beam intensity the appropriate faraday cup       * Measure the beam intensity the appropriate faraday cup
Line 275: Line 281:
  
   * Set trigger to “s800 trigger”   * Set trigger to “s800 trigger”
-      * Ensure that the **[[s800 daq tools#trigger GUI|trigger GUI]]** application is ready. Otherwise, open it by clicking icon **[[s800 daq tools#Run Control Window|RunControl]]** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] computer+      * Ensure that the **[[s800 daq tools#trigger GUI|trigger GUI]]** application is ready. Otherwise, open it by clicking ''Launch ULM GUI'' on [[#Readout GUI|Readout GUI]] in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] computer
       * Under trigger tab select **s800 trigger** (which is E1 up by definition)       * Under trigger tab select **s800 trigger** (which is E1 up by definition)
           * Deselect experiment trigger           * Deselect experiment trigger
           * SAVE TO FILE           * SAVE TO FILE
-          * Stop and start **[[s800 daq tools#Run Control Window|RunControl]]** to assert new trigger condition+          * Begin a new run on [[#Readout GUI|Readout GUI]]  to assert new trigger condition
  
   * Select **[[s800 SpecTcl|Spectcl]]** window **S800_DISPMATCH.win**   * Select **[[s800 SpecTcl|Spectcl]]** window **S800_DISPMATCH.win**
Line 329: Line 335:
               * What experimenters want (e.g., if they want singles, the cut has to be more restrictive to limit acquisition deadtime)               * What experimenters want (e.g., if they want singles, the cut has to be more restrictive to limit acquisition deadtime)
           * Move blocker, decrease attenuator, repeat           * Move blocker, decrease attenuator, repeat
 +
 +      * If necessary, do the ToF corrections to improve the PID resolution (instructions [[During experiments#Particle identification corrections|here]])
  
  
tuning_the_s800_xdt.txt · Last modified: 2023/09/22 15:15 by swartzj