snap-vis-loader

Extract coordinate data and metadata from GADGET-4 HDF5 snapshots.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hfoote/snap-vis --skill snap-vis-loader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snap-vis-loader
Source: https://github.com/hfoote/snap-vis/tree/main/.gemini/skills/snap-vis-loader
Command: npx skills add https://github.com/hfoote/snap-vis --skill snap-vis-loader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads GADGET-4 HDF5 snapshots and extracts coordinate data and metadata to enable fast, reliable 3D visualization.

Core Features & Use Cases

  • Efficiently load coordinate data from the Header and PartTypeX groups.
  • Return coordinates with shape (N, 3) and expose metadata such as BoxSize and Time for visualization pipelines.
  • Support subsetting by particle type and downsampling to maintain interactive performance.

Quick Start

Load the first GADGET-4 snapshot and extract coordinates and header metadata for visualization.

Frequently Asked Questions about snap-vis-loader

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

FAQPage Schema
How do I load GADGET-4 HDF5 snapshots for 3D visualization?

You can load and extract coordinate data and metadata from GADGET-4 HDF5 snapshots using h5py for efficient I/O, returning coordinates with shape (N, 3) and metadata like BoxSize and Time for visualization.

What is the best way to extract particle coordinates from GADGET-4 snapshots?

The best way to extract particle coordinates from GADGET-4 snapshots is by subsetting particle types from the PartTypeX groups, which allows you to isolate specific data and apply coordinate transformations for your visualization pipeline.

Can I subset particle types in GADGET-4 HDF5 files to improve interactive visualization performance?

Yes, you can subset particle types in GADGET-4 HDF5 files and apply downsampling to maintain interactive visualization performance, extracting only the necessary coordinate data from the specified PartTypeX groups.

Does this approach work across multiple GADGET-4 snapshots for time-series visualization?

Yes, this approach works across multiple GADGET-4 snapshots, allowing you to load and extract coordinate data and metadata sequentially to support time-series 3D visualization pipelines.

What metadata is available when loading GADGET-4 HDF5 files for visualization pipelines?

When loading GADGET-4 HDF5 files, the exposed metadata includes BoxSize and Time, which are extracted alongside the coordinate data from the Header group to support 3D visualization pipelines.

How do I handle coordinate transformations when extracting GADGET-4 snapshot data?

To handle coordinate transformations when extracting GADGET-4 snapshot data, the loading process supports transforming coordinates directly after reading them from the PartTypeX groups to align with your 3D visualization requirements.