Solver settings

Commands of the solver_settings chapter of the database, 29 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.

CREATE_AIRFOIL_SEPARATION

Phase init, layout payload_lines. Manual: SRC-003 p.341.

Assigns the airfoil (trailing-edge) separation model to the listed boundaries, with the Valarezo maximum-lift criterion enabled or disabled per assignment. NUM_BOUNDARIES takes -1 for all mesh boundaries, in which case no index line follows; otherwise the comma-separated indices are the next line (SRC-003 pp.341-342).

Argument	Specification
name	str
num_boundaries	int
valarezo_criterion	enum in
boundary_indices	int_list (optional)

Version	Status	Evidence
26.101	documented	SRC-725 p.340, same grammar as 26.120
26.120	documented	SRC-003 p.341
26.121	documented	SRC-740 p.344, same grammar as 26.120
26.123	documented	SRC-751 p.346, unchanged from SRC-750 p.346
26.124	documented	SRC-752 p.346, the SRC-751 file, carried from 26.123; not run on 26.124

CREATE_AXIAL_VORTEX_SEPARATION

Phase init, layout payload_lines. Manual: SRC-003 p.342.

Assigns the axial vortex separation model to a slender body. FRAME is the 1-based index of the coordinate system acting as the body axes, 1 being the reference frame, and BODY_AXIS names the body axis within it either as a letter or as its 1-based index (SRC-003 p.342). Read the manual's second sample with care: it puts -1 in the FRAME position rather than in NUM_BOUNDARIES, which contradicts the parameter table on the same page and is not a form this database records.

Argument	Specification
name	str
num_boundaries	int
frame	int
body_axis	enum in
diameter	float [simulation length units]
sharp_nose_vortices	enum in
boundary_indices	int_list (optional)

Version	Status	Evidence
26.101	documented	SRC-725 p.341, same grammar as 26.120
26.120	documented	SRC-003 p.342
26.121	documented	SRC-740 p.345, same grammar as 26.120
26.123	documented	SRC-751 p.347, unchanged from SRC-750 p.347
26.124	documented	SRC-752 p.347, the SRC-751 file, carried from 26.123; not run on 26.124

CREATE_BULK_SEPARATION

Phase init, layout payload_lines. Manual: SRC-003 p.342.

Assigns the bulk (bluff-body) flow-separation model to the listed boundaries. NUM_BOUNDARIES takes -1 for all mesh boundaries; otherwise the comma-separated indices follow on the next line (SRC-003 p.342). The signature is version-sensitive: 26.12 inserts SEPARATION_TYPE (CYLINDRICAL or FLAT_PLATE, matching the bulk model sub-typing documented at SRC-003 p.207) as the second argument, which the 26.1 grammar does not have (SRC-725 p.341).

Argument	Specification
name	str
separation_type	enum in
num_boundaries	int
diameter	float [simulation length units]
boundary_indices	int_list (optional)

Version	Status	Evidence
26.101	documented	SRC-725 p.341 documents a three-argument form without SEPARATION_TYPE. The same page's sample blocks spell the command CREARE_BULK_SEPARATION while the function header spells CREATE_BULK_SEPARATION; a controlled 26.101 run (build 5012026, RPT-012) resolved the spelling: the solver accepts CREATE_BULK_SEPARATION and rejects CREARE as an unrecognized command, so CREARE is a manual typo and the header spelling stands. That run was recorded as 26.100 before the renumbering of 2026-08-04; the build is what identifies it. Status stays documented pending an effect-asserting harness probe on 26.101
26.120	documented	Contradicted by evidence and not yet reprobed: on 26.120 (build #7012026) the solver refused all four documented forms, including the three-argument 26.1 form that ran on the May build, then called 26.100 and now 26.101 (reports/RPT-015_bulk-separation-family-acceptance_2026-08-02.md). The status stays documented because a promotion needs a probe report written by pyfs-qa (CONTRIBUTING.md invariant 3) and RPT-015 is an ad-hoc probe that promotes nothing; the harness re-probe is PLN-20260802-2240.

CREATE_CYLINDRICAL_BULK_SEPARATION

Phase init, layout payload_lines. Manual: SRC-740 p.345.

The cylindrical bulk separation model, split out of the SEPARATION_TYPE argument that CREATE_BULK_SEPARATION carried on 26.120. RPT-015 accepted this command on 26.120 as well, where no manual documents it; that is a probe result and not a citation, so only the documented version is recorded here.

Argument	Specification
name	str
num_boundaries	int
diameter	float [simulation length units]
boundary_indices	int_list (optional)

Version	Status	Evidence
26.121	documented	SRC-740 p.345
26.122	documented	SRC-750 p.347, same grammar as 26.121
26.123	documented	SRC-751 p.347, unchanged from SRC-750 p.347
26.124	documented	SRC-752 p.347, the SRC-751 file, carried from 26.123; not run on 26.124

CREATE_STRATFORD_BULK_SEPARATION

Phase init, layout payload_lines. Manual: SRC-740 p.345.

The Stratford bulk separation model, which takes no diameter. As with the cylindrical command above, RPT-015 accepted it on 26.120 where no manual documents it. The index-line form was run on 26.121 only; 26.120 saw the -1 form alone.

Argument	Specification
name	str
num_boundaries	int
boundary_indices	int_list (optional)

Version	Status	Evidence
26.121	documented	SRC-740 p.345
26.122	documented	SRC-750 p.347, same grammar as 26.121
26.123	documented	SRC-751 p.347, unchanged from SRC-750 p.347
26.124	documented	SRC-752 p.347, the SRC-751 file, carried from 26.123; not run on 26.124

DELETE_AXIAL_SEPARATION_BOUNDARIES

Phase init, layout bare. Manual: SRC-741 p.339.

Clears the axial flow separation list. Spelled as an empty axial_separation_boundaries selection by the curated helper.

Version	Status	Evidence
25.000	documented	SRC-749 p.303, same grammar as 26.100
25.100	documented	SRC-748 p.317, same grammar as 26.100
26.000	documented	SRC-747 p.316, same grammar as 26.100
26.100	documented	SRC-741 p.339

DELETE_CROSSFLOW_SEPARATION_BOUNDARIES

Phase init, layout bare. Manual: SRC-741 p.340.

Clears the cross-flow separation list. Spelled as an empty crossflow_separation_boundaries selection by the curated helper.

Version	Status	Evidence
25.000	documented	SRC-749 p.304, same grammar as 26.100
25.100	documented	SRC-748 p.317, same grammar as 26.100
26.000	documented	SRC-747 p.316, same grammar as 26.100
26.100	documented	SRC-741 p.340

DELETE_SEPARATION

Phase init, layout inline. Manual: SRC-003 p.342.

Deletes one separation model by its 1-based index in the order the models were created; -1 deletes every one of them (SRC-003 p.342). One command covers all separation types, which is the reason the 26.100 generation needed a DELETE per mechanism and this one does not.

Argument	Specification
index	int

Version	Status	Evidence
26.101	documented	SRC-725 p.341, same grammar as 26.120
26.120	documented	SRC-003 p.342
26.121	documented	SRC-740 p.346, same grammar as 26.120
26.123	documented	SRC-751 p.348, unchanged from SRC-750 p.348
26.124	documented	SRC-752 p.348, the SRC-751 file, carried from 26.123; not run on 26.124

DELETE_THIN_BOUNDARIES

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

Clears the thin boundary list entirely. It takes no argument, so there is no way to remove one boundary from the list: a script that wants a subset clears and re-sets.

Version	Status	Evidence
26.101	documented	SRC-725 p.342, same grammar as 26.120
26.120	documented	SRC-003 p.343
26.121	documented	SRC-740 p.346, same grammar as 26.120
26.123	documented	SRC-751 p.348, unchanged from SRC-750 p.348
26.124	documented	SRC-752 p.348, the SRC-751 file, carried from 26.123; not run on 26.124

DELETE_VALAREZO_CRITERION_BOUNDARIES

Phase init, layout bare. Manual: SRC-741 p.339.

The manual's own name for clearing the Valarezo list, which the solver does not answer to. The name it answers to is the entry directly below, recorded on a probe citation since the design decision of 2026-08-06 (PLN-20260805-1540). Both are kept: this one because SRC-741 p.339 documents it and a reader of that page needs to find out here that it does not work, and the other because it is the one that runs.

Version	Status	Evidence
26.100	documented	Contradicted by evidence and not yet reprobed: RPT-018 found this name unrecognized on 26.100 (build #2122026), the build whose own manual documents it in a function header, while the undocumented DELETE_VALAREZO_SEPARATION_BOUNDARIES was accepted. The status stays documented because a promotion to broken needs a probe report written by pyfs-qa (CONTRIBUTING.md invariant 3) and RPT-018 is an ad-hoc probe that promotes nothing; the harness re-probe is PLN-20260805-1520.

DELETE_VALAREZO_SEPARATION_BOUNDARIES

Phase init, layout bare. Probe report: reports/RPT-018_separation-family-across-builds_2026-08-05.md.

The erase of the Valarezo maximum-lift criterion list that the February build accepts. Its documented sibling above, DELETE_VALAREZO_CRITERION_BOUNDARIES, is the name SRC-741 p.339 prints in a function header and the solver refuses as unrecognized, so the manual names one command and the solver answers to another. Recorded here rather than left to Script.raw(), which is the one emission path with no validation at all.

Version	Status	Evidence
26.100	documented	reports/RPT-018_separation-family-across-builds_2026-08-05.md

DELETE_VISCOUS_EXCLUDED_BOUNDARIES

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

Clears the viscous-exclusion list, restoring viscous coupling on every boundary. The helper spells the clear as an empty viscous_excluded selection rather than as its own keyword, so the snapshot records one list per flag instead of a list and a separate erase.

Version	Status	Evidence
25.000	documented	SRC-749 p.303, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	documented	SRC-741 p.338
26.101	documented	SRC-725 p.340
26.120	documented	SRC-003 p.341
26.121	documented	SRC-740 p.344
26.123	documented	SRC-751 p.346, unchanged from SRC-750 p.346
26.124	documented	SRC-752 p.346, the SRC-751 file, carried from 26.123; not run on 26.124

DISABLE_SOLVER_REF_VELOCITY

Phase init, layout bare. Manual: SRC-740 p.342.

Makes the solver reference velocity equal the free-stream velocity, which is what the manual's sample comment states, rather than holding whatever SOLVER_SET_REF_VELOCITY last set. DOCUMENTED BY THE 26.12 HOTFIX EDITION ALONE, so one version row, a citation of SRC-740, and no probe. Both of those are worth weighing before relying on it, since it reaches a public keyword of solver_settings. Why it exists at all is legible from the contour vocabulary rather than from this page: SET_SCENE_CONTOUR offers pressure_coefficient_reference beside pressure_coefficient_freestream, so the two velocities normalise different reported quantities and a stale reference velocity would change one of them. That is a reading of two pages together and not a measurement of what the solver does.

Version	Status	Evidence
26.121	documented	SRC-740 p.342
26.122	documented	SRC-750 p.344, same grammar as 26.121
26.123	documented	SRC-751 p.344, unchanged from SRC-750 p.344
26.124	documented	SRC-752 p.344, the SRC-751 file, carried from 26.123; not run on 26.124

SET_AXIAL_SEPARATION_BOUNDARIES

Phase init, layout payload_lines. Manual: SRC-741 p.339.

Adds boundaries to the axial flow separation list. NUM_BOUNDARIES takes -1 for all mesh boundaries, in which case the following line is ignored; otherwise the comma-separated indices are the next line (SRC-741 p.339).

Argument	Specification
num_boundaries	int
boundary_indices	int_list (optional)

Version	Status	Evidence
25.000	documented	SRC-749 p.303, same grammar as 26.100
25.100	documented	SRC-748 p.317, same grammar as 26.100
26.000	documented	SRC-747 p.316, same grammar as 26.100
26.100	documented	SRC-741 p.339

SET_BOUNDARY_LAYER_TYPE

Phase init, layout inline. Manual: SRC-003 p.341.

The default transitional-turbulent model is stated valid for chord Reynolds numbers between 500000 and 1500000; outside this range select LAMINAR or TURBULENT explicitly (SRC-003 p.203).

Argument	Specification
type	enum in

Version	Status	Evidence
25.000	documented	SRC-749 p.302, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	documented	SRC-741 p.338, same grammar as 26.120
26.101	documented	SRC-725 p.340, same grammar as 26.120
26.120	verified	reports/compat/CMP-26120_2026-09-08_rotor-path.yaml
26.121	verified	reports/compat/CMP-26121_2026-08-08_savedstate2.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.346, unchanged from SRC-750 p.346
26.124	verified	reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.346, the SRC-751 file, carried from 26.123

SET_CROSSFLOW_SEPARATION_AXISYMMETRIC

Phase init, layout inline. Manual: SRC-741 p.340.

Axisymmetric vortex shedding for the cross-flow separation model.

Argument	Specification
mode	enum in

Version	Status	Evidence
26.100	documented	SRC-741 p.340

SET_CROSSFLOW_SEPARATION_BOUNDARIES

Phase init, layout payload_lines. Manual: SRC-741 p.339.

Adds boundaries to the cross-flow separation list, with the -1 form of the axial command above (SRC-741 pp.339-340).

Argument	Specification
num_boundaries	int
boundary_indices	int_list (optional)

Version	Status	Evidence
25.000	documented	SRC-749 p.303, same grammar as 26.100
25.100	documented	SRC-748 p.317, same grammar as 26.100
26.000	documented	SRC-747 p.316, same grammar as 26.100
26.100	documented	SRC-741 p.339

SET_CROSSFLOW_SEPARATION_CP

Phase init, layout inline. Manual: SRC-747 p.316.

Sets the mean diameter of the body the cross-flow separation model is applied to, which the model needs because the critical pressure coefficient it uses depends on the cross-sectional scale. Strictly positive, in the simulation length units. Documented by the three pre-26.100 editions. The boundary selection commands beside it on the same page, SET_CROSSFLOW_SEPARATION_BOUNDARIES and its delete, are on every build; this one scalar is what stops being printed.

Argument	Specification
mean_diameter	float

Version	Status	Evidence
25.000	documented	SRC-749 p.304, this edition documents it
25.100	documented	SRC-748 p.317, this edition documents it
26.000	documented	SRC-747 p.316, this edition documents it
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.

SET_CROSSFLOW_SEPARATION_DIAMETER

Phase init, layout inline. Manual: SRC-741 p.339.

Maximum diameter of the body carrying the cross-flow separation model. One diameter applies to the whole list, which is the difference from the later named models, where the diameter belongs to each assignment.

Argument	Specification
diameter	float [simulation length units]

Version	Status	Evidence
26.100	documented	SRC-741 p.339

SET_SOLVER_MODEL

Phase init, layout inline. Manual: SRC-749 p.302.

Selects the flow model the solver runs. A standalone command on 25.000 alone, and the successor is not a guess: 25.100 stops printing it and, on the same edition, INITIALIZE_SOLVER gains a SOLVER_MODEL argument that its 25.000 form does not have. The setting moved into the initialization block in the edition that dropped the command. THE TOKENS CHANGE TOO, and a first draft of this note said they did not. This command takes INCOMPRESSIBLE, SUBSONIC, TRANSONIC and LOW_ORDER_SUPERSONIC. The argument that replaces it takes INCOMPRESSIBLE, SUBSONIC_PRANDTL_GLAUERT, TRANSONIC_FIELD_PANEL, SUPERSONIC_LINEAR_DOUBLET, TANGENT_CONE and MODIFIED_NEWTONIAN. Only INCOMPRESSIBLE is common to both, so a script porting forward changes where the token is written AND which token, and three of the four old names have no identical successor. No edition states the mapping between the two vocabularies, so none is recorded here. The names suggest the obvious pairs and suggesting is not evidence: SUBSONIC and SUBSONIC_PRANDTL_GLAUERT may name the same model or a narrowing of it, and LOW_ORDER_SUPERSONIC has two plausible partners among the newer six. Choosing one would put a physics claim in a grammar record.

Argument	Specification
type	enum in

Version	Status	Evidence
25.000	documented	SRC-749 p.302, 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: INITIALIZE_SOLVER
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: INITIALIZE_SOLVER
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: INITIALIZE_SOLVER
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: INITIALIZE_SOLVER
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: INITIALIZE_SOLVER
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: INITIALIZE_SOLVER

SET_SOLVER_STEADY

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

Version	Status	Evidence
25.000	documented	SRC-749 p.302, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	verified	reports/compat/CMP-26100_2026-08-08_full.yaml
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.346, unchanged from SRC-750 p.346
26.124	verified	reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.346, the SRC-751 file, carried from 26.123

SET_SOLVER_UNSTEADY

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

Physical time stepping. For rotary cases the manual recommends 8 to 12 degrees of blade rotation per time step and at least two full rotations (SRC-003 p.210).

Argument	Specification
time_iterations	int
delta_time	float [s]

Version	Status	Evidence
25.000	documented	SRC-749 p.302, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	verified	reports/compat/CMP-26100_2026-08-08_full.yaml
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.346, unchanged from SRC-750 p.346
26.124	verified	reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.346, the SRC-751 file, carried from 26.123

SET_SOLVER_VISCOUS_COUPLING

Phase init, layout inline. Manual: SRC-003 p.341.

Couples the semi-empirical boundary layer model to the potential flow solution. Attached-flow viscosity only; stall capture also needs a flow separation model assignment (SRC-003 pp.207-208).

Argument	Specification
mode	enum in

Version	Status	Evidence
25.000	documented	SRC-749 p.302, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	documented	SRC-741 p.338, same grammar as 26.120
26.101	documented	SRC-725 p.340, same grammar as 26.120
26.120	verified	reports/compat/CMP-26120_2026-09-08_rotor-path.yaml
26.121	verified	reports/compat/CMP-26121_2026-08-08_savedstate2.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.346, unchanged from SRC-750 p.346
26.124	verified	reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.346, the SRC-751 file, carried from 26.123

SET_SURFACE_ROUGHNESS

Phase init, layout inline. Manual: SRC-003 p.341.

Surface roughness height for the boundary layer model, in NANOMETRES, which the manual states and which is worth carrying because every other length in this database is a metre, a coordinate-system unit or an explicit UNITS argument. A height read as millimetres instead of nanometres is a roughness a million times the one intended. Zero means a smooth surface, which the manual states, so the argument has no separate toggle and the value carries the choice.

Argument	Specification
roughness_height	float [nm]

Version	Status	Evidence
25.000	documented	SRC-749 p.302, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	documented	SRC-741 p.338, same grammar as 26.120
26.101	documented	SRC-725 p.340, same grammar as 26.120
26.120	documented	SRC-003 p.341
26.121	documented	SRC-740 p.344, same grammar as 26.120
26.123	documented	SRC-751 p.346, unchanged from SRC-750 p.346
26.124	documented	SRC-752 p.346, the SRC-751 file, carried from 26.123; not run on 26.124

SET_THIN_BOUNDARIES

Phase init, layout payload_lines. Manual: SRC-003 p.343.

Marks boundaries as thin, so the solver treats both faces of a surface rather than one. The indices follow on the next line, comma separated, and -1 marks every mesh boundary and the index line is IGNORED rather than absent, which the manual says in those terms; the index list is therefore optional here as on its siblings. Absent from the February 2026 edition, whose separation family is the per-mechanism one recorded above; thin boundaries arrive with the redesign in May.

Argument	Specification
num_boundaries	int
boundary_indices	int_list (optional)

Version	Status	Evidence
26.101	documented	SRC-725 p.341, same grammar as 26.120
26.120	documented	SRC-003 p.343
26.121	documented	SRC-740 p.346, same grammar as 26.120
26.123	documented	SRC-751 p.348, unchanged from SRC-750 p.348
26.124	documented	SRC-752 p.348, the SRC-751 file, carried from 26.123; not run on 26.124

SET_VALAREZO_SEPARATION_BOUNDARIES

Phase init, layout payload_lines. Manual: SRC-741 p.339.

Adds boundaries to the Valarezo maximum-lift criterion list, with the -1 form of the axial command above. The manual writes this name in the function header and a different one, VALAREZO_CRITERION, in the sample directly beneath it; RPT-018 probed both and the solver accepts this spelling and does not recognize the other.

Argument	Specification
num_boundaries	int
boundary_indices	int_list (optional)

Version	Status	Evidence
26.100	documented	SRC-741 p.339

SET_VISCOUS_EXCLUDED_BOUNDARIES

Phase init, layout payload_lines. Manual: SRC-003 p.341.

Excludes the listed boundaries from viscous coupling; the indices follow on the next line as comma-separated values. Documented unchanged in the four editions read then; the three added on 2026-08-05 were read from their own pages, not inherited.

Argument	Specification
num_boundaries	int
boundary_indices	int_list

Version	Status	Evidence
25.000	documented	SRC-749 p.303, same grammar as 26.120
25.100	documented	SRC-748 p.316, same grammar as 26.120
26.000	documented	SRC-747 p.315, same grammar as 26.120
26.100	documented	SRC-741 p.338, same grammar as 26.120
26.101	documented	SRC-725 p.340, same grammar as 26.120
26.120	documented	SRC-003 p.341
26.121	verified	reports/compat/CMP-26121_2026-08-08_savedstate2.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.346, unchanged from SRC-750 p.346
26.124	verified	reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.346, the SRC-751 file, carried from 26.123

SOLVER_STABILIZATION

Phase init, layout inline. Manual: SRC-003 p.346.

Maximum level of stabilization applied to the main convergence, dimensionless, from 0 to 1. The manual states that 0 is the same as disabling it, so this is a strength rather than a switch, and it takes intermediate values. No edition states a default. Absent from the February 2026 edition, so no 26.100 row. ITS SRC-740 PAGE BREAKS THE +3 RULE AND THE NOTE IS RIGHT ANYWAY. Every SRC-003 page maps to SRC-740 plus three, which commands/_meta states and about forty-five notes obey, so p.346 here should read p.349. It reads p.348 because it was MEASURED: the three commands sharing SRC-003 p.346 split across two pages in the hotfix edition, this one landing on 348 and the other two on 349. A page shift is a rule about a document's average and not about a page boundary, so the reading wins over the arithmetic. A 2026-08-08 review pass reported this as a paste error from the arithmetic alone; it is not one, and this paragraph exists so the next reader measures before correcting it.

Argument	Specification
value	float

Version	Status	Evidence
26.101	documented	SRC-725 p.345, same grammar as 26.120
26.120	verified	reports/compat/CMP-26120_2026-09-08_rotor-path.yaml
26.121	documented	SRC-740 p.348, same grammar as 26.120
26.123	verified	reports/compat/CMP-26123_2026-09-08_rotor-path.yaml; SRC-751 p.350, unchanged from SRC-750 p.350
26.124	documented	SRC-752 p.350, the SRC-751 file, carried from 26.123; not run on 26.124

VALAREZO_CRITERION

Phase init, layout inline. Manual: SRC-747 p.316.

Enables the Valarezo pressure-difference criterion for predicting the onset of separation. Documented by the three pre-26.100 editions and by none after them. The 26.100 editions document a separate Valarezo family of their own, which is why the absence of this switch is worth stating rather than reading as the capability leaving.

Argument	Specification
mode	enum in

Version	Status	Evidence
25.000	documented	SRC-749 p.303, this edition documents it
25.100	documented	SRC-748 p.317, this edition documents it
26.000	documented	SRC-747 p.316, this edition documents it
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.