frontier-hub

Curated hub of public physics-AI datasets and benchmarks: catalog, fetchers and converters to the Frontier dataset format.

One YAML file per public dataset or benchmark: what physics it covers, how large it is, its licence and whether commercial use is allowed, how to fetch it, and (where we have verified it) a converter to the Frontier dataset format.

pip install frontier-hub
python -m frontier_hub search "external aerodynamics"
python -m frontier_hub info drivaernet-plus-plus
python -m frontier_hub pull ahmedml --subset surface --max-bytes 2e9 --to datasets/

What is in this repository

• packages/frontier-hub/: Python package frontier-hub

Add a dataset

1. Copy catalog/_TEMPLATE.yaml to catalog/<domain>/<id>.yaml and fill it in. license must be the dataset's real licence as an SPDX identifier, with commercial_use set honestly; entries are rejected without it.
2. Optional: add a converter under converters/ and reference it from the entry.
3. Run python -m frontier_hub verify <id> and open a pull request.

The catalog lists datasets; it does not redistribute them. Data is fetched from the original source under the original licence, and every entry carries the citation.

Ecosystem

Repository	What it is
frontier-format	Frontier data model and dataset format: the frontier-dataset specification, the plugin contract, and reference readers/writers in Rust and Python.
frontier-connectors	Connector plugins that turn CFD/CAE solver output (OpenFOAM, VTK, Fluent, STAR-CCM+, CGNS, LS-DYNA, ...) into Frontier datasets. Write your own in an afternoon.
frontier-sdk	Frontier Python SDK: offline-first experiment tracking for physics ML, the native Rust core, and the NVIDIA PhysicsNeMo bridge.
frontier-physicsnemo	NVIDIA PhysicsNeMo plugin for Frontier: logging, model registry, checkpoint compatibility and dataset adapters. Installable independently of the platform.
frontier-hub (this repository)	Curated hub of public physics-AI datasets and benchmarks: catalog, fetchers and converters to the Frontier dataset format.
frontier-editor	Editor core and GPU text view for physics-ML configs, recipes and logs: rope document, undo tree, hunks with per-hunk approval, tree-sitter syntax, JSON-Schema diagnostics, provenance events, and a wgpu renderer that draws into the host's render pass.
frontier-viz	GPU-accelerated (wgpu) rendering core for meshes, fields and neural-network topology: native, browser (WebGPU) and headless.
foldstate	Statecharts as data with an event log: a pure, deterministic kernel (state, event) -> (state, effects), replay, fork, restore and explanations. no_std + alloc, runs natively and in WebAssembly. Not specific to Frontier.
frontier-zed	Frontier for Zed: JSON schemas, snippets and the Frontier MCP context server for physics-ML training configs, RunSpecs, data-prep recipes, pipelines, hub entries and plugin manifests. A Zed extension (extension.toml plus a small wasm32-wasip2 crate), installable as a dev extension today and submitted to the Zed extension registry later.

Contributing

Catalog entries and converters are the easiest way to start: see CONTRIBUTING.md. Code is licensed under Apache-2.0; each dataset keeps its own licence.