Difference between revisions of "FA125 Data Format Aug 11, 2015"

From GlueXWiki
Jump to: navigation, search
(Agenda (to be updated, this is copied from the last meeting))
m (Text replacement - "http://argus.phys.uregina.ca/cgi-bin/private" to "https://halldweb.jlab.org/doc-private")
 
(14 intermediate revisions by one other user not shown)
Line 34: Line 34:
 
</div>
 
</div>
  
= Agenda (to be updated, this is copied from the last meeting)=
+
= Agenda =
 
* [[FA125_Data_Format_July_7,_2015|Previous meeting (July 7, 2015)]]
 
* [[FA125_Data_Format_July_7,_2015|Previous meeting (July 7, 2015)]]
* Status of FADC125 Firmware  
+
* FADC125 Firmware status
* Catch up on format spec changes
+
* Driver library status
** Field range for configuration parameters [[FA125_Data_Format_June_23,_2015#Proposed_field_range_for_configuration_parameters|previous minutes]]
+
* Mode names: CDC long/FDC short with amplitude, etc [[:File:FADC125_ADCmodes_v5_08.pdf|(See list)]]
** Diagrams added to format spec  
+
* Catch up on format spec since last meeting
 +
** Field range for configuration parameters unchanged [[FA125_Data_Format_June_23,_2015#Proposed_field_range_for_configuration_parameters|(See table in June minutes)]]
 +
** Latest version of format spec includes diagrams 
 +
** Added NE
 +
** Question on NPK>1 output in combo mode
 +
* Format spec still-to-do
 +
** Add table of time error codes
 +
* Testing plans
 +
* Next meeting
  
 
== Useful Info ==
 
== Useful Info ==
* [http://argus.phys.uregina.ca/cgi-bin/private/DocDB/ShowDocument?docid=2274 fADC125 Data Format Specification Document in DocDB - version 6]  
+
* [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=2274 fADC125 Data Format Specification Document in DocDB - version 6]  
 
* [[CDC_algo|Timing algorithm wiki page]]
 
* [[CDC_algo|Timing algorithm wiki page]]
 
* Older documents:
 
* Older documents:
Line 55: Line 63:
  
 
=Minutes=
 
=Minutes=
Present: Naomi (CMU), Cody, Beni (JLab)
+
Present: Naomi, Mike (CMU), David, Bryan, Cody, Lubomir, Beni (JLab)
#FA125 status: Cody received the new module from Naomi yesterday and is working to fit it into with the rest of the firmware, at present in simulationThe integration now takes place outside the timing module. The timing module was modified to output the number of the sample containing the leading edge as soon as this is found, so that the integration can start while the timing module is working on upsampling to find the pulse time more accuratelyNaomi will send Cody the new results for some test signals.
+
* FADC125 Firmware status - Cody has the short and long CDC modes working; with Beni he ran some tests to make sure that the output was as expected. The short mode ran at 120 kHZ with a random triggerNext they will try the long mode, and different configuration parameters.  
#Configuration parameter range: We are asking for any modifications to the proposed range to be provided by the end of this week. After then, Cody will start working them into the firmware and send them to Bryan for the driver.
+
* Driver library status - Bryan reported that the driver is ready, and available on his git repository as branch release-2.0.1This includes redefined arguments for fa125procmode and incorporates the new parameter names and functions for setting and retrieving timing thresholds and scaling factors, etc.  
#Data types: The list has been consolidated with the unused types moved to the end (see the meeting agenda).
+
* Mode names: We decided to stick with the names CDC long/FDC short with amplitude, etc [[:File:FADC125_ADCmodes_v5_08.pdf|(See list)]] but will have to renumber some of the data types to maintain consistency between the new and old data. David emailed that data type numbers 5,6,9,11 and 12 are available as these have not been used for the FA125 (some were defined but not used).
#ADC modes: We had a brief discussion about the proposed mode names in [[:File:FADC125_ADCmodes_v5_08.pdf|ADC modes (pdf)]]. Cody will talk to Bryan to find out if this is workable and if he has any other suggestions. The main aim is to avoid confusion between ourselves and between the FA125 and FA250 modes.
+
* Catch up on format spec since last meeting
#Integration: the new meaning of parameter IE is the count of samples in the integration, starting with the pulse leading edge, and not the original hit threshold crossingIntegration stops when either IE samples have been summed, or sample WE is reached. Some examples are given in the meeting agenda.
+
** The field range for configuration parameters was unchanged.[[FA125_Data_Format_June_23,_2015#Proposed_field_range_for_configuration_parameters|(See table in June minutes)]]
#Error codes: We are not sure how useful it would be to be able to identify the different error cases offline, but giving them a unique error code is harmless and might be useful later. We changed the proposed amendment to the following
+
** The latest version of format spec includes diagrams 
##ADC value of 0 anywhere in NSAMPLES buffer: q=1, t=10*TC-29 (time ends in 1)
+
** The configurable parameter NE is required in place of the hard-coded 6 to prevent the subset of samples required by the timing algorithm from extending past the end of the data window6 was sufficient for the number of samples NU=15 and threshold crossing sample X=9, but making NU configurable requires a configurable parameter (NE) in place of '6'.
##ADC value > LIMIT_PED_MAX (511) in 0 to PED_SAMPLE: q=1, t=10*TC-28 (time ends in 2)
+
** NPK>1 output should be removed from the CDC combo mode as we will not use it
##All ADC values in buffer < high timing threshold: q=1, t=10*TC-27 (time ends in 3)
+
** An extra word containing NW and number of peaks found is needed for the long (combo) modes. It was suggested either to add that word as the second word in the data format (before the peak data and before the raw samples), or to use the 250 data format for raw samples.  
##Low timing threshold found between samples TCL and TCL+1 but too late in buffer to upsample: q=1, t=10*TCL+4 (time ends in 4)
+
* Next meeting - to be decided, either Aug 25 at 2.30 or the following week at 1.30.
##Low timing threshold found between samples TCL and TCL+1 but any upsampled value < 0: q=1, t=10*TCL+5 (time ends in 5)
+
Postscript: Next meeting will be Tuesday Aug 25 at 2pm
##Low timing threshold found between samples TCL and TCL+1 but not found in upsampled data: q=1, t=10*TCL+9  (time ends in 9)
+
#Diagrams: Naomi will update the 2nd and 3rd figs in the following plot to include in the file spec.
+
{| border="0" cellpadding="2"
+
|[[Image:cdc_old_time_diagram.png|thumb|x80px|from May meeting]]
+
|}
+

Latest revision as of 17:04, 24 February 2017

Location and Time

Room: CC F326

Time: 3pm.

Remote Connection

You can connect using BlueJeans using the meeting number 589 693 655 .       (Click "Expand" to the right for more details -->):

(if problems, call phone in conference room: 757-269-6460 might not be the correct number)

  1. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 589693655.
  2. To join via a Web Browser, go to the page [1] https://bluejeans.com/589693655.
  3. To join via phone, use one of the following numbers and the Conference ID: 589693655
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560

More information on connecting to bluejeans is here

Specific instructions for connecting via polycom:

  • Turn polycom on if necessary
  • With the polycom, place a call at 199.48.152.152
  • Press # to enable the polycom keypad, then enter the meeting id: 589693655 and #
  • You may have to unmute the microphone: #*4
  • Turn the computer on if needed

Agenda

  • Previous meeting (July 7, 2015)
  • FADC125 Firmware status
  • Driver library status
  • Mode names: CDC long/FDC short with amplitude, etc (See list)
  • Catch up on format spec since last meeting
    • Field range for configuration parameters unchanged (See table in June minutes)
    • Latest version of format spec includes diagrams
    • Added NE
    • Question on NPK>1 output in combo mode
  • Format spec still-to-do
    • Add table of time error codes
  • Testing plans
  • Next meeting

Useful Info

Minutes

Present: Naomi, Mike (CMU), David, Bryan, Cody, Lubomir, Beni (JLab)

  • FADC125 Firmware status - Cody has the short and long CDC modes working; with Beni he ran some tests to make sure that the output was as expected. The short mode ran at 120 kHZ with a random trigger. Next they will try the long mode, and different configuration parameters.
  • Driver library status - Bryan reported that the driver is ready, and available on his git repository as branch release-2.0.1. This includes redefined arguments for fa125procmode and incorporates the new parameter names and functions for setting and retrieving timing thresholds and scaling factors, etc.
  • Mode names: We decided to stick with the names CDC long/FDC short with amplitude, etc (See list) but will have to renumber some of the data types to maintain consistency between the new and old data. David emailed that data type numbers 5,6,9,11 and 12 are available as these have not been used for the FA125 (some were defined but not used).
  • Catch up on format spec since last meeting
    • The field range for configuration parameters was unchanged.(See table in June minutes)
    • The latest version of format spec includes diagrams
    • The configurable parameter NE is required in place of the hard-coded 6 to prevent the subset of samples required by the timing algorithm from extending past the end of the data window. 6 was sufficient for the number of samples NU=15 and threshold crossing sample X=9, but making NU configurable requires a configurable parameter (NE) in place of '6'.
    • NPK>1 output should be removed from the CDC combo mode as we will not use it
    • An extra word containing NW and number of peaks found is needed for the long (combo) modes. It was suggested either to add that word as the second word in the data format (before the peak data and before the raw samples), or to use the 250 data format for raw samples.
  • Next meeting - to be decided, either Aug 25 at 2.30 or the following week at 1.30.

Postscript: Next meeting will be Tuesday Aug 25 at 2pm