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
      RDB, protoDUNE, status, etc.
      Speaker: Prof. Norm Buchanan (Colorado State University)

      Attending: Norm, Chuck, Heidi, Jon, hajime

      Heidi: what are these variables?

      Norm: not slow controls, from FICL at run-time, list on wiki.

      Without webviewer to explore these variables in DB, can't tell how to use them.

      Jon: web viewer not that useful. Doesn't tell what they ARE.

      Norm: probably should improve wiki.

      Heidi: want type in run#, spits out values of parameters.

      Norm: will put up some instructions.

      J: slow controls indexed by time, not by run#.

      H: putting run-dependent info in every single file in SAM, not the best way to do it.  Also google spreadsheets

      Not sure that elog is 100% reliable. Flushed?  Can't see enough. Not sure how to scrape.

      J: there are web interface, no one has requested beyond that.

      H: from D0 RDB, so end users could select runs. Quality and stuff like that. Need to know for analysis.

      N: data quality from HV, etc?

      H: multiple quality multiple quality measures (DAQ, analysis, later stuff).

      N: n-bits?

      H: users don't want bit maps, just want "good/not"

      J: Nova, runs data base: run history, what was config, separate table for quality from quality group. SAM queries these tables.

      N: prefer separate DB for offline-derived quantities

      H: can add links to condb? ifbeam? etc.

      N: will see about this. Wiki pointers, examples.  Like different table for offline stuff.

      N: merging info from different DBs, like time-keyed vs. run-keyed.

      H: mapping time vs run a long-term project. Don't fret it.  Get on the list.

      N: getting google docs into new columns of RDB...?

      N: know enough about voltages to finish task of integrating into run history. Other slow controls not there yet.

      J: Nova calibrations: have range of run#s with calibration.

      H: huge step forward to use these variables.

      N: will try. Have roadmap. Need people?

      N: plan going forward, SP and DP: info only contained in CERN-side DB, only through elisa(?)

      Plan: document, add google sheet data into DB, example command-line access

      tidy up and finish up  slow controls

      Next topic: interest in HW and inventory DB is growing.  Several options, shouldn't have 3 parallel approaches. What to do? 

      N: separate meeting, ask about resources and support. W/principals of other efforts.

      N: must start getting ready for DUNE efforts.

      H: HW DB is part of project funding.  If no one has project funding for this, it won't happen.

      H: phone conf next week of US PI's to go to DOE ask for money 11AM Thurs MST  Marvin email

      H: Proj Mgt and tracking DB should be part of project budgets.