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))
(Agenda (to be updated, this is copied from the last meeting))
Line 37: Line 37:
 
* [[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  
 
* Status of FADC125 Firmware  
 +
* Driver library status
 
* Catch up on format spec changes
 
* Catch up on format spec changes
 
** Field range for configuration parameters [[FA125_Data_Format_June_23,_2015#Proposed_field_range_for_configuration_parameters|previous minutes]]
 
** Field range for configuration parameters [[FA125_Data_Format_June_23,_2015#Proposed_field_range_for_configuration_parameters|previous minutes]]
 
** Diagrams added to format spec  
 
** Diagrams added to format spec  
 +
* Format spec still-to-do
 +
** Add table of time error codes
 +
* Testing plans
  
 
== Useful Info ==
 
== Useful Info ==

Revision as of 11:50, 11 August 2015

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 (to be updated, this is copied from the last meeting)

  • Previous meeting (July 7, 2015)
  • Status of FADC125 Firmware
  • Driver library status
  • Catch up on format spec changes
    • Field range for configuration parameters previous minutes
    • Diagrams added to format spec
  • Format spec still-to-do
    • Add table of time error codes
  • Testing plans

Useful Info

Minutes

Present: Naomi (CMU), Cody, Beni (JLab)

  1. 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 simulation. The 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 accurately. Naomi will send Cody the new results for some test signals.
  2. 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.
  3. Data types: The list has been consolidated with the unused types moved to the end (see the meeting agenda).
  4. ADC modes: We had a brief discussion about the proposed mode names in 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.
  5. 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 crossing. Integration stops when either IE samples have been summed, or sample WE is reached. Some examples are given in the meeting agenda.
  6. 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
    1. ADC value of 0 anywhere in NSAMPLES buffer: q=1, t=10*TC-29 (time ends in 1)
    2. ADC value > LIMIT_PED_MAX (511) in 0 to PED_SAMPLE: q=1, t=10*TC-28 (time ends in 2)
    3. All ADC values in buffer < high timing threshold: q=1, t=10*TC-27 (time ends in 3)
    4. 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)
    5. 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)
    6. 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)
  7. Diagrams: Naomi will update the 2nd and 3rd figs in the following plot to include in the file spec.
from May meeting