Solver contours

Commands of the solver_contours chapter of the database, 1 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.

SET_SCENE_CONTOUR

Phase analysis, layout inline. Manual: SRC-003 pp.349-350.

Selects the scalar field drawn on the surfaces of the solver scene. THE VALUES ARE LOWERCASE AND THAT IS NOT A TRANSCRIPTION CHOICE. Every other closed set in this database is uppercase, because that is how the manual prints them; this page prints these 32 in lower case, and they are recorded as printed. THE 26.123 ADDITIONS BREAK THAT AND ARE ALSO RECORDED AS PRINTED. SRC-751 p.355 appends four values spelled FSI_dx, FSI_dy, FSI_dz and FSI_displacement, mixed case, to the same table whose other thirty-two are lower case. So the paragraph above stops holding for the command and holds only for the four editions it names; the rule that produced it, record what the page prints, is what stays. Matching is case-insensitive here as everywhere in this database and normalises to the declared member, so a caller writing fsi_dx still emits FSI_dx. THE 26.123 ROW RESTATES THE WHOLE LIST rather than the four it adds. A per-version override merges argument KEYS and never merges list items, so a row naming only the additions would leave that build with four values and no velocity_magnitude. WHAT THE FOUR DRAW IS DOCUMENTED ON A DIFFERENT PAGE, and citing only p.355 would leave a reader with four tokens and no statement of what they mean. SRC-751 p.248 lists a group of FSI displacement output parameters in the solver's own parameter list: mesh node displacement in X, Y and Z, and the magnitude of that displacement. Those four are what these four contour values draw, one for one. THAT GROUP STATES NO UNIT, and the silence is the page's rather than this database's. Rows a few lines above it on the same page say in so many words that a contour has dimensional length units; the displacement rows say nothing at all. A displacement is a length and the simulation length unit is the only candidate, but the page does not say so and neither does this note, on the precedent of EXPORT_BL_VELOCITY_PROFILE, whose unit is left unstated for the same reason. Nothing in this package reads that output group: no edition gives its file format and no run has produced one, so there is nothing to parse against. What a caller writes does not matter and what the SCRIPT carries does: enum matching is case-insensitive across this whole database and normalises to the declared member, so MACH_NUMBER and mach_number both emit mach_number. Whether the solver itself cares about the case is untested; recording the page's own spelling is what makes the question moot for anyone using this emitter. THE PAGE HAS NO RUNNABLE SAMPLE, in any of the five editions read. Its sample line prints the placeholder rather than a value, so unlike most of this manual there is no example call to compare the table against. The 32 tokens, and the 36 of the newest edition, are the table's alone. none is one of them, and it is the way to clear the contour rather than a way of saying nothing: there is no separate clear command. Several tokens name boundary-layer fields, which exist only once a viscous solution has been computed. Nothing here can check that, so selecting one before the run is a scene showing an empty field rather than an error. THE TWO 25 EDITIONS WRITE THIS COMMAND AS A KEYWORD BLOCK and carry no row here because of it. They print KEY VALUE lines until a terminator, where 26.000 onward prints the arguments inline. A version row can override the argument grammar and cannot override the layout, so a row for those editions would emit the newer shape under an older build's citation, which is worse than refusing to emit at all. The reading exists and is withheld deliberately; the schema gap is PLN-20260810-1200.

Argument	Specification
variable	enum in

Version	Status	Evidence
26.000	documented	SRC-747 p.322, same grammar as 26.120
26.100	documented	SRC-741 pp.345-346, same grammar as 26.120
26.101	documented	SRC-725 pp.348-349, same grammar as 26.120
26.120	documented	SRC-003 pp.349-350
26.121	documented	SRC-740 pp.352-353, same grammar as 26.120
26.123	documented	SRC-751 p.355, four contour values added
26.124	documented	SRC-752 p.355, the SRC-751 file, carried from 26.123; not run on 26.124