Mu2e
Official@mu2e · Batavia, IL
Fermilab Mu2e experiment
Agent Skills by Mu2e
Showing 10 vetted skills indexed across 1 GitHub repositories.
Mu2ecoding-with-fhicl
Author, review, and troubleshoot Mu2e FHiCL configuration files.
Mu2eunderstanding-data-handling
Explain the Mu2e data handling architecture, SAM-to-metacat/Rucio transition, and dCache storage flavors.
Mu2ebuilding-with-smack
Guide Mu2e Phase 3 builds using Spack and CMake commands.
Mu2ecoding-with-metacat
Query and manipulate Mu2e file metadata using the metacat Python API.
Mu2ecoding-with-query-engine
Construct Mu2e Query Engine URLs for PostgreSQL data access.
Mu2efinding-data-sam
Query the Mu2e SAM data catalog to find datasets, files, and initiate prestaging.
Mu2efinding-data-metacat
Query Mu2e datasets and files with metacat, Rucio, and mdh tools.
Mu2ebuilding-with-muse
Guide Mu2e software builds with Muse, Spack, and SCons.
Mu2ebuilding-offline-software
Build Mu2e offline software with SCons-based Muse and Spack-based Smack orchestrators.
Mu2ebuilding-agent-skills
Create self-contained AI agent skills following the agentskills.io standard.
Frequently Asked Questions About Mu2e
FAQPage SchemaWhat specific tasks are enabled by the Mu2e software ecosystem?▼
The ecosystem enables precise configuration of experiment parameters via FHiCL, management of large-scale datasets through SAM and Metacat, and the orchestration of complex offline software builds. It facilitates data retrieval from dCache storage and metadata manipulation within the Mu2e high-energy physics research environment.
Which personas are the primary users of these technical capabilities?▼
These capabilities are designed for particle physicists, research software engineers, and data analysts working within the Fermilab Mu2e experiment. Users typically manage high-volume experimental data, maintain offline software build environments, or perform complex queries against distributed metadata catalogs and PostgreSQL-backed data stores.
What are the core dependencies for building Mu2e offline software?▼
Building Mu2e offline software requires the Muse environment manager, the Spack package manager, and SCons for build orchestration. Users must also interface with the Metacat metadata service and the SAM data catalog to manage file prestaging and dataset discovery within the experiment's infrastructure.