Difference between revisions of "February 1, 2012 Tracking CDC/FDC"

Revision as of 13:32, 1 February 2012

Meeting Time and Place

Wednesday February 1, 2012 at 11:00am At Jefferson Lab, the meeting will be held in F326

Connections

To connect from the outside, please use ESNET

1. ) ESNET: 8542553
   
2. )To connect by telephone, dial:

• You can look up toll-free number at http://www.readytalk.com/intl
• US and Canada: (866)740-1260 (toll free)
  
• International: (303)248-0285 (toll call)
• enter access code followed by the # sign: 3421244#
  

Hardware Agenda

1. Announcements
2. FDC Update logbook
3. CDC Update
   1. February 2012 GlueX-doc 1898

Tracking Software Agenda

1. Announcements.
2. Status of performance metrics.
3. Summary of current work on tracking.

Hardware Minutes

Participants: Curtis, Naomi, Dave, Mark, Eugene, Tim, Simon, Beni, Lubomir

1. FDC Update
2. CDC Update
   1. Stringing - this should be finished next week, there were 220 wires left to do this morning.
   2. HV - 500V is being applied to (one end of) each wire and the (very small) current measured.
   3. Resistance - now is a good opportunity to measure the resistance of each wire.
   4. Survey - wires need to settle for a week before finishing tension measurements. Tim will schedule the survey team between Feb 20 and March 5.
   5. Remaining hardware - the cheeseplate is on its way to CMU. Slava is working on the other hardware.
   6. Soldering - Kait and Amy are now expert at this.
3. Collaboration meeting
   1. One talk each will be scheduled for the CDC and FDC.

Software Minutes

The meeting started about five minutes early due to an early completion of the hardware meeting. Present at the meeting were: (CMU) N. Jarvis, P. Mattions and C.Meyer, (JLab) E. Chudakov, M. Ito, D. Lawrence, L. Pentchev, S. Taylor, B. Zihlmann (IU) R. Mitchell, K. Moriya, M. Shepherd (FSU) N. Sparks.

1. Performance Metrics:
   1. Simon reported on setting up an automated single track program similar to the the automated b1-pi program that now runs. This would run twice per week and allow us to track these more basic parameters. Mark is looking at this to make sure that he can get it to run before letting this go.
   2. Paul has some specific metrics that we can add to the single track code once it is running. Paul agreed to send this information to Kei who will implement it.
   3. Simon reported that currently about 1/2 of the reconstruction time is spent in the vertex section of the code---DVerteX Factory. This is even true for the single-track events. This factory caries out a Hough transform on the event to try and locate verticies.
2. Snapshot of Current Activity.