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.