DUNE Phlex Project¶

Workflow reference and design proposals for DUNE’s migration from art to Phlex. The site collects six Phlex Adoption Working Group presentations on simulation and reconstruction, compares their data hierarchies, and records I/O requirements and proposed conventions. See Coverage and known gaps for areas still needing documentation.

Quick links¶

• Migrating to Phlex: the Phlex developers' guide to moving an art module to Phlex (separation, extraction, binding), with LArSoft's GausHitFinder as the worked example. Start here if you are migrating code.
• Workflow reference: what the six documented workflow presentations say about current production chains and Phlex-relevant needs.
• Hierarchy model: candidate data hierarchies and the evidence for each mapping.
• I/O, persistence, and associations: the separation between Window scheduling, cross-layer access, and persistent relationships through FORM.
• Existing art/FHiCL workflows: literal configurations and modules available as concrete migration and validation entry points.
• Conventions: DUNE-specific conventions being proposed for Phlex-era code (units, timestamps, Python), each marked with its actual adoption status.
• Ecosystem: dune-xerosere: Brett Viren's pathfinder umbrella environment for growing a DUNE ecosystem around Phlex.
• Migration status: dated milestones, benchmark plans, and migration scope.
• Coverage and known gaps: what the site covers well and which DUNE software areas are still missing.
• Repositories: the DUNE-org and Framework-R-D-org repos relevant to Phlex.

Who this is for¶

• New to Phlex and DUNE's migration to it: start with Workflow reference, then Migration status.
• Migrating an art module: follow the Phlex developers' Migrating to Phlex guide, and use Existing art/FHiCL workflows to pick a concrete starting module.
• Building Phlex or the DUNE software stack with Spack: see the companion DUNE Spack Project.
• Deciding how to structure data for your subsystem: read Hierarchy model alongside your own subsystem's page.
• Writing Phlex-era code and wondering what conventions to follow: Conventions, and note that most of what's there is proposed, not yet ratified.
• Looking for where the actual code lives: Repositories.

Related¶

• DUNE Spack Project: the companion site for Spack and MPD, which DUNE uses to build and develop Phlex-era software.
• Phlex framework documentation: the framework itself.

Status¶

Last verified: 2026-08-26. The workflow descriptions and design comparisons need review by the presenters and the Phlex Adoption WG before they can be used as authoritative guidance. Dates on individual pages identify the evidence available for each topic.