April 2020 Offline Leads Meeting Notes

Attendees: Tracy Usher, Tingun Yang, Erica Snider, Katherine Lato, Tom Junk (late)

LArSoft report

  Event Displays. Existing options 

  1. LArSoft Event Display (ROOT based)
    1. In principle can display everything both in 2D and 3D 
    2. Very slow for large detectors.
    3. Works for all detectors. Can display multiple data items and labels at once
    4. Request from ProtoDUNE to improve speed and better support for multiple TPCs (they still believe it is useful, easy to modify, etc). But plan to look at TITUS
  2. TITUS  (Qt based)
    1. Combination of python 3 and C++ and is based on the PyQT5 interface. 
    2. Updated version of the  event display supported by Marco Del Tutto and Gianluca Petrillo (originally authored by Corey Adams for MicroBooNE)
    3. Runs in gallery. Being used by ICARUS. Works for MicroBooNE, ArguNeuT and possibly DUNE. LArSoft would like to see this run in art environment also.
    4. Native 2D displays of low-level data
  3. WebEVD (using three.js/WebGL for access to OpenGL) 
    1. Chris Backhouse developed 
    2. In use at ProtoDUNE. Has been updating based on feature requests. 
    3. Runs in LArSoft & Gallery. 
    4. 3D oriented. Doesn’t have a native 2D display.
    5. Request to be a UPS product distributed w LArSoft. Plan to do this. 
  4. EVE based for SBND
    1. Umut Kose developed.
    2. 3D Oriented, 
    3. Study of using EVE for event display started after SBN workshop in 2019 at Fermilab. It aims to provide the functions of 3D and 2D projection views, animations, interactive display for users.
    4. Eve is a ROOT module based on experiment-independent part of the ALICE event display developed in cooperation between ALICE offline project and ROOT.
  5. Bee event display (based on WebGL)
    1. Developed by Chao Zhang for use with wire-cell.
    2. 3D oriented.
    3. Uses three.js.
    4. Doesn’t run in LArSoft or Gallery,  uses wire-cell data format, so requires conversion step
    5. Authors aiming at PR-level displays

On-going work

  • Supporting jenkins build of SBN online monitoring
  • Supporting work on spack build of LArSoft / ICARUS code to run on Theta machine.
    • Running on Theta is part of a goal to run on HPC more generally
    • Also exercising the spack stuff
  • Working on multi-threading for ProtoDUNE and ICARUS production workflows (data prep through hit-finding)
  • LArSoft now using art 3.05, so have started the process of introducing thread-safe service implementations
    • Kyle working on DetectorClocks and DetectorProperties

Tingjun – ProtoDUNE

  • Happy LArSoft is moving to TensorFlow 1.12 since it has made development work easier.
  • ProtoDUNE is preparing for a new release for production. Uses the refactorized LArG4 simulation. 
  • Things are going well. 

Tracy – ICARUS

  • Good news on database — got libwda going right way. Now able to access the database and that work is making progress. Don’t need to include extra packages that were initially requested.  Noted that they expect to be able to use the standard LArSoft services for reading the database in most cases. The new code is just for filling the DBs
  • There is a new SBN Data/Infrastructure group headed up by Wesley Ketchum and Joseph Zennamo that will be merging much of the SBND and ICARUS software efforts. Goal is to get everything into GitHub and adopt the same cmsbot scheme for pull requests and CI tests that LArSoft uses, etc. 
    • Suggested inviting Wes and Joseph to be part of this group since they are trying to make SBN to be like an experiment, rather than SBND and ICARUS alone. 

Tom Junk – DUNE

  • Noted that the DUNE offline people don’t always get to the requests promptly. Now commits hang in level 2 review state longer than they should, so commits take longer than they did in the past. But things were committed before without review. 
    • Noted that the reviews were a good thing. Just need to balance level of review versus need to get the code merged.
    • Concerned about a flurry of work showing up that overwhelms level 2 reviewers. 
      • By design, the system scales by adding level 2 approvers within the experiment. CMS does this with domain-specific level 2 reviewers. Suggested DUNE pursue this if needed to distribute the 2 responsibilities.
  • A 2×2 liquid argon pixel detector, ArgonCube/ProtoDUNE-ND, is coming online. That’s the only time pressure at present.
    • Discussed the software situation for that. Though the TDR work being carried out by LBL is in a different software framework, Tom believes the experiment will go with a more unified ND/FD software solution moving forward from there.

Please email Katherine Lato or Erica Snider for any corrections or additions to these notes.