Difference between revisions of "Minutes-11-3-2016"

From GlueXWiki
Jump to: navigation, search
(Agenda)
 
(3 intermediate revisions by the same user not shown)
Line 19: Line 19:
 
# fADC125 (Naomi, Cody, Beni)
 
# fADC125 (Naomi, Cody, Beni)
 
# Other
 
# Other
 
<!--
 
  
 
= Minutes =
 
= Minutes =
  
Participants: Sean (NU), Curtis, Naomi, Mike (CMU) Eugene, Luke, Paul, Chris, Beni, Alexander A., Simon, Sergey, and Lubomir (JLab).
+
Participants: Naomi (CMU) Fernando, Eugene, Cody, Alexander A., Simon, Beni, Mike, and Lubomir (JLab).
  
== Collaboration meeting ==
+
== Preparation for the fall 2016 run ==
  
- Simon will (have to) have a talk on the collaboration meeting in the tracking section, taking the Paul's slot.  
+
- Naomi and Beni are looking at the latest CDC data. Cody: there's an issue with one module in the CDC4 crate.
 +
 
 +
- Lubomir is analyzing the FDC data from the latest run 21050. Sasha excluded FDC6 and FDC11 for this run due to problems with them, but Cody tested them with his own code and they are fine, suspect software problem.
 +
 
 +
- after the spring 2016 run, Beni stopped the alcohol to be mix in the gas for both CDC and FDC and will put it back next week.  
  
 
== Tracking ==
 
== Tracking ==
  
- Paul plotted "measured-missing" pi momentum (log entry above) showing that there's 20% offset in the measurements at small (FDC) angles. => Something's wrong with analysis version 2.  
+
- Mike showed the timing calibrations for the FDC fADCs and TDCs (plots linked above). The fADC time variations with the runs are due to changes in the look-back parameter that Sasha played with during the running. The TDC time is with respect to TI and jumps by 4ns, but for all detectors, so relatively it doesn't matter. However, Beni found found that once the TI timing (same for all the detector crates) was different from the timing of the trigger crate for some runs.  
  
- Simon presented extensive study (linked above) of the tracking resolution based on pull distributions with MC for different momenta ranging from 0.25 to 4 GeV. He also used Paul's method for rho production and missing pi momentum to study the tracking resolution. Main observations:
+
- Mike made a presentation (linked) on his studies of the CDC/FDC transition region. He used straight tracks through the FDC and looked at the residuals w.r.t. the CDC wires. This is the procedure used by Lubomir to find the CDC offsets w.r.t. FDC except that Mike used the standard Simon's tracking. Mike showed there's ~20% more tracks in the 10-30 deg region after applying the offsets. These offsets will be included for the next analysis run.
  
-- poor tracking efficiency for theta < 40deg (0.25GeV) and <20deg (1-4 GeV), and at the same time some systematic deviations from the thrown momentum projections - not clear why (this is MC!). However no bias seen in the total momentum.
+
== f125 ==
  
-- some modulations in the errors of the track parametrization parameters with phi, but the mean values are OK.
+
- Cody is fixing some issues in the timing algorithm pointed out by Naomi. He's replacing a module in CDC4. He doesn't see issues with FDC6 and FDC11 when tested with his soft. Sasha could use these two crates in the last cosmic run.
 
+
-- using MC doesn't see Paul's problems with real data.
+
 
   
 
   
 
== Other ==
 
== Other ==
  
- Next meeting in three weeks.
+
- Next meeting in two weeks if not too much busy with the run.
 
+
-->
+

Latest revision as of 18:47, 7 November 2016

November 3, 2016 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. Preparation for the fall 2016 run
    • CDC (Beni/Naomi/Mike)
    • FDC (Lubomir)
  2. Tracking
  3. fADC125 (Naomi, Cody, Beni)
  4. Other

Minutes

Participants: Naomi (CMU) Fernando, Eugene, Cody, Alexander A., Simon, Beni, Mike, and Lubomir (JLab).

Preparation for the fall 2016 run

- Naomi and Beni are looking at the latest CDC data. Cody: there's an issue with one module in the CDC4 crate.

- Lubomir is analyzing the FDC data from the latest run 21050. Sasha excluded FDC6 and FDC11 for this run due to problems with them, but Cody tested them with his own code and they are fine, suspect software problem.

- after the spring 2016 run, Beni stopped the alcohol to be mix in the gas for both CDC and FDC and will put it back next week.

Tracking

- Mike showed the timing calibrations for the FDC fADCs and TDCs (plots linked above). The fADC time variations with the runs are due to changes in the look-back parameter that Sasha played with during the running. The TDC time is with respect to TI and jumps by 4ns, but for all detectors, so relatively it doesn't matter. However, Beni found found that once the TI timing (same for all the detector crates) was different from the timing of the trigger crate for some runs.

- Mike made a presentation (linked) on his studies of the CDC/FDC transition region. He used straight tracks through the FDC and looked at the residuals w.r.t. the CDC wires. This is the procedure used by Lubomir to find the CDC offsets w.r.t. FDC except that Mike used the standard Simon's tracking. Mike showed there's ~20% more tracks in the 10-30 deg region after applying the offsets. These offsets will be included for the next analysis run.

f125

- Cody is fixing some issues in the timing algorithm pointed out by Naomi. He's replacing a module in CDC4. He doesn't see issues with FDC6 and FDC11 when tested with his soft. Sasha could use these two crates in the last cosmic run.

Other

- Next meeting in two weeks if not too much busy with the run.