DELPHI + EDM4hep

DELPHI event display

DELPHI events straight from edm4hep — no DELGRA, no X11, no ROOT. Drawn with Plotly, and it runs in your browser.

Open the event display → A showcase event loads immediately; drop your own .edm4hep.root file to explore any event. Documentation → Install, command line, collections and roles, what is drawn, the decoding rules, Python API.

What it does

Opens any DELPHI edm4hep file, in the browser. Drop a file on the display and uproot reads it locally under Pyodide — nothing is uploaded, and there is no server behind this page.

Nothing is pinned by collection name. A DELPHI file holds 3 Track collections, 7 Vertex, 4 Cluster, 2 TrackerHit3D and 24 ParticleID. The display discovers them from podio's own metadata and binds each part of the picture to one by role, which you can change. Beside the figure, every collection is listed with its type, domain, provenance, links and per-event count; select one and everything not from it dims, or click a track to select its collection.

Only measured quantities are drawn. Tracks are helices from their own perigee parameters, started at the vertex they belong to, with the back-extrapolation to the IP dotted so the picture never claims a path the particle did not travel.

In the 3-D scene this matters more, not less: a vertex-detector hit is a strip, so it constrains a line in space, not a point. Hits on a track are placed at the z their own track measures; hits on no track are drawn as the line they actually constrain.

Four panels, or the detector

From the command line

pip install -e .
delphi-display FILE.edm4hep.root --entry 3990 --out event.html --view both

See the command-line reference.