Skip to content

Solver initialization

Commands of the solver_initialization chapter of the database, 7 entries. The status words are defined once, on the compatibility matrix, which says what each rests on and what the script builder does with it. Read it before this page: broken and removed are refusals, so a row here can be telling you the emitter will not write that command for that version.

CLEAR_SOLUTION

Phase exec, layout bare. Manual: SRC-003 p.338.

Clears the existing solution while keeping the initialization; used between sweep points when solution reuse is not wanted.

Version Status Evidence
25.100 documented SRC-748 p.313, same grammar as 26.120
26.000 documented SRC-747 p.312, same grammar as 26.120
26.100 documented SRC-741 p.335, same grammar as 26.120
26.101 documented SRC-725 p.337, same grammar as 26.120
26.120 verified reports/compat/CMP-26120_2026-08-08_full.yaml
26.121 verified reports/compat/CMP-26121_2026-08-08_full.yaml
26.122 verified reports/compat/CMP-26122_2026-08-11_full.yaml
26.123 verified reports/compat/CMP-26123_2026-08-17_full-sim.yaml; SRC-751 p.343, unchanged from SRC-750 p.343
26.124 verified reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.343, the SRC-751 file, carried from 26.123

INITIALIZE_SOLVER

Phase init, layout keyword_block. Manual: SRC-003 p.337.

SURFACES takes -1 for all boundaries or a count followed by one line per surface with the surface index and the quad mesher toggle (SURFACE_TOGGLES lines of the form index,ENABLE; the count check ties them to SURFACES). WAKE_TERMINATION_X takes an X location in the reference frame or DEFAULT for auto-computation. PERIODIC symmetry appends the number of copies on the SYMMETRY line (SYMMETRY_COPIES). WALL_COLLISION_AVOIDANCE applies to solver models 1 to 3. The initialize_solver helper builds both extended forms from typed arguments. Initializing MIRROR symmetry with a full (non-half) model diverges instantly (SRC-003 p.217); case metadata declaring a full model triggers a build-time warning when cases/ lands.

Argument Specification
solver_model enum in
surfaces int
surface_toggles str_list (optional)
wake_termination_x str
symmetry enum in
symmetry_copies int (optional)
wall_collision_avoidance enum in {ENABLE, DISABLE} (optional)
Version Status Evidence
25.000 documented SRC-749 p.298, this edition's own grammar; see the note below
25.100 documented SRC-748 p.312, this edition's own grammar; see the note below
26.000 documented SRC-747 p.311, this edition's own grammar; see the note below
26.100 documented SRC-741 p.334, same grammar as 26.120
26.101 verified reports/compat/CMP-26101_2026-08-08_full.yaml
26.120 verified reports/compat/CMP-26120_2026-08-08_full.yaml
26.121 verified reports/compat/CMP-26121_2026-08-08_full.yaml
26.122 verified reports/compat/CMP-26122_2026-08-11_full.yaml
26.123 verified reports/compat/CMP-26123_2026-08-17_full-sim.yaml; SRC-751 p.342, unchanged from SRC-750 p.342
26.124 verified reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.342, the SRC-751 file, carried from 26.123

REMOVE_INITIALIZATION

Phase init, layout bare. Manual: SRC-003 p.338.

Discards the solver initialization. Its empty 25.000 column is not a gap: that edition spells the same capability SOLVER_UNINITIALIZE, and the two are exactly complementary across the seven editions, sharing the bare layout, the init phase and the chapter. The changeover is at 25.100 and the older entry carries the successor.

Version Status Evidence
25.100 documented SRC-748 p.313, same grammar as 26.120
26.000 documented SRC-747 p.312, same grammar as 26.120
26.100 documented SRC-741 p.335, same grammar as 26.120
26.101 verified reports/compat/CMP-26101_2026-08-08_full.yaml
26.120 verified reports/compat/CMP-26120_2026-08-08_full.yaml
26.121 verified reports/compat/CMP-26121_2026-08-08_full.yaml
26.122 verified reports/compat/CMP-26122_2026-08-11_full.yaml
26.123 verified reports/compat/CMP-26123_2026-08-17_full-sim.yaml; SRC-751 p.343, unchanged from SRC-750 p.343
26.124 verified reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.343, the SRC-751 file, carried from 26.123

SOLVER_CLEAR

Phase exec, layout bare. Manual: SRC-749 p.307.

Clears the solver solution, leaving the initialization in place. The 25.000 edition states it takes no parameters and no later edition prints it.

Version Status Evidence
25.000 documented SRC-749 p.307, this edition documents it
25.100 removed SRC-748 pp.271-347, the whole scripting reference of the 25.100 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.
26.000 removed SRC-747 pp.270-346, the whole scripting reference of the 26.000 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.
26.100 removed SRC-741 pp.275-369, the whole scripting reference of the 26.100 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.
26.101 removed SRC-725 pp.280-375, the whole scripting reference of the 26.101 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.
26.120 removed SRC-003 pp.281-376, the whole scripting reference of the 26.120 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.
26.121 removed SRC-740 pp.284-379, the whole scripting reference of the 26.121 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.

SOLVER_PROXIMAL_BOUNDARIES

Phase init, layout payload_lines. Manual: SRC-003 pp.337-338.

Enables solver proximity checking for the listed boundaries, one index per line. Must be called before INITIALIZE_SOLVER (SRC-003 p.338).

Argument Specification
count int
boundary_indices int_list
Version Status Evidence
25.000 documented SRC-749 p.298, same grammar as 26.120
25.100 documented SRC-748 p.313, same grammar as 26.120
26.000 documented SRC-747 p.312, same grammar as 26.120
26.100 documented SRC-741 p.335, same grammar as 26.120
26.101 documented SRC-725 p.336, same grammar as 26.120
26.120 documented SRC-003 pp.337-338
26.121 verified reports/compat/CMP-26121_2026-08-08_savedstate2.yaml; SRC-740 pp.340-341 documents a SECOND call form no older edition prints: a count of -1 selects every boundary and takes no index lines at all. So this build's grammar makes the index list optional, which the grammar the older editions state does not. Not an all_sentinel declaration: that field is read on an index argument, and the -1 here is written in the COUNT field. The count-and-payload check is what enforces the pairing, refusing any count except -1 when the list is omitted.
26.122 verified reports/compat/CMP-26122_2026-08-11_full.yaml
26.123 verified reports/compat/CMP-26123_2026-08-17_full-sim.yaml; SRC-751 p.342, unchanged from SRC-750 p.342
26.124 verified reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.342, the SRC-751 file, carried from 26.123

SOLVER_UNINITIALIZE

Phase init, layout bare. Manual: SRC-749 p.298.

Discards the solver initialization, returning the model to the state before INITIALIZE_SOLVER ran. Printed by the 25.000 edition and by no edition after it. IT WAS RENAMED RATHER THAN WITHDRAWN, and the reading is a measurement rather than an inference from the two names. Across the seven editions this command and REMOVE_INITIALIZATION are exactly complementary: this one is printed by 25.000 alone, that one by every edition from 25.100 on and by no earlier one. They share the bare layout, the init phase and the chapter. One capability, two spellings, with the changeover at 25.100. SOLVER_CLEAR is NOT the successor even though it leaves at the same edition, because it clears the SOLUTION rather than the initialization, and unlike this command nothing takes its place.

Version Status Evidence
25.000 documented SRC-749 p.298, this edition documents it
25.100 removed SRC-748 pp.271-347, the whole scripting reference of the 25.100 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.; Successor: REMOVE_INITIALIZATION
26.000 removed SRC-747 pp.270-346, the whole scripting reference of the 26.000 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.; Successor: REMOVE_INITIALIZATION
26.100 removed SRC-741 pp.275-369, the whole scripting reference of the 26.100 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.; Successor: REMOVE_INITIALIZATION
26.101 removed SRC-725 pp.280-375, the whole scripting reference of the 26.101 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.; Successor: REMOVE_INITIALIZATION
26.120 removed SRC-003 pp.281-376, the whole scripting reference of the 26.120 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.; Successor: REMOVE_INITIALIZATION
26.121 removed SRC-740 pp.284-379, the whole scripting reference of the 26.121 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name.; Successor: REMOVE_INITIALIZATION

START_SOLVER

Phase exec, layout bare. Manual: SRC-003 p.338.

Runs the solver with the current runtime settings; convergence is declared against the SOLVER_SET_CONVERGENCE threshold.

Version Status Evidence
25.000 documented SRC-749 p.307, same grammar as 26.120
25.100 documented SRC-748 p.313, same grammar as 26.120
26.000 documented SRC-747 p.312, same grammar as 26.120
26.100 documented SRC-741 p.335, same grammar as 26.120
26.101 verified reports/compat/CMP-26101_2026-08-08_full.yaml
26.120 verified reports/compat/CMP-26120_2026-08-08_full.yaml
26.121 verified reports/compat/CMP-26121_2026-08-08_full.yaml
26.122 verified reports/compat/CMP-26122_2026-08-11_full.yaml
26.123 verified reports/compat/CMP-26123_2026-08-17_full-sim.yaml; SRC-751 p.343, unchanged from SRC-750 p.343
26.124 verified reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.343, the SRC-751 file, carried from 26.123