mcp · Global

CHILmesh

Mesh data structure for representing triangular, quadrangular, and mixed-element meshes. Intended for hydrodynamic domains.

Claim this listing

Represent CHILmesh? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: 2D triangular, quadrilateral and mixed-element meshes (hydrodynamic domains) · ADCIRC fort.14 mesh read/write · SMS .2dm mesh read/write (with NS nodestrings) · Gmsh .msh mesh read/write · ADCIRC output read: fort.61/62/63/64, maxele.63, maxvel.63 · ADCIRC NetCDF output read (optional netCDF4 extra) · ADCIRC boundary forcing and tidal potential files (fort.13/15/19/20/22/24, OWI wind and pressure) · Per-element skew quality · Layer peeling · Mesh smoothing (FEM) · Element coloring and partitioning · Point location in mesh · Mesh fetch from Valence registry (token-gated)
Formats docs-verified: ADCIRC fort.14 · ADCIRC fort.13/15/19/20/22/24 · ADCIRC output fort.61/62/63/64, maxele.63, maxvel.63 · ADCIRC NetCDF (.nc) · OWI · SMS .2dm · Gmsh .msh · Python objects
Access docs-verified: Python library installable via pip (PyPI). Licence: PolyForm Noncommercial 1.0.0 with a No-AI/ML-training restriction. Registry meshes need a Valence API token (GitHub sign-in, 500 downloads/day, expires after one year).

Use cases llm-inferred: Check per-element skew quality of an ADCIRC or Gmsh mesh before model runs · Smooth and convert a fort.14 grid for handover in SMS .2dm or Gmsh .msh format · Map nodal ADCIRC output (maxele.63, maxvel.63) onto the mesh for flood-extent or velocity review · Pull a shared hydrodynamic mesh from the Valence registry for a coastal or estuary model baseline
Audience llm-inferred: hydraulic and hydrodynamic modellers · coastal and estuarine engineers · flood consultants

Constraints docs-verified: Two-dimensional only: topology, quality and smoothing operate in the plane · A plain pip install runs at Python speed; the C++ backend needs the [cpp] extra · GPU renderer is experimental · Smoothing does not change topology; the size function can trade worst-element quality for size accuracy · Registry meshes need a Valence token: GitHub sign-in, 500 downloads/day, token expires after one year · Noncommercial and research use only; commercial use needs a separate written licence, which would likely cover paid consultancy work · Listed as MCP, but the docs list MCP server tools as a future item (#286) and the metadata tools list is empty; the documented interface is the Python API · Docs describe mesh tooling only, with no rainfall, river-level or gauge data

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Daily discovery 2026-10-15: GitHub search; verified via GitHub API. Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · daily-2026-10-15 (github-search)