Skip to content

Frozen Rotor derived boundary surfaces 38155649489

Latest

Choose a tag to compare

Frozen Rotor derived boundary surfaces — educational data only

This package contains the exact binary STL files referenced by topology-report.json,
that read-only report, and the original upstream example-data MIT license notice.
Surfaces are derived from the two immutable official HDF5 meshes. Original mesh
files are not modified or included in this boundary package.

Native coordinate units are UNVERIFIED. Do not label these STL coordinates as
metres, scale them silently, or import them as an exact manufacturer pump model.
Zone identity, source mesh provenance, triangle count, file length and SHA-256 are
recorded in the report. Preserve these records before any separate derived work.

This extraction does NOT generate a volume mesh, joined Fluent case, a solver
session, a quality-qualified mesh, CFD, cavitation, NPSHr or physical transient
results. A topology inventory is not a native mesh-quality or solver check.
No Fluent, gmsh or other native solver was launched. Main application inputs,
results, pump database, credentials and deployment are not part of this package.

Before a separate learning mesh can be used, verify coordinate units, boundary
roles, geometry/interface integrity, mesh quality, resource limits, fluid and
pressure datum, solver/license availability and relevant numerical criteria.
The installed PyFluent SDK and a checked surface alone do not establish CFD ready.

SHA256SUMS verifies all separate release files except itself. topology-report.json
also verifies every exact STL file inside the ZIP. No additional directory files
are bundled or executed. Standard public GitHub hosted runner only; no paid fallback.

Official example:
https://fluent.docs.pyansys.com/version/stable/examples/00-fluent/frozen_rotor_workflow.html