Milestone #19034

Plan for Event Display

Added by Katherine Lato almost 3 years ago. Updated 3 days ago.

Event Display
Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)
Spent time:
(Total: 8.00 h)


Investigate having a new Event Display framework common to all experiments. Some important features:
  • Provides a simple, intuitive means to navigate through large events and multi-TPC detectors.
  • Ability to zoom and pan with a data density that matches the screen resolution.
  • Provides basic interfaces to art for controlling runs and events, the geometry service, run conditions services. Re-running reconstruction workflows and displaying the result should be possible.
    This work does not cover development of drawing routines. It is expected that the core event display users within the experiments will provide this code. Arrangements for this follow-on work will be part of this project.

The plan will be listed in a series of tasks for this milestone.


Task #19035: Create list of requirementsClosedKatherine Lato

Task #19036: Community input on requirementsClosedErica Snider

Task #19037: Establish criteria to judge between the optionsClosedErica Snider

Task #19038: Identify possible technologiesClosedPaul Russo

Task #19039: Compare technologiesClosed

Task #19040: Evaluate technologies based on criteriaClosedErica Snider

Task #19041: Plan for building the common infrastructure pieceClosedErica Snider


#1 Updated by Katherine Lato almost 3 years ago

  • Status changed from New to Assigned

#2 Updated by Katherine Lato over 2 years ago

  • Assignee changed from Katherine Lato to Erica Snider

#3 Updated by Katherine Lato 6 months ago

  • Status changed from Assigned to Resolved
Event Display options
The LArSoft event display strategy has changed from developing a common tool to providing adequate support for community developed and supported displays sufficient to allow community members to choose on their own. Here are the currently available options:
  1. LArSoft Event Display (ROOT based)
    In principle can display everything both in 2D and 3D
    Very slow for large detectors.
    Works for all detectors. Can display multiple data items and labels at once
  2. TITUS (Qt based)
    Combination of python (3) and C++ and is based on the PyQT5 interface.
    Updated version (by Marco Del Tutto and Gianluca Petrillo) of the event display originally authored by Corey Adams (QT based) for MicroBooNE
    Runs in gallery. Being used by ICARUS. Works for MicroBooNE, ArguNeut and possibly DUNE.
    Native 2D displays of low-level data
  3. WebEVD (using three.js/WebGL for access to OpenGL)
    Chris Backhouse developed
    In use at ProtoDUNE. Has been updating based on feature requests.
    Runs in LArSoft & Gallery.
    Doesn’t have a native 2D display.
    Requested to be a UPS product distributed with LArSoft.
  4. EVE based for SBND
    Umut Kose developed.
    3D Oriented,
    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.
    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)
    Developed by Chao Zhang for use with wire-cell.
    3D oriented.
    Uses three.js.
    Doesn’t run in LArSoft and Gallery, uses wire-cell data format, so requires conversion step
  6. Phoenix event display - Ed Moyse developing
    Experiment-agnostic display that relies on event serialization via JSON. It allows for a shared code base.

The issue tickets associated with the previous strategy will be closed, but can be re-opened should the need arise.

#4 Updated by Katherine Lato 3 days ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF