Fluxcore requests

Use validate_simulation / POST /v1/simulations/validate before run_simulation / POST /v1/simulations. Both interfaces use the central API’s SimulationRequest. Use architecture="fluxcore" for the supported GPU solver. Omit compatibility selectors and unspecified numerical controls.

Required engineering evidence

Start from a ready, accepted simulation mesh artifact. Read its exact patch and material-zone names, unit metadata and quality. Establish an operating point: the default air properties and zero freestream speed are not substitutes for choosing the physical problem.

The request references mesh_artifact_id, optional project_id, config and optional decision_context. URANS also requires an owned restart_artifact_id. Simulation input locations are resolved by the service; clients supply artifact IDs, not filesystem or storage paths.

Steady external-flow example

This example assumes actual mesh patches named farfield and body. Replace them with the inspected names. It illustrates a request and does not establish validated aerodynamic performance.

{
  "mesh_artifact_id": "REPLACE_WITH_MESH_ARTIFACT_ID",
  "config": {
    "architecture": "fluxcore",
    "simulation_type": "rans",
    "turbulence_model": "k_omega_sst",
    "wall_treatment": "wall_functions",
    "airspeed": 30,
    "temperature": 300,
    "reference_pressure": 101325,
    "boundary_conditions": {
      "farfield": {"type": "farfield"},
      "body": {"type": "wall"}
    },
    "max_iterations": 6000,
    "export_solution_fields": true
  }
}

Main control groups

Group

What to specify

Physics

simulation_type, turbulence_model, wall_treatment

Operating point

Freestream speed/angle, pressure, temperature and fluid properties

Boundaries

Exact patch names and typed boundary values

Rotation

mrf_zones linked to real cell zones; rotating-wall patches where appropriate

Thermal

Zone classifications, conductivity, density, heat capacity, heat sources and inlet temperature

Runtime

Steady iteration ceiling or transient steps/time step/inner controls

Monitoring

Forces/reference dimensions, history cadence and convergence assessment criteria

Results

Field publication and intermediate-output cadence

Advanced

Explicit overrides under config.compressible_config, discovered from the service

Use the linked FluxCoreConfig model for exact nested fields. Boundary conditions, thermal setup, turbulence and time integration explain the coupled requirements.

Validate and qualify

API validation rejects unknown fields and incompatible combinations before dispatch. Mesh-dependent validity and numerical convergence remain separate checks. Estimate the work, submit once with a retained idempotency key, and follow the durable job.

Report the returned convergence assessment, histories, forces and thermal balances that are actually present. Keep field publication enabled for volume slices and streamlines. A result can finish without converging; a diagnostic summary can remain available even if field publication fails.