understanding-data-handling

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.

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.

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.

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.

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.