A render of a surf-pool CFD case tells you very little. What you actually get is a calculation package: free-surface frames over time, control sections, breaking-zone observations, the assumptions behind them, and a plain statement of what the model does and does not support.
Before anything runs, the task fixes the geometry, the bathymetry, the generation input, the control sections and the exact conclusion being tested. Public pages carry sanitized water frames only. The proprietary geometry, internal run names, grid parameters and mechanical detail stay off the site.
Water-surface frames over time, so you watch the wave move instead of reading one still image.
Lines used to read height, slope, breaking location and how the wave changes along the ride path.
Where the result leans heavily on the bathymetry, the generation input or geometry we still don't have.
Which conclusions still need refinement, convergence checks or a second scenario before you can trust them.
The package a client gets goes much deeper: frames, sections, the assumptions behind them and the engineering comments.
Useful inputs: the basin envelope, the depth profile, the target wave, your generation assumption, the control sections you care about, and the specific output you need out of the calculation.
Ask a vague question and you get a pretty picture back. Ask a specific one and CFD can back an engineering memo with its assumptions and limits written down. How the toolchain itself is checked against published flume measurements — with error numbers — is on the CFD validation page.
Free-surface states through wave growth, breaking and decay.
Control lines, bathymetry observations and the places that need another scenario.
A written boundary around what the calculation supports, and what it doesn't support yet.
No. CFD answers inside the model you set up. A final performance claim needs enough input data, validation work and checks tied to the specific project.
Only once they're sanitized. They must not expose the proprietary geometry, grid parameters, internal run names or closed mechanical detail.
A run of free-surface frames over time, the control sections, the assumptions, the limitations, and the next engineering step.
When the bathymetry, the generation input, the geometry or the engineering question changes.
A basin outline, a depth profile, a target wave and the question you want tested are enough to scope the first CFD run. Even a couple of paragraphs gets us started. We'll tell you what we can compute right away and where we'd need an NDA or more data.