@pipeworx/turbulence-modeling-resource

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/turbulence-modeling-resource’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 2

Catalog of NASA Langley’s standard turbulence-model verification and validation test cases (flat plates, airfoils, jets, a backward-facing step, the wall-mounted hump, shock/boundary-layer interactions, and more), plus reference data for the cases that publish an unambiguous experimental or correlation dataset.

Tools

• tmr_cases(...) — the full case catalog (or one category): id, category, flow regime, documented Mach/Reynolds conditions, and whether reference data is available via tmr_reference_data.
• tmr_reference_data(...) — the reference (experimental or correlation) data for one case, where the case’s own page unambiguously labels a file as the reference data rather than one of many turbulence-model CFD results.

Auth

Keyless. US government work — public domain.

Data sources

• NASA Langley Research Center, Turbulence Modeling Resource — the standard set of verification cases (checking that a turbulence model is implemented correctly) and validation cases (checking that it reproduces real flow physics) used across the turbulence-modeling community: flat plates, bumps-in-channel, 2D and 3D airfoils, axisymmetric jets, a backward-facing step, a wall-mounted hump, shock/boundary-layer interactions, a supersonic square duct, the ONERA M6 wing, and a high-Reynolds-number channel flow.

The resource moved from its original NASA-hosted address to a GitHub Pages site the publisher itself maintains; this pack reads from the current address. Mach number and Reynolds number in the case catalog are filled in only where a case’s own page states them explicitly — a null means NASA’s page did not give that figure, not that the flow has no such condition.

Case directories hold dozens of files each — one per turbulence model’s CFD result, plus (for some cases) the actual experimental or correlation reference data the models are checked against, named and linked distinctly on the case’s own page. tmr_reference_data only serves the latter kind, and only for cases where that distinction is unambiguous from the page itself; everything else stays unmapped rather than guessed at, which is why only a handful of cases report reference_data: true today. Every file follows the same plain-text, Tecplot-style convention: #-prefixed comment lines, a variables="col1","col2",... header, optional zone, t="label" sections, then whitespace-separated numeric rows — parsed generically in src/index.ts rather than per-case.

tmr_reference_data’s data_as_of is the upstream file’s own Last-Modified response header — never a date written into the pack at build time, which would silently go stale. fetched_at is always this call’s own timestamp, so a caller still knows when Pipeworx last asked even on the rare response without a Last-Modified header. tmr_cases’ catalog_transcribed is a different thing entirely: the case list and conditions are a plain array transcribed from the publisher’s pages at pack-build time, not re-fetched live on every call, so it is named and dated separately rather than borrowing data_as_of’s meaning.

Tools

• tmr_cases — Catalog of NASA Langley Turbulence Modeling Resource (TMR) verification and validation cases for turbulence models — flat plates, bumps-in-channel, airfoils (NACA 0012, NACA 4412), axisymmetric jets,
• tmr_reference_data — Reference data (an experimental measurement or an established correlation, e.g. skin-friction coefficient Cf or lift/drag vs. angle of attack) for one NASA Langley Turbulence Modeling Resource case, a