DeepCausalityCFD

Blueprints

One task per blueprint

Each entry covers a single task, with the DSL verbs it uses and the worked examples that exercise it. Generated API documentation lives with the crate.

  1. 00Install and run a reference caseYou need the crate as a dependency, or a single command that exercises it.An unpublished git dependency, and one command that exercises the full coupling stack in about forty seconds.cargo
  2. 01Sweep a parameter and get a tableYou have a parameter and need a table of outcomes across it.A study is a family of cases run to a verdict. The table is written before judgment, so it survives a failed gate.casessweepreduce_allrecordgatesverdict
  3. 02Gate a run against a placardYou need the run to fail and exit nonzero when a limit is exceeded.Gates turn a run into a check. Every verification target and every example exits nonzero when a gate fails, so the suite runs as a CI gate.GateSeqGateOutcomegatesverdict
  4. 03Fork a running simulation into counterfactual worldsYou need to compare commands evaluated from the same physical state.March until the physics fires an event, pause, then continue every candidate from that shared marched state. The fork is O(1) copy-on-write and each branch is alternated into its own audited world.march ... untilforkbranchcontinue_forrefinereduce_all
  5. 04Couple thermochemistry to a compressible flowYou need chemistry, thermal nonequilibrium and an electromagnetic observable evaluated with the flow rather than after it.The reentry sheath chain from gasdynamic jump through vibrational relaxation, finite-rate ionization and plasma frequency to comms cutoff, assembled as ordered stages over one marched field with a measured value at every link.VibrationalLagStageFiniteRateIonizationStageRegimeClassifyBlackoutTrigger
  6. 05Couple navigation to the physics stackYou need a state estimator to run at the solver's cadence, on the solver's evolved field.Navigation, chemistry, aero and control are entries in one ordered stage tuple executed after every marcher step. Composition is static, so there is no dyn dispatch and no scheduler.Coupling::between_stepsPhysicsStageTrajectoryNavCoupledField
  7. 06Detect and act on a regime changeYou need the run to notice that the governing physics changed, and to record when.A classifier reads the evolved field each step, bands the continuous quantities into a discrete key, and logs only key transitions. Downstream stages and march predicates read the class.RegimeClassifyRegimeClassGoverningModelBlackoutTrigger
  8. 07Pick a solver familyYou need to select one of the three solver families for a given problem.Dispatch is resolved at compile time from the config type. The selection criterion is the problem class, listed below with the evidence for each.marchMarchDispatchFloatType

Full API reference lives with the source:deep_causality_cfd