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
tuning_the_s800_xdt [2017/05/26 16:06]
pereira [Timing setup]
tuning_the_s800_xdt [2017/07/24 10:48] (current)
pereira
Line 52: Line 52:
       * Check CFD walk inspect signal in scope by triggering scope with CFD output       * Check CFD walk inspect signal in scope by triggering scope with CFD output
       * Ensure that CFD delay cable is ok: about 80% of raising time of the input signal       * Ensure that CFD delay cable is ok: about 80% of raising time of the input signal
-      * Adjust CFD threshold looking at scalers. The ratio of OBJ to XFP scaler rates (channels OBJ.Scint and XFP.Scint) should reflect the transmission of the cocktail beam +      * Adjust CFD threshold looking at scalers. ​ 
 +          * With beam on/off, check amplitude of signals from OBJ. You should be able to clearly see the difference between noise signals and fragment-beam signals.  
 +          * Raise thresholds to get rid of noise signals. 
 +          * NOTE: Be aware that sometimes, after running for a while, the OBJ box is activated. This results in a non-negligible count rate in OBJ scalers with beam off, which comes from HIGH amplitude signals (not noise). DO NOT try to eliminate this "​activation"​ counts by raising the thresholds because that would reduce the efficiency of the detector. 
 +          * The ratio of OBJ to XFP scaler rates (channels OBJ.Scint and XFP.Scint) should reflect the transmission of the cocktail beam (between 60% to 90%, depending on quality of tunning)
  
   * Adjust MCFD threshold:   * Adjust MCFD threshold:
Line 66: Line 70:
  
 ==== FP scintillator setup ==== ==== FP scintillator setup ====
 +
 +  * Make sure that S800 DAQ is in [[s800 daq tools#​Running in Slave mode with multilogger |Slave mode and multilogger enabled]] to record S800 data in the s800 stagearea.
  
   * Set trigger to “s800 trigger” ​   * Set trigger to “s800 trigger” ​
Line 129: Line 135:
   * 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**)   * 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**  
-          * Each spectra shows the multiple sampled ​signals from each pad +          * Each spectra shows the pad signals ​averaged over the number of samples ​from the SCA (typically four) 
           * The 224 pads are assembled along the dispersive direction           * The 224 pads are assembled along the dispersive direction
           * Width of beam peak is proportional to A1900 p-acceptance in focus optics           * Width of beam peak is proportional to A1900 p-acceptance in focus optics
           * Width is narrower in match optics ​           * Width is narrower in match optics ​
           * Adjust anode HV to bring fuzzy maximum to around 600-700 channels (saturation of each pad at ~ 1000 ch)           * Adjust anode HV to bring fuzzy maximum to around 600-700 channels (saturation of each pad at ~ 1000 ch)
 +          * These are good spectra to check if the pad thresholds are properly set. Thresholds are too low if you see that all pads are firing at low energies. If that's the case, increase the pad thresholds in files **s800crdcv1.tcl** and **s800crdcv2.tcl**,​ under directory **s800/​operations/​daq/​usb/​Configs** (contact device physicist for assistance, if needed).
  
-      * Spectra **crdc1.anode_crdc1.tac** and **crdc2.anode_crdc2.tac** ​(top and middle spectra in the second column)+      * Spectra **crdc1.anode_crdc1.tac** and **crdc2.anode_crdc2.tac** ​
           * This spectrum is used to ensure that the field in the detectors is uniform and well aligned. If the detector is working properly, then the amplitude of the ANODE signals should not depend on the position of the beam (as shown in the figure below) ​           * This spectrum is used to ensure that the field in the detectors is uniform and well aligned. If the detector is working properly, then the amplitude of the ANODE signals should not depend on the position of the beam (as shown in the figure below) ​
           * If the field is not well aligned, then there will be a correlation between ANODE signals and TAC signals ​           * If the field is not well aligned, then there will be a correlation between ANODE signals and TAC signals ​
  
-     * Spectra **crdc1.x_crdc1.padsum** and **crdc2.x_crdc2.padsum** ​(top and middle spectra in the third column)+     * Spectra **crdc1.x_crdc1.padsum** and **crdc2.x_crdc2.padsum** ​
           * It shows the sum over multiple sampled signals from each pad along the (dispersive) x position ​           * It shows the sum over multiple sampled signals from each pad along the (dispersive) x position ​
           * The padsum signals should not show any correlation with the x (dispersive) position ​     ​           * The padsum signals should not show any correlation with the x (dispersive) position ​     ​
  
-      * Spectra **crdc1.xg_crdc1.tac** and **crdc2.xg_crdc2.tac** ​(top and middle spectra in the fourth column)+      * Spectra **crdc1.xg_crdc1.tac** and **crdc2.xg_crdc2.tac** ​
           * It shows the beam distribution in the dispersive (xg) //vs// non-dispersive (tac) directions           * It shows the beam distribution in the dispersive (xg) //vs// non-dispersive (tac) directions
           * It is used to ensure that the fragment beam is centered in the detectors           * It is used to ensure that the fragment beam is centered in the detectors
           * It is also used to see the effect of the beam blocker (used to stop intense contaminants) in the cocktail beam                  * It is also used to see the effect of the beam blocker (used to stop intense contaminants) in the cocktail beam       
   ​   ​
-      * Spectra **crdc1.xg** and **crdc2.xg** ​(bottom spectra in first and second columns)+      * Spectra **crdc1.xg** and **crdc2.xg** ​
           * It shows the position of the beam in the dispersive direction, evaluated by calculating the "​center of gravity"​. The peak should be in the middle of the spectra in order to center the beam           * It shows the position of the beam in the dispersive direction, evaluated by calculating the "​center of gravity"​. The peak should be in the middle of the spectra in order to center the beam
  
- +      ​* Spectra **crdc1.tac** and **crdc2.tac** ​
-      ​* Spectra **crdc1.tac** and **crdc2.tac** ​(bottom spectra in third and fourth columns)+
           * They correspond to the non-dispersive position of the beam in the CRDCs. ​           * They correspond to the non-dispersive position of the beam in the CRDCs. ​
 +
 +      * Spectra **crdc1.pad_mult** and **crdc2.pad_mult** ​
 +          * They show the distribution of pad multiplicies (i.e. number of pads firing for each event). Typical average values are ~10-15. Significantly larger average multiplicities might indicate that the thresholds are set too low.
  
 {{:​wiki:​CRDCS-example.png?​850|S800_CRDCS.win SpecTcl window}} {{:​wiki:​CRDCS-example.png?​850|S800_CRDCS.win SpecTcl window}}
  
 +
 +      * Check **[[s800 SpecTcl|Spectcl]]** window **S800_CRDCS_EFF.win** (see figure below) to verify the efficiency of the detectors. ​
 +         * Start a new run recording data on disk
 +         * Make a gate in spectrum **ic.sum** (top right plot) to select the Z region of interest, and call it **ic**
 +         * Make a summing region around the "​bananas"​ in spectra **crdc1.x.tac!ic** and **crdc2.x.tac!ic** (bottom left and right plots respectively)
 +         * Stop the run and rescan data from disk
 +         * Compare the number of event inside the 2D summing regions with the number of events inside the **ic** gate. Typically the former are very close to the later (nearly 100% efficiency for medium/high Z)
 +
 +{{:​wiki:​CRDCS-eff-015028.png?​550|S800_CRDCS_EFF.win SpecTcl window}}
  
 ==== Timing setup ==== ==== Timing setup ====
Line 185: Line 203:
  
   * If necessary, adjust delays of Phillips TDC (in principle, the TACs delays don't need to be adjusted):   * 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 (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)+      * 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 
       * Connect the XFP and/or OBJ signals going to the Phillips TDC (via cables plugged to patch #66 and #67, respectively) to 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/or XFP with respect to the TDC startusing 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 (~200 ns delay is good) 
-      * 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.+      * Check the corresponding ToF spectra ​in SpecTcl ​to confirm that the timings are properly adjusted.
  
   * Check the efficiencies of the Phillips TDC, TACs, and MTDC for the OBJ-FP and XFP-FP ToFs:   * Check the efficiencies of the Phillips TDC, TACs, and MTDC for the OBJ-FP and XFP-FP ToFs:
Line 304: Line 322:
   * Open the NCS application **QtKM** in the Applications Menu. Open file **BLSetup_A1900.gkm**. The magnetic elements that are typically tweaked with the knob box sitting on the left side of u6pc5 are **I232TA**, **I236TC**, and **I245TC** which can be found on page **S800 BLine+Spectrograph**. Other elements used to improve the focusing in the object point, and the transmission are **I172QA** and **I174QB**. The goal of the dispersion-matching tuning is to find a compromise between transmission and resolution.   * Open the NCS application **QtKM** in the Applications Menu. Open file **BLSetup_A1900.gkm**. The magnetic elements that are typically tweaked with the knob box sitting on the left side of u6pc5 are **I232TA**, **I236TC**, and **I245TC** which can be found on page **S800 BLine+Spectrograph**. Other elements used to improve the focusing in the object point, and the transmission are **I172QA** and **I174QB**. The goal of the dispersion-matching tuning is to find a compromise between transmission and resolution.
        ​{{:​wiki:​QtKM.png?​650|XG.}}        ​{{:​wiki:​QtKM.png?​650|XG.}}
-         * The two figures below show the spectrum **CRDC1.XG!FOI-AFP-BFP** before (top) and after (bottom) the dispersion-matching tuning for a typical experiment. Be aware that the width given by SpecTcl for the selected peak is not too reliable. It is more convenient to do a real gaussian fit. Unfortunatelly this is not an option included in the current version of SpecTcl. That's why some device physicists prefer SpecTk for this type of tuning+         * The two figures below show the spectrum **CRDC1.XG!FOI-AFP-BFP** before (top) and after (bottom) the dispersion-matching tuning for a typical experiment. Be aware that the width given by SpecTcl for the selected peak is not too reliable. It is more convenient to do a real gaussian fit. 
 {{:​wiki:​DispMatch-XG-run2.png?​650|XG before tuning.}} {{:​wiki:​DispMatch-XG-run5.png?​650|XG after tuning.}} ​ {{:​wiki:​DispMatch-XG-run2.png?​650|XG before tuning.}} {{:​wiki:​DispMatch-XG-run5.png?​650|XG after tuning.}} ​
  
Line 348: Line 366:
       * The auxiliary detector provides a secondary trigger that is fed into the S800 trigger system       * The auxiliary detector provides a secondary trigger that is fed into the S800 trigger system
       * A key part of setting up the S800 for such experiments is getting proper timing setup between the S800 and any auxiliary detectors       * A key part of setting up the S800 for such experiments is getting proper timing setup between the S800 and any auxiliary detectors
-      * For cases where the Secondary detector has a slow response relative to the S800, the coincidence timing must be reset to the S800 timing by delaying the S800 trigger using the third gate and delay generator on the trigger GUI+      * For cases where the Secondary detector has a slow response relative to the S800, the coincidence timing must be reset to the S800 timing by delaying the S800 trigger using the third gate and delay generator on the  ​[[S800 DAQ tools#​Trigger GUI|trigger GUI]]
           * A typical S800 delay for SeGA is 450 ns           * A typical S800 delay for SeGA is 450 ns
           * Probably smaller typical S800 delay needed for HiRA           * Probably smaller typical S800 delay needed for HiRA
Line 359: Line 377:
   
   * Setup   * Setup
-      * Coincidence signals are usually visible on scope without running scope in acquire mode+      * Using the [[S800 DAQ tools#​Trigger GUI|trigger GUI]], select (right-click) the wires going into the first AND GATE (see figure below) from the "​S800"​ and "​Secondary"​ (after passing through their respective "Gate & Delay Generators"​) ​  
 +      * Assign each wire to an inspect channel from the patch panel so that you can check their timings ​in the oscilloscope
       * Adjust the width of the early signal (S800 or secondary) should be wide enough to catch coincidences with the late signal (width of late signal is not critical)       * Adjust the width of the early signal (S800 or secondary) should be wide enough to catch coincidences with the late signal (width of late signal is not critical)
       * Readjust TDC delays based on changes made to S800 trigger delay       * Readjust TDC delays based on changes made to S800 trigger delay
Line 368: Line 387:
               * This check is required for verification in cases of low beam intensity (e.g. 1000 pps)               * This check is required for verification in cases of low beam intensity (e.g. 1000 pps)
           * Length of run required is typically about 10-15 minutes           * Length of run required is typically about 10-15 minutes
-          * To be resolved: ​ whether or not to this run copied from experiment account for documentation of device tuning+
   
 +
 +
 +{{:​wiki:​800px-TriggerGUI.png?​800|right|Trigger GUI}}
 +
   * Sample timing for running S800 with SeGA   * Sample timing for running S800 with SeGA
       * SeGA trigger is late with respect to S800 trigger       * SeGA trigger is late with respect to S800 trigger
tuning_the_s800_xdt.1495829206.txt.gz · Last modified: 2017/05/26 16:06 by pereira