Difference between revisions of "July 31, 2013 Tracking CDC/FDC"

From GlueXWiki
Jump to: navigation, search
(Minutes)
(Minutes)
Line 27: Line 27:
 
#FDC Update
 
#FDC Update
 
# CDC Update  
 
# CDC Update  
We are now reading out data from all 3 new fadcs successfully, data look fine, tracks aplenty.
+
#*We are now reading out data from all 3 new fadcs successfully, data look fine, tracks aplenty.
 
# Data Formats
 
# Data Formats
#*[http://argus.phys.uregina.ca/cgi-bin/public/DocDB/ShowDocument?docid=2274 fADC125 Data Format Document]
+
#*fADC125 Data Format Document
 
We decided to reinstate data type 5 (window raw data) for reading out pedestal data in the absence of a hit, and to use this instead of type 6, pulse raw data.  This leaves us with data types 5 (window raw data), 7 (pulse data) and 8 (combined - pulse data followed by raw data).  Window raw data would be used for configuration; pulse data would be the usual hit event readout; the combined format would facilitate algorithm development and monitoring.  
 
We decided to reinstate data type 5 (window raw data) for reading out pedestal data in the absence of a hit, and to use this instead of type 6, pulse raw data.  This leaves us with data types 5 (window raw data), 7 (pulse data) and 8 (combined - pulse data followed by raw data).  Window raw data would be used for configuration; pulse data would be the usual hit event readout; the combined format would facilitate algorithm development and monitoring.  
 
*David has already updated and redistributed the document.
 
*David has already updated and redistributed the document.
#*[[FADC_algorithm | FDC algorithm]]
+
#*FDC algorithm
 
The integration requirements for the 2 detectors are not identical - the CDC has pulses which can start at any time during a window of nearly 1us but all end at the same time, whereas the FDC pulses can start at any time during a shorter window, and are much shorter in duration.  There are benefits to having one firmware package which would be used for both FDC and CDC; this would work best if there could be software settings to specify that (eg) a certain process should be used for the FDC and another for the CDC.
 
The integration requirements for the 2 detectors are not identical - the CDC has pulses which can start at any time during a window of nearly 1us but all end at the same time, whereas the FDC pulses can start at any time during a shorter window, and are much shorter in duration.  There are benefits to having one firmware package which would be used for both FDC and CDC; this would work best if there could be software settings to specify that (eg) a certain process should be used for the FDC and another for the CDC.
#*[[CDC_algo | CDC algorithm]]
+
#*CDC algorithm
 
Beni is going to implement Naomi's timing algorithm for the FDC to see how it performs.
 
Beni is going to implement Naomi's timing algorithm for the FDC to see how it performs.

Revision as of 14:47, 31 July 2013

Meeting Time and Place

Wednesday July 31, 2013 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. Announcement
  2. FDC Update
  3. CDC Update
  4. Data Formats

Minutes

Present: Naomi, Beni, Simon, David, Cody

  1. FDC Update
  2. CDC Update
    • We are now reading out data from all 3 new fadcs successfully, data look fine, tracks aplenty.
  3. Data Formats
    • fADC125 Data Format Document

We decided to reinstate data type 5 (window raw data) for reading out pedestal data in the absence of a hit, and to use this instead of type 6, pulse raw data. This leaves us with data types 5 (window raw data), 7 (pulse data) and 8 (combined - pulse data followed by raw data). Window raw data would be used for configuration; pulse data would be the usual hit event readout; the combined format would facilitate algorithm development and monitoring.

  • David has already updated and redistributed the document.
    • FDC algorithm

The integration requirements for the 2 detectors are not identical - the CDC has pulses which can start at any time during a window of nearly 1us but all end at the same time, whereas the FDC pulses can start at any time during a shorter window, and are much shorter in duration. There are benefits to having one firmware package which would be used for both FDC and CDC; this would work best if there could be software settings to specify that (eg) a certain process should be used for the FDC and another for the CDC.

    • CDC algorithm

Beni is going to implement Naomi's timing algorithm for the FDC to see how it performs.