Dune Database bi-weekly meeting

Wednesday 9 Jan 2019, 14:00 → 15:00 US/Central

Charles Lane (Drexel University), Norm Buchanan (Colorado State University)

Topic: DUNE Database Bi-Weekly Group Meeting Time: Mondays, 10:00 AM Central Time (US and Canada) Join from PC, Mac, Linux, iOS or Android: https://fnal.zoom.us/j/7302520319 Or iPhone one-tap : US: +16699006833,,7302520319# or +16465588656,,7302520319# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 Meeting ID: 730 252 0319 International numbers available: https://fnal.zoom.us/zoomconference?m=ZMNLflx1BTDtl6PdedwzCT6ePTU4_ugi Or an H.323/SIP room system: H.323: 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India) 213.19.144.110 (EMEA) 202.177.207.158 (Australia) 209.9.211.110 (Hong Kong) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) Meeting ID: 730 252 0319 SIP: 7302520319@zoomcrc.com

14:00 → 14:20 General

TDR, protoDUNE DB status, meeting schedule, plans

Speaker: Prof. Norm Buchanan (Colorado State University)

1. This time for meetings is okay
2. TDR:still rough, in progress
   1. slow control db size unclear, since protoDUNE db rates still in progress
   2. estimation discussion taken offline, ~10k channels to log?
3. Heidi: computing consortium went to BNL, Belle DB model was interesting
4. DUNE collaboration meeting planning, parallel session
5. Please look at/add to DB "technote", pre TDR; on Overleaf; invites need to go out
6. Jon will give talk at CERN meeting
7. Need more info on how to decode device data for use with DB.
8. problem getting attention to slow-control data before crisis develops
9. Look at data, guess what is reasonable, wait for complaints
10. Should get comparison of DB architectures & FNAL hosting, long term for DUNE
11. Hardware DB: experience with protoDUNE photon detection system; should implement an "example" (simpler) h/w DB to get started.
12. Slow control details (voltages, etc) NOT so much into run history database, more like summary data goes into run history db.