Difference between revisions of "Compton Meeting, December 8, 2011"

From PolWiki
Jump to navigationJump to search
(New page: == Agenda == === Laser === # Entrance function analysis (maybe defer until Mark returns) === Photon Detector === # LED system # Analysis --> scripts? # Scanner detector - more results =...)
 
 
(One intermediate revision by one other user not shown)
Line 11: Line 11:
 
=== Electron Detector ===
 
=== Electron Detector ===
 
# Further commissioning
 
# Further commissioning
−
## List of tests
+
## Give CALIB to one side of each plane taking 1 minute run and making sure that everything is where it should be [=30 min] '*'
 +
## List of tests with full production beam and keeping all other parameters fixed at their currently used values
 +
### Perform a HV scan from -200 to -450 in steps of 75 V (should we do this?) [10 min @ each voltage] = 40 min
 +
### With full production beam perform a scan of pipeline delay [5 min @ each value; 3 values of either side of current optimum]=30 min
 +
### Perform a scan of the minimum width parameter [5 min @ each value; 3 values of either side of current optimum]
 +
### perform a scan of QWAD threshold [2 min run from 4.2V to 6.0V in steps of 0.2V] = 30 min
 +
### Set all of the above to the optimal parameters and vary event-trig to 4/4 & 2/4 while keeping accum-trig at 2/4
 +
## On one of the slaves, at the above optimum parameters check the chip-scope view of the data (take several snapshots)
 +
###with calibration input ~ 9 kel '*'
 +
###with 10 uA beam
 +
###with full production beam
 +
## From the hits spectra identify noisy strips and mask them if the background subtracted value is also flaky
 
## Schedule
 
## Schedule
 +
# Detector motion reproducibility: what's going on??
 
# Systematic uncertainties - it would be nice to start a summary document/report
 
# Systematic uncertainties - it would be nice to start a summary document/report
 +
 +
Notes:
 +
-------
 +
#'*' this can be done parasitically during any downtime.
 +
#For all the above tests, we don't need to disconnect anything at the detector or the v1495 end
 +
#For CALIB tests, we only need to plug in the function generator input and without disconnecting any other connection
 +
#It would take much less time to do the above tests if Green monster is enabled on our DAQ
  
 
=== Analysis ===
 
=== Analysis ===

Latest revision as of 14:11, 8 December 2011

Agenda

Laser

  1. Entrance function analysis (maybe defer until Mark returns)

Photon Detector

  1. LED system
  2. Analysis --> scripts?
  3. Scanner detector - more results

Electron Detector

  1. Further commissioning
    1. Give CALIB to one side of each plane taking 1 minute run and making sure that everything is where it should be [=30 min] '*'
    2. List of tests with full production beam and keeping all other parameters fixed at their currently used values
      1. Perform a HV scan from -200 to -450 in steps of 75 V (should we do this?) [10 min @ each voltage] = 40 min
      2. With full production beam perform a scan of pipeline delay [5 min @ each value; 3 values of either side of current optimum]=30 min
      3. Perform a scan of the minimum width parameter [5 min @ each value; 3 values of either side of current optimum]
      4. perform a scan of QWAD threshold [2 min run from 4.2V to 6.0V in steps of 0.2V] = 30 min
      5. Set all of the above to the optimal parameters and vary event-trig to 4/4 & 2/4 while keeping accum-trig at 2/4
    3. On one of the slaves, at the above optimum parameters check the chip-scope view of the data (take several snapshots)
      1. with calibration input ~ 9 kel '*'
      2. with 10 uA beam
      3. with full production beam
    4. From the hits spectra identify noisy strips and mask them if the background subtracted value is also flaky
    5. Schedule
  2. Detector motion reproducibility: what's going on??
  3. Systematic uncertainties - it would be nice to start a summary document/report

Notes:

  1. '*' this can be done parasitically during any downtime.
  2. For all the above tests, we don't need to disconnect anything at the detector or the v1495 end
  3. For CALIB tests, we only need to plug in the function generator input and without disconnecting any other connection
  4. It would take much less time to do the above tests if Green monster is enabled on our DAQ

Analysis

  1. Can we revert to old root tree structure?
  2. BPM calibrations (DG has some pedestals)
  3. BCM calibrations
  4. Edet analysis from root trees
Retrieved from "https://hallcweb-2024.jlab.org/polwiki/index.php?title=Compton_Meeting,_December_8,_2011&oldid=889"