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/27 14:28]
pereira [Setting up Reaction Settings]
tuning_the_s800_xdt [2015/10/27 16:43]
pereira [CRDCs setup]
Line 18: Line 18:
       * Expected "open" values for top and bottom slits are CT ~6.8 and CB ~3.2, respectively        * Expected "open" values for top and bottom slits are CT ~6.8 and CB ~3.2, respectively 
  
-  * Ensure that CRAD04 (typically connected to object scintillator) is enabled with a rate limit of **20 kHz** (CRAD04 looks at E1 up FP scintillator)+  * Ensure that CRAD04 is enabled with a rate limit of **20 kHz** (CRAD04 looks at E1 up FP scintillator)
  
   * Remember: S800 FP rate limit is **6 kHz**   * Remember: S800 FP rate limit is **6 kHz**
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**+  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_SCINT.win** in directory **/user/s800/operations/spectcl/Windows**
  
   * 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 94:
  
  
-  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_IC.win**+  * Select **[[s800 SpecTcl|Spectcl]]** window **S800_IC.win** in directory **/user/s800/operations/spectcl/Windows** 
  
   * Adjust pad gains   * Adjust pad gains
Line 126: 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** (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** 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**)
  
       * 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 367: Line 368:
  
  
- 
- 
-====== Follow-up ====== 
- 
-  * Before leaving beam with experimenters 
-      * Set up current trip points on Linux HV controls 
-          * Values used for K-48 
-              * 5 for CRDC and Ion Chamber anodes and intermediate image ppacs 
-              * 50 for CRDC drifts 
-              * 80 for IC drift 
-          * Ensure alarms are running 
-              * Make sure Linux HV GUI alarms are enabled 
-              * Make sure threshold on isobutane level is set up (not currently connected to alarms because they give too many false alarms when communication is lost) 
-          * All logs are being recorded 
-              * There is no log file for biases controlled by Labview 
-              * Linux HV 
-              * LabView gas handling system 
-              * Note in logbook 
-                  * Scintillator biases 
-                  * IC gate biases 
-          * Post reference printouts for experimenters 
-              * HV status: a snapshot of HV GUI 
-              * Gas handling system status: a snapshot of LabView window 
- 
-  * Create window configuration with summing regions to make it easier for experimenters to track efficiency/performance of all detectors 
- 
-  * Setting up coincidences for additional reaction settings in an experiment 
-      * Do not need to redo coincidence settup if secondary beam does not change 
-      * Might need to redo coincidence setup if secondary beam changes drastically 
- 
-  * To watch during experiment 
-      * Look for isobutene running out – messes up data over several hours 
- 
-  * Implementing dE- or TOF-based corrections is part of EXR  
- 
-More detail needed 
- Minimum rates required for coincidence setup 
- Selection of appropriate substitute reactions for coincidence setup 
- How to feel comfortable that there will not be a problem with FP detector gases running out 
- Starting alarms 
- Starting logging 
  
  
  
tuning_the_s800_xdt.txt · Last modified: 2023/09/22 15:15 by swartzj