Dune Database bi-weekly meeting

US/Central
Charles Lane (Drexel University), Norm Buchanan (Colorado State University)
Description
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 20m
      TDR, protoDUNE DB status, meeting schedule, plans
      Speaker: Prof. Norm Buchanan (Colorado State University)

      In attendence: Norm, Chuck, Kurt, Steve W, Hajime..

      Norm: message this morning, SAM run history DB interface is finished. Needs to be tested.

      Runs history database, some 'clock' related terms added recently. Should happen soon.

      How to connect new information, ifbeam? etc in run history DB?

      DP will want versions as well, DP phase sched June?  Get in advance if possible

       

      Going over M Verocchi's slides from DUNE collab mtg, Jan 19.

      DB central at FNAL? No clear overall plan for where it would hosted.

      Issue for ProtoDUNE: problem getting info from CERN, assistance at CERN end was needed.

      For DUNE, in addition, database needs might well be larger (calib, slow con)? HW/SW people needed  for that?

      Protodune effort: once communication that tools already existing and ready to use, THEN they quickly started being used; until then, people 'roll their own'.

      Have to commit to what should be used, what is supported, set boundaries.

      FNAL uses PostGres, CERN used MongoDB and Oracle?  need to collapse the wavefunction.

      If choice isn't obvious in a one hour discussion, then it probably doesn't matter; select and see how things stand in 6 months and re-evaluate.

      Hajime started on this, encourage continuation.  Ernesto Kemp on hardware info as well.
       

      Kurt: at offline meeting, request to get the window size? into run db?  Wondered if worth having 60 fields in DB from online data then somehow condense into some parameter? (different window size in different parts of detector).

      Norm: nervous about touching that stuff, like data conversions, etc.  Not necessary unreasonable, but precident might be a problem. Mission creep.

       

      60 numbers in, some algorithm, puts out one number out. It's an 'interpretation' of the data, rather than just storing and retrieving.

      Meet again in 2 weeks, test SAM by then.

      Slowcontrol db: existing conditions db would work for that? Norm will look for that.