Difference between revisions of "UCSD-2019: Cross-Cut: Readout/DAQ/Control Testing"

From CMB-S4 wiki
Jump to navigationJump to search
Line 18: Line 18:
 
* 8:45-9:00 SPT3G fMux DAQ (Sasha) [https://docs.google.com/presentation/d/1oz1cpAYTk8aFEhgeF2yJPYxXQCLurEuN_TbaOgI6A_4/edit?usp=sharing]
 
* 8:45-9:00 SPT3G fMux DAQ (Sasha) [https://docs.google.com/presentation/d/1oz1cpAYTk8aFEhgeF2yJPYxXQCLurEuN_TbaOgI6A_4/edit?usp=sharing]
 
* 9:00 - 9:15 BICEP mumux (Ed Y.) [https://drive.google.com/open?id=1CBfOWxz_6FaTsB3N0ZTLzSSHcip1NeaTvNSG6Melha8]
 
* 9:00 - 9:15 BICEP mumux (Ed Y.) [https://drive.google.com/open?id=1CBfOWxz_6FaTsB3N0ZTLzSSHcip1NeaTvNSG6Melha8]
* 9:15 - 9:30 SO mumux (Jack L.)
+
* 9:15 - 9:30 SO mumux (Jack L.) [https://docs.google.com/presentation/d/1u1QovfC_Snc3ge3omNs3ExMVCWOqgviGKpmOzHCoAjk/edit?usp=sharing]
  
 
== Remote attendance ==
 
== Remote attendance ==
  
 
== Notes ==
 
== Notes ==

Revision as of 09:42, 19 October 2019

Link back to agenda

Charge

What interfaces do we want/have between readout and DAQ? What does readout need from DAQ? What does DAQ need from readout? Do any of these items affect readout downselect?

Open Questions:

  • What do we need to have a data transport interface that meets our data loss requirements?
  • What quality of timing (1/f and jitter) do we need for readout noise requirements to be met? Can DAQ deliver this (at all or with the chosen transport technology)?
  • What integration complexity do we expect for readout control?
  • How do we coordinate development of readout control?
  • What is needed from DAQ for laboratory testing?

Agenda

  • 8:30-8:45 SPIDER TDM DAQ (Sasha) [1]
  • 8:45-9:00 SPT3G fMux DAQ (Sasha) [2]
  • 9:00 - 9:15 BICEP mumux (Ed Y.) [3]
  • 9:15 - 9:30 SO mumux (Jack L.) [4]

Remote attendance

Notes