Advanced Fluxcore controls¶
Automatic service defaults are the starting point for a new case. Deliberate advanced overrides belong in config.compressible_config; only supplied values are forwarded. Omission and explicit null are different: omit unused numerical controls.
Discover the supported control¶
{"name":"get_solver_controls","arguments":{"architecture":"fluxcore","simulation_type":"rans","query":"cfl","offset":0,"limit":30}}
REST provides GET /v1/simulations/controls with the same query/filter concept. Each entry gives the canonical request path, type, reference default and applicability. fluxcore_api_default, when returned, identifies an API-level default override. These defaults are not instructions to fill an entire request with overrides.
Choose controls by purpose¶
Purpose |
What to examine |
Evidence to review |
|---|---|---|
Startup and progression |
CFL and progression controls |
Residual trends, field bounds, progress and stability |
Spatial accuracy |
Reconstruction, limiter and gradient controls |
Mesh sensitivity and local field quality |
Turbulence |
Model-specific and DES/DDES controls |
Wall treatment, wake resolution and sampling |
Time advancement |
Physical and inner transient settings |
Time-step sensitivity and within-step convergence |
Linear convergence |
Supported tolerances and iteration policies |
Overall convergence and runtime |
Thermal coupling |
Conjugate iteration limits, tolerances and transport properties |
Fluid/solid residuals, interface and energy balance |
Output |
Cadence, fields, forces and histories |
Whether saved data supports the requested analysis |
The generated numerical field reference lists public field types. Use live discovery for complete compatibility selectors and currently available combinations. Never guess a canonical field name from its friendly label or copy implementation comments into a request.
Apply a change reproducibly¶
Record the baseline request, change one relevant setting, validate the complete request and compare the engineering result as well as convergence. Keep mesh, physical model, reference quantities and output definitions fixed when measuring the effect of a numerical change.
A numeric field being present does not make every value or combination valid. Some controls are fixed for particular transient/physics configurations. Native source features are not callable until the central API contract exposes them. Validation failure should lead to a corrected supported request, not a bypass.