Difference between revisions of "Meeting-3-1-2018"

From GlueXWiki
Jump to: navigation, search
(Created page with "March 1, 2018 Drift Chamber meeting = Connection = # [https://halldweb.jlab.org/wiki/index.php/Connect_to_Bluejeans_Meetings Instructions for Bluejeans meeting connection] #...")
 
m (CDC gas issues)
 
(8 intermediate revisions by 2 users not shown)
Line 12: Line 12:
  
 
# Current run analysis/issues:
 
# Current run analysis/issues:
#*
+
#* CDC thresholds
#*
+
#* CDC gas issues
#*
+
#* FDC [http://www.jlab.org/Hall-D/detector/fdc/spring2018run/Charge_vs_driftime.pdf average charge vs drift time]
 
# Tracking
 
# Tracking
 
# fADC125
 
# fADC125
 
# Other
 
# Other
  
<!--
 
  
 
= Minutes =
 
= Minutes =
Line 25: Line 24:
 
Participants: Naomi (CMU) Eugene, Beni, Alex B., Simon, Sergey, Alex A., and Lubomir (JLab).
 
Participants: Naomi (CMU) Eugene, Beni, Alex B., Simon, Sergey, Alex A., and Lubomir (JLab).
  
== Status and current run analysis ==
+
= Discussions about the current run =
  
= CDC =
+
== CDC thresholds ==
  
- We discussed the settings for higher current running (up to 300nA) tomorrow (Fri 01/26/18). Eugene: we need the same conditions as for the normal running and if the chambers trip we will lower the beam current. Naomi proposed to lower the CDC HV of the inner HV sector (4 inner rings) from 2125 to 2025 so that they have current similar to the outer rings. Eugene wants to postpone this studies for later time when we have enough statistics and have dedicated studies of the DAQ rates and detector performance at higher fluxes.
+
- Naomi proposed several options: setting the CDC thresholds from the widths of the pedestal, scaling the current thresholds, or doing dedicated threshold scan with 4 different thresholds same for all straws.
 +
After lengthy discussions that included all kind of topics, we agreed that it is worth doing the threshold scan but after we figure out what is going on with the CDC gas leakage. Initially, the observable to be optimized was signal/noise as taken from the amplitude spectrum (if you can fit the noise and the signal reliably). At the end of the discussion we concluded that it is better to have enough statistics to get the rho yields (like 10M triggers per setting). Sergey pointed out that we should not really be calling the initial "noise" peak "noise".  With the cosmics runs we see a real noise peak from the electronics - the earlier threshold scan would have set the thresholds to make this noise level acceptable.  What we are seeing now is (presumably non-hadronic) background.    Later addition from Naomi: it would be best to do the threshold scan when the atmospheric pressure is stable, so that the changing gain does not confuse the analysis.
  
- Naomi and Beni looked at the fADC thresholds - no need to be changed.
 
  
- Naomi has issues with her plugin for gain calibration. Using the same data and plugin now it gives different results: less hits in the outer layers, compared to earlier analysis in spring/summer of 2017. Simon will look into that.  
+
- Beni: excluding the hits with times before the expected signal may improve the tracking (the wire-based one) and then the effect of the threshold may not be so important. Simon will re-analyze the two runs that Justin used to compare the rho yields with different thresholds, using a more appropriate software time window on the CDCdigihits.
  
= FDC =
+
== CDC gas issues ==
  
- Lubomir showed results from straight track runs. In total we had ~120M events, among them ~6M straight tracks with high quality. Alex B. will contact Mike Staib to see if that's enough for his Millipede alignment. We may ask for additional time at the end of the run if needed. The projection of the tracks on FCAL (plot at page 1) shows the exclusion of the inner FCAL blocks (4 on each side, making box 40x40 cm) visible on the plot. What is not understood are the four hot FCAL blocks inside that box, that were supposed to be excluded from the trigger.
+
- Naomi showed amplitude spectra for different regions of the drift time spectrum and compare them for runs in December and now. Her conclusion is that we are losing some charge, possible due to oxygen contamination in the gas as Beni suggested this morning. On Monday during the access Lubomir will measure the O2 contamination. We will also sniff around the CDC. If needed we may increase the flow and re-measure the O2.
The wire residuals (page 3) will be compared with previous straight track runs in 2016.
+
  
- Alex B. is in contact with Mike and wants to further improve the chamber alignment using Mike's code.
+
- Lubomir showed the average charge vs drift time for the FDC that is indicative of electron losses due to electronegative contamination. The relatively small slope was always there and is related to the way the charges are collected by the electronics, also because only one peak is readout. Important is to compare such plot for the CDC for runs in December and now.
  
- HV scan runs were analyzed by Lubomir using his straight track code limiting the analysis to small (<6deg) angles where the tracks are almost straight. The hit efficiency vs HV shows that with the nominal HV of 2225V we are well in the plateau (page 4). For the high intensity studies we should stay the DAQ limit and lower the HV till the current in the chamber is acceptable. As shown on the last plot, the loss of efficiency will not be significant.
+
= fADC125 =
  
- Alex A. also analyzed the scan runs with his plugin and showed that the loss of the efficiency for lower HV happens first at bigger drift distances (see plot attached).
+
- Cody is working on implementing multi-peak mode. The way it works now, without comparing to the threshold, is not very useful. Naomi: only the first peak is calculated precisely. We will still have to be very careful with the thresholds.  Lubomir: Still, having second is better than nothing. Eugene; the best is to use raw mode and evaluate all these effects. It should be done with the nominal high current even with a dead time close to 100%. We plan to have such run with ~10M trigger.
 
+
- Lubomir discussed the investigation of the HV sector in package 3 cell 4, that doesn't hold HV. By measuring the currents of both positive and negative HV after applying separately positive and negative voltage up to 50V we see that there's an ohmic resistance of 0.5MOhm on the positive and 1MOhm on the negative HV.
+
Each wire has 1MOhm at the HV side, thus the 0.5Mohm can be explained by a broken wire that touches another sense wire and goes to ground on the strips. However the negative HV sector has a common 10KOhm and it is difficult to explain the 1MOhm seen on the negative HV. More studies will be done after the run.
+
 
+
== Other ==
+
 
+
- Next meeting on Feb. 15, will discuss the collaboration meeting talks.
+
 
+
-->
+

Latest revision as of 21:16, 2 March 2018

March 1, 2018 Drift Chamber meeting

Connection

  1. Instructions for Bluejeans meeting connection
  2. Meeting ID: 290664653

Headline text

  1. To join via a Web Browser, go to the page [1] https://bluejeans.com/290664653.

Agenda

  1. Current run analysis/issues:
  2. Tracking
  3. fADC125
  4. Other


Minutes

Participants: Naomi (CMU) Eugene, Beni, Alex B., Simon, Sergey, Alex A., and Lubomir (JLab).

Discussions about the current run

CDC thresholds

- Naomi proposed several options: setting the CDC thresholds from the widths of the pedestal, scaling the current thresholds, or doing dedicated threshold scan with 4 different thresholds same for all straws. After lengthy discussions that included all kind of topics, we agreed that it is worth doing the threshold scan but after we figure out what is going on with the CDC gas leakage. Initially, the observable to be optimized was signal/noise as taken from the amplitude spectrum (if you can fit the noise and the signal reliably). At the end of the discussion we concluded that it is better to have enough statistics to get the rho yields (like 10M triggers per setting). Sergey pointed out that we should not really be calling the initial "noise" peak "noise". With the cosmics runs we see a real noise peak from the electronics - the earlier threshold scan would have set the thresholds to make this noise level acceptable. What we are seeing now is (presumably non-hadronic) background. Later addition from Naomi: it would be best to do the threshold scan when the atmospheric pressure is stable, so that the changing gain does not confuse the analysis.


- Beni: excluding the hits with times before the expected signal may improve the tracking (the wire-based one) and then the effect of the threshold may not be so important. Simon will re-analyze the two runs that Justin used to compare the rho yields with different thresholds, using a more appropriate software time window on the CDCdigihits.

CDC gas issues

- Naomi showed amplitude spectra for different regions of the drift time spectrum and compare them for runs in December and now. Her conclusion is that we are losing some charge, possible due to oxygen contamination in the gas as Beni suggested this morning. On Monday during the access Lubomir will measure the O2 contamination. We will also sniff around the CDC. If needed we may increase the flow and re-measure the O2.

- Lubomir showed the average charge vs drift time for the FDC that is indicative of electron losses due to electronegative contamination. The relatively small slope was always there and is related to the way the charges are collected by the electronics, also because only one peak is readout. Important is to compare such plot for the CDC for runs in December and now.

fADC125

- Cody is working on implementing multi-peak mode. The way it works now, without comparing to the threshold, is not very useful. Naomi: only the first peak is calculated precisely. We will still have to be very careful with the thresholds. Lubomir: Still, having second is better than nothing. Eugene; the best is to use raw mode and evaluate all these effects. It should be done with the nominal high current even with a dead time close to 100%. We plan to have such run with ~10M trigger.