h5py
A Pythonic interface to the HDF5 binary data format. It allows you to store huge amounts of numerical data and easily manipulate that data from NumPy. Features a hierarchical structure similar to a file system. Use for storing datasets larger than RAM, organizing complex scientific data hierarchically, storing numerical arrays with high-speed random access, keeping metadata attached to data, sharing data between languages, and reading/writing large datasets in chunks.
What this skill does
# h5py - Hierarchical Data Storage
h5py provides a seamless bridge between NumPy and HDF5. It allows you to organize data into groups (like folders) and datasets (like NumPy arrays), with rich metadata (attributes) attached to every object.
## When to Use
- Storing datasets that are much larger than your computer's RAM.
- Organizing complex scientific data into a hierarchical "folder-like" structure.
- Storing numerical arrays (NumPy) with high-speed random access.
- Keeping metadata (units, experiment dates, parameters) attached directly to the data.
- Sharing data between different languages (C, C++, Fortran, Java, MATLAB), as HDF5 is a cross-platform standard.
- Reading/writing large datasets in chunks to optimize I/O performance.
## Reference Documentation
**Official docs**: https://docs.h5py.org/
**HDF Group**: https://www.hdfgroup.org/
**Search patterns**: `h5py.File`, `create_dataset`, `h5py.Group`, `chunks=True`, `compression="gzip"`
## Core Principles
### The Hierarchy
HDF5 files contain two main types of objects:
- **Datasets**: Multidimensional arrays of data (NumPy-like).
- **Groups**: Container structures that can hold datasets or other groups (like directories).
### Slicing
h5py datasets support standard NumPy slicing. When you slice a dataset, only that specific slice is read from the disk, keeping memory usage low.
### Attributes
Every group and dataset can have attributes (key-value pairs) for metadata.
## Quick Reference
### Installation
```bash
pip install h5py
```
### Standard Imports
```python
import h5py
import numpy as np
```
### Basic Pattern - Writing and Reading
```python
import h5py
import numpy as np
# Writing data
with h5py.File('data.h5', 'w') as f:
dset = f.create_dataset('main_data', data=np.random.rand(100, 100))
dset.attrs['units'] = 'meters'
grp = f.create_group('subgroup')
grp.create_dataset('results', data=[1, 2, 3])
# Reading data
with h5py.File('data.h5', 'r') as f:
data_slice = f['main_data'][0:10, 0:10] # Only read 100 elements
units = f['main_data'].attrs['units']
print(f"Group content: {list(f['subgroup'].keys())}")
```
## Critical Rules
### ✅ DO
- **Use Context Managers** - Always use `with h5py.File(...) as f:` to ensure files are closed even if errors occur.
- **Use Chunking** - For large datasets, specify `chunks=True` or a manual shape to optimize access speed for specific slicing patterns.
- **Enable Compression** - Use `compression="gzip"` to save disk space for large numerical arrays.
- **Use Descriptive Names** - Use groups to organize data logically (e.g., `/experiment1/sensorA/raw`).
- **Store Metadata in Attributes** - Don't create separate text files for units or timestamps; attach them to the datasets.
- **Check Membership** - Use `"name" in group` before accessing to avoid KeyError.
### ❌ DON'T
- **Open files in 'w' by mistake** - The 'w' mode overwrites existing files. Use 'a' (append/read-write) or 'r+' (read-write) instead.
- **Load entire datasets into RAM** - Avoid `data = f['large_dataset'][:]` unless you are sure it fits in memory.
- **Store thousands of small datasets** - HDF5 is optimized for large arrays. For millions of tiny scalars, use a single array or a different database.
- **Forget to close files** - An unclosed HDF5 file can become corrupted or locked.
## Anti-Patterns (NEVER)
```python
import h5py
import numpy as np
# ❌ BAD: Manual file closing (unsafe)
f = h5py.File('data.h5', 'w')
f.create_dataset('x', data=np.arange(10))
f.close() # If an error happened above, this never runs!
# ✅ GOOD: Context manager
with h5py.File('data.h5', 'w') as f:
f.create_dataset('x', data=np.arange(10))
# ❌ BAD: Storing metadata as strings inside a dataset
f.create_dataset('meta', data=np.array(['unit: meter', 'date: 2024']))
# ✅ GOOD: Using Attributes
dset = f.create_dataset('data', data=np.random.rand(10))
dset.attrs['unit'] = 'meter'
dset.attrs['date'] = '2024'
# ❌ BAD: Inefficient chunking (one row at a time when you read columns)
# f.create_dataset('big', shape=(10000, 10000), chunks=(1, 10000))
```
## Dataset Creation and Configuration
### Advanced Options
```python
with h5py.File('optimized.h5', 'w') as f:
# 1. Resizable dataset (maxshape)
dset = f.create_dataset('growing',
shape=(100,),
maxshape=(None,), # Allow growth in 1st dimension
dtype='float32')
# 2. Compression and Chunking
f.create_dataset('compressed',
data=np.random.randn(1000, 1000),
chunks=(100, 100),
compression="gzip",
compression_opts=4) # 4 is a good balance
# 3. Filling with default values
f.create_dataset('default', shape=(10, 10), fillvalue=-1.0)
```
## Working with Groups
### Navigation and Iteration
```python
with h5py.File('nested.h5', 'w') as f:
f.create_group('raw/2024/january')
f.create_group('raw/2024/february')
# Recursive iteration
def print_structure(name, obj):
print(name)
with h5py.File('nested.h5', 'r') as f:
f.visititems(print_structure) # Visits every dataset and group
# Accessing via path
feb_data = f['/raw/2024/february']
```
## Performance Optimization
### 1. Chunking Strategies
Chunks are the smallest unit of data that can be read or written.
- If you usually read row by row: `chunks=(1, n_cols)`.
- If you read blocks: `chunks=(100, 100)`.
- If unsure: `chunks=True` lets h5py guess.
### 2. SWMR (Single Writer Multiple Reader)
Allows a writer to append to a file while other processes read from it in real-time.
```python
# Writer
f = h5py.File('live.h5', 'w', libver='latest')
f.swmr_mode = True
# Reader
f = h5py.File('live.h5', 'r', libver='latest', swmr=True)
```
### 3. Core Driver (In-Memory HDF5)
Use HDF5 structure but keep it entirely in RAM for speed, with optional save to disk.
```python
# Create an HDF5 file in memory
f = h5py.File('memfile.h5', 'w', driver='core', backing_store=True)
```
## Practical Workflows
### 1. Storing Machine Learning Training Data
```python
def save_ml_dataset(X, y, filename):
with h5py.File(filename, 'w') as f:
# Create datasets for images and labels
f.create_dataset('images', data=X, compression="lzf") # LZF is fast
f.create_dataset('labels', data=y)
# Add metadata
f.attrs['n_samples'] = X.shape[0]
f.attrs['input_shape'] = X.shape[1:]
f.attrs['classes'] = np.unique(y)
# Use cases: training on data that exceeds RAM
```
### 2. Large Simulation Logger
```python
def log_simulation_step(filename, step_idx, data_array):
with h5py.File(filename, 'a') as f:
if 'simulation' not in f:
# Initialize resizable dataset
f.create_dataset('simulation',
shape=(0, *data_array.shape),
maxshape=(None, *data_array.shape),
chunks=(1, *data_array.shape))
dset = f['simulation']
dset.resize(step_idx + 1, axis=0)
dset[step_idx] = data_array
```
### 3. Batch Image Storage
```python
def store_images(image_files, h5_file):
with h5py.File(h5_file, 'w') as f:
grp = f.create_group('microscopy_data')
for i, img_path in enumerate(image_files):
# Load your image here
img_data = np.random.rand(512, 512)
dset = grp.create_dataset(f'img_{i:04d}', data=img_data)
dset.attrs['original_path'] = img_path
```
## Common Pitfalls and Solutions
### The "Dataset Already Exists" Error
```python
# ❌ Problem: f.create_dataset('x', ...) fails if 'x' exists
# ✅ Solution: Delete first or use a check
if 'x' in f:
del f['x']
f.create_dataset('x', data=new_data)
```
### File Locking Issues
```python
# ❌ Problem: "OSError: Unable to open file (file locking disabled on this file system)"
# This often happens onRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.