DUNE DAQ Firmware David Cussans Firmware Meeting 16Jan20

Goal • Demonstrate upstream DAQ functions in firmware before design review - Have implementation

Hit finding chain test - sim 6 Writing, documenting. Who? When? Input files, output

Hit finding chain test - Hardware 7 Writing, documenting. Who? When? Input files, output

Hit finding block - Simulation 8 Writing, documenting. Who? When? Input files, output files.

Hit finding core - Simulation 9 Writing, documenting. Who? When? Input files, output files.

Compression - Simulation Writing, documenting. Who? When? Input files, output files. Who? When? Verification

Infrastructure “ 33 b” Interface. Same for WIB data and hit output source in

10 s Buffer - Hardware Writing, documenting. Who? When? Input files, output files. Who?

Data Source on Fibre “Fake WIB” Include loop-back for testing For testing outside CERN?

Slides: 13

Download presentation

DUNE DAQ Firmware David Cussans Firmware Meeting 16/Jan/20 You Inst Logo

Goal • Demonstrate upstream DAQ functions in firmware before design review - Have implementation ready before May 2020 • 10 -second buffer • Hit finding • As first step, hit finding in Proto. DUNE - Best source of data - Must complete while Lar in detector • Currently planned – DAQ Mondays until 30/March/20 • 2 See https: //indico. fnal. gov/event/22704/contribution/1/material/slides/0. pdf for schedule Presenter Name | Presentation Title You Inst Logo

Full System 3 Presenter Name | Presentation Title You Inst Logo

Felix with Hit-Finding 4 Presenter Name | Presentation Title You Inst Logo

Hit finding chain test 5 Presenter Name | Presentation Title You Inst Logo

Hit finding chain test - sim 6 Writing, documenting. Who? When? Input files, output files. Who? When? Verification scripts. Who? When? Presenter Name | Presentation Title You Inst Logo

Hit finding chain test - Hardware 7 Writing, documenting. Who? When? Input files, output files. Who? When? Verification scripts. Who? When? Presenter Name | Presentation Title You Inst Logo

Hit finding block - Simulation 8 Writing, documenting. Who? When? Input files, output files. Who? When? Verification scripts. Who? When? Presenter Name | Presentation Title You Inst Logo

Hit finding core - Simulation 9 Writing, documenting. Who? When? Input files, output files. Who? When? Verification scripts. Who? When? Presenter Name | Presentation Title You Inst Logo

Compression - Simulation Writing, documenting. Who? When? Input files, output files. Who? When? Verification scripts. Who? When? 10 Presenter Name | Presentation Title You Inst Logo

Infrastructure “ 33 b” Interface. Same for WIB data and hit output source in hardware (Wibulator++ ) sink in hardware Probably best a README. md in Gitlab, pointed to by Twiki. Python routines for easy access 11 Written by Simone Documentation. Erdem sink/source in simulation Alessandro Who? Presenter Name | Presentation Title You Inst Logo

10 s Buffer - Hardware Writing, documenting. Who? When? Input files, output files. Who? When? Verification scripts. Who? When? 12 Presenter Name | Presentation Title You Inst Logo

Data Source on Fibre “Fake WIB” Include loop-back for testing For testing outside CERN? Who? When? Verification scripts. Who? When? 13 Presenter Name | Presentation Title You Inst Logo