understanding-data-handling

Name: understanding-data-handling
Availability: InStock
Author: Mu2e

Explain the Mu2e data handling architecture, SAM-to-metacat/Rucio transition, and dCache storage flavors.

4|Updated Feb 11, 2026

Search Tags:#data architecture #data handling #sam #rucio #mu2e #dcache #metacat

Ready to run

npx skills add https://github.com/Mu2e/aitools --skill understanding-data-handling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: understanding-data-handling
Source: https://github.com/Mu2e/aitools/tree/main/skills/understanding-data-handling
Command: npx skills add https://github.com/Mu2e/aitools --skill understanding-data-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill demystifies the complex Mu2e data handling architecture, including its transition from SAM to metacat/Rucio, dCache storage, and file naming conventions, enabling users to effectively manage and locate data.

Core Features & Use Cases

Data Architecture Overview: Understand the SAM-to-metacat/Rucio transition and its implications.
dCache Storage Explained: Learn about the different dCache storage flavors (tape, persistent, scratch) and their use cases.
File Naming & Datasets: Master the strict six-field file naming convention and dataset definitions.
Tool Guidance: Get practical advice on using metacat, Rucio, and the mdh convenience layer.
Use Case: A new user needs to understand where simulation data is stored and how to access it. This Skill provides the necessary context on dCache, file naming, and the tools to locate and retrieve the data.

Quick Start

Explain the difference between the 'tape' and 'scratch' dCache storage areas.

Frequently Asked Questions about understanding-data-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How does the Mu2e data handling transition from SAM to metacat and Rucio work?▼

The Mu2e data handling transition shifts cataloging from SAM to metacat and data management to Rucio. This architecture upgrade changes how datasets are defined and located, requiring users to adopt metacat and Rucio for file retrieval instead of the legacy SAM system.

What is the difference between tape, persistent, and scratch dCache storage areas?▼

dCache storage areas differ by retention policy: tape provides long-term archival, persistent offers stable disk access, and scratch supplies temporary high-availability space. Users select the appropriate dCache flavor based on their data access frequency and simulation processing requirements.

How do I use metacat and Rucio to locate and retrieve Mu2e simulation data?▼

To locate and retrieve Mu2e simulation data, query dataset definitions through metacat and manage file transfers using Rucio. Users can also utilize the mdh convenience layer, which streamlines data management operations across both systems for efficient retrieval.

What are the file naming conventions for defining Mu2e datasets?▼

Mu2e datasets require a strict six-field file naming convention. Mastering this structure is essential for correctly defining datasets in metacat, ensuring accurate data cataloging and reliable file retrieval across the dCache storage system.

Do I need to know both metacat and Rucio to navigate Mu2e data architecture?▼

While knowing both metacat and Rucio provides complete control over Mu2e data architecture, users can also leverage the mdh convenience layer. This tool abstracts underlying complexities, simplifying data management and retrieval tasks without requiring deep expertise in both systems.