Frequently asked questions

Which interface is authoritative?

The central API/MCP service. Studio, REST, Python and MCP all use its engineering operations, validation and saved resources.

Which mesher should I choose?

Use GD Structured Meshing for supported Cartesian workflows and GD Hex-core Meshing for body-fitted walls, wall layers, a hexahedral core and polyhedral fill. Choose from geometry and physics requirements; see meshing.

Does more resolution always produce a better answer?

Resolution must cover the important physics and be paired with suitable models and convergence. Establish adequacy through mesh/time-step sensitivity and relevant engineering outputs.

Can I run laminar, RANS or DES?

The current contract exposes laminar through CHT, SST and Spalart–Allmaras RANS/URANS, and supported DES/DDES controls through discovery. Read the compatibility table.

Does a completed job mean the solution converged?

No. Review convergence, physical balances, sensitivity and publication status separately. Use saved convergence assessment.

Can an agent edit my Studio design?

A shared authoring draft supports validated intermediate edits and checkpoints. Finished work follows Studio’s revision review. A stateless candidate does not automatically change a saved project.

Do I need a Python package?

REST and MCP require no Gradient Dynamics package. The implemented Python client is documented separately; do not install a similarly named package based on the old preview SDK.