Difference between revisions of "IntegrationDaq 210922"

From Moller Wiki
Jump to: navigation, search
(Agenda)
(Minutes)
 
(6 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
Back to [[Main_Page|Main Page]] >>  [[DAQ Meetings|Data Acquisition Meetings]] >>  [[DAQ Meetings#Integrating mode DAQ meetings|Integrating mode DAQ meetings]]
 
Back to [[Main_Page|Main Page]] >>  [[DAQ Meetings|Data Acquisition Meetings]] >>  [[DAQ Meetings#Integrating mode DAQ meetings|Integrating mode DAQ meetings]]
  
[[IntegrationDaq_210813 | previous meeting]] <<  >> [[IntegrationDaq_210922 | following meeting]]
+
[[IntegrationDaq_210908 | previous meeting]] <<  >> [[IntegrationDaq_211103 | following meeting]]
  
 
== Meeting information ==
 
== Meeting information ==
Line 16: Line 16:
 
== Agenda ==
 
== Agenda ==
 
*  Touching back on prior topics
 
*  Touching back on prior topics
**  Status of port of CODA ROC to run on the SOM
+
**  What needs to be done to port CODA ROC to run on the SOM
 
**  What needs to be done to allow ~20us delays on making the integration start from TI signal?
 
**  What needs to be done to allow ~20us delays on making the integration start from TI signal?
 
**  Draft timing diagram: [https://moller.jlab.org/cgi-bin/DocDB/private/ShowDocument?docid=790 DocDB 790]
 
**  Draft timing diagram: [https://moller.jlab.org/cgi-bin/DocDB/private/ShowDocument?docid=790 DocDB 790]
Line 27: Line 27:
  
 
== Minutes ==
 
== Minutes ==
''Recording on Bluejeans.com:''   
+
''Recording on Bluejeans.com:''  [https://bluejeans.com/s/XYSnwWd1xVL]
  
Participants:
+
Participants: P. King, B. Moffit, M. Goodrich, J. Fast, W. Gu, B. Blaikie, M. Gericke, J. Pan, D. Bishop
 +
 
 +
*  Next step for CODA ROC:  compile ROC for ARM64 & test TI connection
 +
*  Allowing ~20us delays on making integration start from TI:  William says this will require a TI firmware change, but should be fairly straightforward
 +
*  Activity updates
 +
**  Michael:  getting ready for the Mainz beam tests.  Set-up is 11Oct with the beam time 14-18Oct
 +
*** The 16-channel boards are due to arrive next week
 +
**  Brynne:  working on making housings to hold base and preamp together.
 +
*  Discussion of my slides for the review
 +
**  HVMAPS may require a more powerful FPGA than the integrators, but it should still work with the TI-FMC
 +
**  Jim recommends to have a slide to define the acronyms used in the talk

Latest revision as of 14:28, 3 November 2021

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

previous meeting << >> following meeting

Meeting information

 Meeting time:  3:00pm Eastern
 
 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560 
 Other BlueJeans access phone numbers are listed at https://www.bluejeans.com/premium-numbers
 
 Bluejeans CODE:                    385 600 867
 Bluejeans link: https://bluejeans.com/385600867

Agenda

  • Touching back on prior topics
    • What needs to be done to port CODA ROC to run on the SOM
    • What needs to be done to allow ~20us delays on making the integration start from TI signal?
    • Draft timing diagram: DocDB 790
  • Activity updates
  • 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

Minutes

Recording on Bluejeans.com: [1]

Participants: P. King, B. Moffit, M. Goodrich, J. Fast, W. Gu, B. Blaikie, M. Gericke, J. Pan, D. Bishop

  • Next step for CODA ROC: compile ROC for ARM64 & test TI connection
  • Allowing ~20us delays on making integration start from TI: William says this will require a TI firmware change, but should be fairly straightforward
  • Activity updates
    • Michael: getting ready for the Mainz beam tests. Set-up is 11Oct with the beam time 14-18Oct
      • The 16-channel boards are due to arrive next week
    • Brynne: working on making housings to hold base and preamp together.
  • Discussion of my slides for the review
    • HVMAPS may require a more powerful FPGA than the integrators, but it should still work with the TI-FMC
    • Jim recommends to have a slide to define the acronyms used in the talk