sue-dataset-preparation

Prepare ML/HPC datasets with inode-safe formats and storage compliance checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-dataset-preparation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sue-dataset-preparation
Source: https://github.com/dongzhuoyao/deepresearch/tree/main/.codex/skills/sue-dataset-preparation
Command: npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-dataset-preparation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing datasets for large-scale ML/HPC experiments on HPC clusters often leads to inode quota exhaustion on parallel filesystems, misplaced datasets in invalid project directories, or sandbox accessibility failures that derail expensive experiment runs. This Skill eliminates those risks by enforcing strict storage, formatting, and validation rules tailored to each supported HPC backend.

Core Features & Use Cases

  • Inode-safe dataset formatting: Automatically recommends and implements LMDB, WebDataset tar shards, or SquashFS layouts to avoid metadata pressure on Lustre/GPFS parallel filesystems, instead of leaving datasets as millions of small individual files.
  • Backend-specific storage compliance: Enforces correct path rules for all supported HPC sandboxes (LUMI, Snellius, NM5, Brev, RunPod, AutoDL) to ensure datasets are stored in accessible, quota-valid locations rather than invalid project source trees or user home directories.
  • Preflight validation and budget checks: Runs space, inode, and accessibility probes before dataset preparation to catch quota shortfalls or path issues early, preventing wasted compute on failed experiment runs.
  • Use Case: A researcher preparing a 2TB ImageNet-scale dataset for a LUMI cluster can use this Skill to convert raw archives to LMDB to avoid inode exhaustion, verify the LUMI scratch quota has sufficient headroom, and write the final dataset path to the experiment runtime config for downstream training jobs.

Quick Start

Use the sue-dataset-preparation skill to convert your raw dataset archives to an inode-safe format, verify your target HPC sandbox's storage quotas, and record the final dataset path in your experiment runtime configuration.

Frequently Asked Questions about sue-dataset-preparation

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

FAQPage Schema
How do I prevent inode quota exhaustion when preparing large ML datasets on HPC parallel filesystems?

To prevent inode quota exhaustion on HPC parallel filesystems, convert raw dataset archives into inode-safe formats like LMDB, WebDataset tar shards, or SquashFS, which eliminates metadata pressure caused by storing millions of small individual files.

How do I verify my HPC sandbox has enough storage quota before running dataset preparation?

You verify HPC sandbox storage quota by running preflight validation and budget checks that probe available space and inode headroom before dataset preparation begins, preventing wasted compute on failed experiment runs due to quota shortfalls.

What is the best way to format datasets for LUMI or Snellius clusters?

The best way to format datasets for LUMI or Snellius clusters is applying backend-specific storage path rules alongside inode-safe formatting like LMDB or WebDataset to ensure datasets reside in accessible, quota-valid locations rather than invalid project directories.

Why does my sandbox accessibility fail when loading datasets on parallel filesystems?

Sandbox accessibility fails when datasets are misplaced in invalid project source trees or user home directories, violating backend-specific storage path requirements for HPC sandboxes like LUMI, Snellius, NM5, Brev, RunPod, and AutoDL.

Can I use SquashFS to avoid metadata pressure on Lustre or GPFS filesystems?

Yes, you can use SquashFS to avoid metadata pressure on Lustre or GPFS parallel filesystems, as it serves as an inode-safe formatting method that consolidates small files and prevents inode quota exhaustion during ML experiments.

How do I record the final dataset path for downstream training jobs on AutoDL or Brev?

You record the final dataset path for downstream training jobs by writing the verified, quota-compliant storage location into your experiment runtime configuration after completing dataset preparation, format conversion, and preflight validation probes.