Difference between revisions of "IntegrationDaq 220211"

Revision as of 23:21, 22 February 2022

Back to Main Page >> Data Acquisition Meetings >> Integrating mode DAQ meetings

previous meeting << >> following meeting

Meeting information

 Meeting time:  12:00pm Eastern
 
 Zoom connection information
 Join ZoomGov Meeting
 https://jlab-org.zoomgov.com/j/1603800887?pwd=aXVmSnN6aWZWN3RBdXB4RUhGckZJdz09
 
 Meeting ID: 160 380 0887
 Passcode: 903612
 US Tool free phone: (833) 568 8864
 Find your local number: https://jlab-org.zoomgov.com/u/ab8341cjcG

Agenda

• Activity updates
  • We have restarted the discussion of the integrator running modes we would like to have available, but is not final
• General discussion

Open Issues to be followed up later

1. Discussions with M. Pitt & J. Musson to understand the beam monitor signals we'll be getting
2. Draft timing diagram: DocDB 790
3. Michael, Bob, Brynne, and Paul should put together a list of the integrator running modes we would like to have available

Minutes

Recording at zoomgov: [https://jlab-org.zoomgov.com/rec/share/CZ_UGy6P_XBp6vP6DKwIKaLIVPgKiburxT_MEa8spBtfHMKKa1iP5XjDOCHrmB2P.iNqQ2NPlOSXDQvLQ

Meeting recording]

Participants: R. Michaels, B. Moffit, D. Bishop, B. Blaikie, W. Gu, P. King, M. Gericke

• Talking about the concept of the integrating ADC firmware DocDB 864
  • The delay between the trigger to the "Start of integration" will be done in the TI firmware within the module.
    • We can use either the leading edge or trailing edge of the Tsettle as the trigger to give us the most flexibility in defining the time
    • In an email after the meeting, Michael asks if we might need to have different delays for different channels, such as for beam monitors at different places along the beam line running into the same ADC board
  • Daryl points out that the ADC samples will be running all the time, and the trigger information is just flagging what to do with the samples, such as to integrate them or to store them as the waveform, etc.
    • Bryan asks if we could have some "lookback" or latency in the module such that we could actually accumulate samples from earlier than the trigger arrives
  • Talking about the subblocks
    • Our normal subblocks would be the time-ordered blocks, i.e. the first subblock is the first quarter of the helicity window, etc.
    • The interleaved subblock proposal would have every fourth sample accumulated in the same block, i.e. the first interleaved subblock would be samples 1, 5, 9, etc.
    • Bryan asks if the interleaved blocks are designed to look for a particular type of noise, or if there might be some better choice to pick out a type of noise; the answer is that these aren't specifically designed for a particular type of noise. This had been brought up at a collaboration meeting several years ago, and we don't recall right now if this was targeted at something specific