Motion definitions¶
Commands of the motion_definitions chapter of the database, 32 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_NEW_6DOF_CUSTOM_FORCE¶
Phase setup, layout inline. Manual: SRC-003 p.335.
A force profile read from a text file, the path on the following line. The two tokens use UNDERSCORES where the motion table's VELOCITY-TIME and POSITION-TIME use hyphens, which is the manual's inconsistency and is mirrored rather than harmonised.
| Argument | Specification |
|---|---|
motion_id |
int |
type |
enum in |
filename |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.295, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.309, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.308, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.331, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.334, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.335 |
| 26.121 | documented | SRC-740 p.338, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.340, unchanged from SRC-750 p.340 |
| 26.124 | documented | SRC-752 p.340, the SRC-751 file, carried from 26.123; not run on 26.124 |
CREATE_NEW_6DOF_EXTERNAL_FORCE¶
Phase setup, layout inline. Manual: SRC-003 p.334.
A force applied at a point of the body for a window of time. Both the application point and the force vector are in the BODY frame. T_START and DELTA_T are SECONDS, and the second is a DURATION rather than an end time: the force runs from T_START for DELTA_T. Reading it as an end time would apply the force for the wrong interval and nothing would say so.
| Argument | Specification |
|---|---|
motion_id |
int |
x |
float |
y |
float |
z |
float |
t_start |
float [s] |
delta_t |
float [s] |
fx |
float |
fy |
float |
fz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.295, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.309, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.308, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.331, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.333, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.334 |
| 26.121 | documented | SRC-740 p.337, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.339, unchanged from SRC-750 p.339 |
| 26.124 | documented | SRC-752 p.339, the SRC-751 file, carried from 26.123; not run on 26.124 |
CREATE_NEW_6DOF_SPRING_FORCE¶
Phase setup, layout inline. Manual: SRC-003 p.335.
A spring attached to the body. ELEVEN arguments, and the manual's heading WRAPS with SPRING_RATE alone on the second line, which is one of the five wrapped signatures in the scripting reference. Three lengths and none of them interchangeable. FREE_LENGTH is where the spring stops pushing, beyond which it applies no force at all; SOLID_LENGTH is the fully compressed length it cannot pass; and INITIAL_LENGTH is where it starts. All three must be greater than zero, which the manual states and this database does not enforce. SPRING_RATE is in NEWTONS PER METRE, which the manual states, and it is the only unit given on this command: the point and the axis carry none, and the axis is a direction from the spring's base outwards rather than a position.
| Argument | Specification |
|---|---|
motion_id |
int |
x |
float |
y |
float |
z |
float |
nx |
float |
ny |
float |
nz |
float |
free_length |
float |
solid_length |
float |
initial_length |
float |
spring_rate |
float [N/m] |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.295, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.309, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.308, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.332, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.334, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.335 |
| 26.121 | documented | SRC-740 p.338, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.340, unchanged from SRC-750 p.340 |
| 26.124 | documented | SRC-752 p.340, the SRC-751 file, carried from 26.123; not run on 26.124 |
CREATE_NEW_MOTION¶
Phase setup, layout inline. Manual: SRC-003 p.332.
Rotary motion is the blade-resolved alternative to the actuator disc surrogate (SRC-003 p.234); it requires the unsteady solver. The February 2026 build, and 25.100 and 26.000 before it, call this motion type EUCLIDEAN and every later edition calls it ROTARY, which is why those three override the grammar above rather than sharing it. The rename is not a relabel of one capability: 26.100's Euclidean motion is a general rigid-body kinematic motion set by velocity, angular velocity and their accelerations (SRC-741 pp.228, 329), and the later Rotary motion is rotation alone, set by axis and RPM (SRC-725 p.234). Four commands that configure the February form (SET_MOTION_VELOCITY, SET_MOTION_ACCELERATION, SET_MOTION_ANGULAR_VELOCITY, SET_MOTION_ANGULAR_ACCELERATION) exist in no later edition, and SET_MOTION_ROTOR_AXIS and SET_MOTION_ROTOR_RPM exist in no earlier one. Emitting the later vocabulary onto a February script would name a type that build has never heard of.
| Argument | Specification |
|---|---|
type |
enum in |
| Version | Status | Evidence |
|---|---|---|
| 25.100 | documented | SRC-748 p.306 documents the February form, type EUCLIDEAN, in its parameter table and its sample alike. Recorded until 2026-09-15 with the 26.120 grammar, which put ROTARY in an edition that never names it; re-read that day from the page. |
| 26.000 | documented | SRC-747 p.305 documents the February form, type EUCLIDEAN, in its parameter table and its sample alike. Recorded until 2026-09-15 with the 26.120 grammar; re-read that day from the page. |
| 26.100 | documented | SRC-741 p.328 documents the same one-argument signature with a different first token: the February 2026 edition calls that motion type EUCLIDEAN, and its parameter table and its sample agree with each other on it. |
| 26.101 | documented | SRC-725 p.331, the first edition naming the type ROTARY |
| 26.120 | documented | SRC-003 p.332 |
| 26.121 | documented | SRC-740 p.335, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.337, unchanged from SRC-750 p.337 |
| 26.124 | documented | SRC-752 p.337, the SRC-751 file, carried from 26.123; not run on 26.124 |
CREATE_NEW_MOTION_6DOF¶
Phase setup, layout bare. Manual: SRC-749 p.291.
Creates a six-degree-of-freedom motion definition, where the trajectory is solved from the aerodynamic loads rather than prescribed. One of the four type-specific creation commands 26.100 folds into CREATE_NEW_MOTION.
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.291, 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
CREATE_NEW_MOTION_CUSTOM¶
Phase setup, layout bare. Manual: SRC-749 p.291.
Creates a custom motion definition, whose position history comes from a file rather than from a rule. One of the four type-specific creation commands 26.100 folds into CREATE_NEW_MOTION.
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.291, 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
CREATE_NEW_MOTION_EUCLIDEAN¶
Phase setup, layout bare. Manual: SRC-749 p.291.
Creates a Euclidean motion definition. On 25.000 each motion type is its own bare command, and 26.100 replaces all four with CREATE_NEW_MOTION taking the type as an argument. THE FOUR DID NOT SURVIVE AS THREE PLUS ONE. CREATE_NEW_MOTION accepts EUCLIDEAN, 6DOF and CUSTOM, so the FSI type has no argument value on the newer builds and the fourth command is the only one of the four with nothing to become.
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.291, 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
| 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: CREATE_NEW_MOTION |
CREATE_NEW_MOTION_FSI¶
Phase setup, layout bare. Manual: SRC-749 p.291.
Creates a fluid-structure-interaction motion definition, where the surface deflects under the aerodynamic loads and the deflection changes the loads. IT IS THE ONE OF THE FOUR WITH NO SUCCESSOR RECORDED, and that is why no successor is named rather than an oversight. The other three become argument values of CREATE_NEW_MOTION on 26.100; that command's documented type list is EUCLIDEAN, 6DOF and CUSTOM, with no FSI among them. Whether the capability moved elsewhere or left is a question about the solver, and nothing here has measured it.
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.291, 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. |
DELETE_6DOF_EXTERNAL_FORCE¶
Phase setup, layout inline. Manual: SRC-003 p.335.
Deletes one external force from a motion by index. The manual names no delete for the spring or the custom force, and this entry does not assume the FORCE_ID space covers them.
| Argument | Specification |
|---|---|
motion_id |
int |
force_id |
int |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.296, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.310, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.309, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.332, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.334, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.335 |
| 26.121 | documented | SRC-740 p.338, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.340, unchanged from SRC-750 p.340 |
| 26.124 | documented | SRC-752 p.340, the SRC-751 file, carried from 26.123; not run on 26.124 |
DELETE_MOTION¶
Phase setup, layout inline. Manual: SRC-003 p.336.
| Argument | Specification |
|---|---|
motion_id |
int |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.296, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.310, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.309, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.333, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.335, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.336 |
| 26.121 | documented | SRC-740 p.339, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.341, unchanged from SRC-750 p.341 |
| 26.124 | documented | SRC-752 p.341, the SRC-751 file, carried from 26.123; not run on 26.124 |
EXPORT_6DOF_TRAJECTORY¶
Phase setup, layout inline. Manual: SRC-003 p.335.
Writes a motion's trajectory tables to a file, the path on the following line. Its phase is SETUP rather than export, and the reason is the opposite of the one that put CAD_CREATE_CURVE_EXPORT_CCS in geometry: the phase is where the command may legally sit, and this one belongs with the motion definition it names. There is no evidence about when the trajectory becomes available to write, so the entry does not imply that a script may call it before the solver has produced one.
| Argument | Specification |
|---|---|
motion_id |
int |
filename |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.296, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.310, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.309, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.332, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.334, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.335 |
| 26.121 | documented | SRC-740 p.338, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.340, unchanged from SRC-750 p.340 |
| 26.124 | documented | SRC-752 p.340, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_6DOF_MOTION_SYMMETRY_LOADS¶
Phase setup, layout inline. Manual: SRC-003 p.334.
Includes the loads on the symmetry boundary in a 6DOF motion, which the page's own sample comment describes as converting the motion into a longitudinal 3DOF. THE SAMPLE CALLS A SHORTER NAME THAN THE HEADING. Every edition prints the heading SET_6DOF_MOTION_SYMMETRY_LOADS and a sample line reading SET_6DOF_MOTION, and the February edition's sample writes SET_3DOF_MOTION instead. The heading is recorded, because the Script Index agrees with it and because the measured record of this repository is that a heading has won every case a solver has settled against a sample; the mirror curve, where the index sides with the sample, is the one held for a probe instead (PLN-20260806-1200).
| Argument | Specification |
|---|---|
motion_id |
int |
symmetry_loads |
enum in |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.294, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.309, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.308, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.331, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.333, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.334 |
| 26.121 | documented | SRC-740 p.337, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.339, unchanged from SRC-750 p.339 |
| 26.124 | documented | SRC-752 p.339, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_6DOF_ACTIVE_VARIABLES¶
Phase setup, layout payload_lines. Manual: SRC-003 p.334.
Frees or locks each degree of freedom, one per line after the command: U, V and W are the velocity components and P, Q and R the angular ones, each followed by ENABLE or DISABLE. The six lines are recorded as preformatted tokens rather than as six enum arguments, the same convention as the per-surface lines of INITIALIZE_SOLVER, so the pairing of a name with a toggle is the caller's to get right and this database records the shape. The LENGTH is refused, because the manual fixes it at six and nothing counts the lines, so a short payload would make the solver read the next command as data. The CONTENT is not: six lines naming the same variable twice, or misspelling one, still emit. Locking a subset is how a 6DOF motion becomes a constrained one, and the manual's own sample leaves Q and R free. The page describes that reduction as a longitudinal 3DOF, but on the sample of the NEXT command rather than this one, so the phrase is not this entry's to borrow.
| Argument | Specification |
|---|---|
motion_id |
int |
variables |
str_list |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.294, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.308, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.307, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.331, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.333, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.334 |
| 26.121 | documented | SRC-740 p.337, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.339, unchanged from SRC-750 p.339 |
| 26.124 | documented | SRC-752 p.339, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_6DOF_INITIAL_ANGULAR_VELOCITY¶
Phase setup, layout inline. Manual: SRC-003 p.334.
Initial angular velocity of a 6DOF body, in the body coordinate system. No unit is stated, and unlike SET_MOTION_ROTOR_RPM, which names revolutions per minute, this one leaves it open.
| Argument | Specification |
|---|---|
motion_id |
int |
wx |
float |
wy |
float |
wz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.294, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.308, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.307, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.330, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.333, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.334 |
| 26.121 | documented | SRC-740 p.337, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.339, unchanged from SRC-750 p.339 |
| 26.124 | documented | SRC-752 p.339, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_6DOF_INITIAL_VELOCITY¶
Phase setup, layout inline. Manual: SRC-003 p.334.
Initial velocity of a 6DOF body, in the BODY coordinate system, not the reference one its gravity vector uses. No unit is stated.
| Argument | Specification |
|---|---|
motion_id |
int |
vx |
float |
vy |
float |
vz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.294, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.308, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.307, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.330, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.333, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.334 |
| 26.121 | documented | SRC-740 p.337, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.339, unchanged from SRC-750 p.339 |
| 26.124 | documented | SRC-752 p.339, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_ACCELERATION¶
Phase setup, layout inline. Manual: SRC-741 p.329.
Acceleration vector of a February 2026 Euclidean motion, in the motion definition coordinate system. Its parameter row describes the three components as a VELOCITY vector, which is the row written for SET_MOTION_VELOCITY above carried across; the command name and the sample both say acceleration.
| Argument | Specification |
|---|---|
motion_id |
int |
ax |
float |
ay |
float |
az |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.292, same grammar as 26.100 |
| 25.100 | documented | SRC-748 p.307, same grammar as 26.100 |
| 26.000 | documented | SRC-747 p.306, same grammar as 26.100 |
| 26.100 | documented | SRC-741 p.329 |
SET_MOTION_ANGULAR_ACCELERATION¶
Phase setup, layout inline. Manual: SRC-741 p.329.
Angular acceleration vector of a February 2026 Euclidean motion, in the motion definition coordinate system.
| Argument | Specification |
|---|---|
motion_id |
int |
wax |
float |
way |
float |
waz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.293, same grammar as 26.100 |
| 25.100 | documented | SRC-748 p.307, same grammar as 26.100 |
| 26.000 | documented | SRC-747 p.306, same grammar as 26.100 |
| 26.100 | documented | SRC-741 p.329 |
SET_MOTION_ANGULAR_VELOCITY¶
Phase setup, layout inline. Manual: SRC-741 p.329.
Angular velocity vector of a February 2026 Euclidean motion, in the motion definition coordinate system. The scripting page states no unit, and the sample's -450.5 settles nothing. The rotor tutorial of the same manual gives RAD/S for the dialog field (SRC-741 p.394), and on 26.000 a rotor set this way in rad/s turned a blade exactly as a ROTARY motion at the same speed in rev/min turned it on 26.120, in the same sense (RPT-049). helpers.rotary_motion writes a rotor this way, in rad/s with the rotor mark, on 25.100 and 26.000, and in rev/min without the mark on 26.100 (see that version's note).
| Argument | Specification |
|---|---|
motion_id |
int |
wx |
float |
wy |
float |
wz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.292, same grammar as 26.100 |
| 25.100 | documented | SRC-748 p.307, same grammar as 26.100 |
| 26.000 | documented | SRC-747 p.306, same grammar as 26.100 |
| 26.100 | documented | The unit is NOT measured on this build. helpers.rotary_motion writes the rotor speed here in rev/min, with no rotor mark, by a maintainer decision (RPT-051), while this build's manual tutorial gives rad/s for the dialog field (the notes below). |
SET_MOTION_BOUNDARIES¶
Phase setup, layout payload_lines. Manual: SRC-003 p.332.
Assigns geometry boundaries to the motion; the comma-separated index line follows. NUM_BOUNDARIES -1 selects all boundaries and takes no index line.
| Argument | Specification |
|---|---|
motion_id |
int |
num_boundaries |
int |
boundary_indices |
int_list (optional) |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.291, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.306, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.305, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.328, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.331, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.332 |
| 26.121 | documented | SRC-740 p.335, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.337, unchanged from SRC-750 p.337 |
| 26.124 | documented | SRC-752 p.337, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_COORDINATE_SYSTEM¶
Phase setup, layout inline. Manual: SRC-003 p.332.
| Argument | Specification |
|---|---|
motion_id |
int |
coordinate_system_id |
int |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.292, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.306, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.305, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.328, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.331, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.332 |
| 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.337, unchanged from SRC-750 p.337 |
| 26.124 | verified | reports/compat/CMP-26124_2026-09-14_full-sim.yaml; SRC-752 p.337, the SRC-751 file, carried from 26.123 |
SET_MOTION_CUSTOM_TABLE¶
Phase setup, layout inline. Manual: SRC-003 p.333.
Reads a motion from a table in a text file, the path on the line after the command. THE MOTION ID IS SECOND HERE AND FIRST EVERYWHERE ELSE IN THIS CHAPTER. Every other motion command opens with MOTION_ID; this one opens with TYPE. A caller who writes the id first passes it where the type belongs and the token is refused, which is the good outcome, but the reason is worth having written down. The two type tokens carry a HYPHEN, not an underscore, which is unusual in this vocabulary and is the manual's own spelling.
| Argument | Specification |
|---|---|
type |
enum in |
motion_id |
int |
filename |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.293, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.307, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.306, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.330, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.332, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.333 |
| 26.121 | documented | SRC-740 p.336, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.338, unchanged from SRC-750 p.338 |
| 26.124 | documented | SRC-752 p.338, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_FSI_EXECUTABLE¶
Phase setup, layout inline. Manual: SRC-003 pp.335-336.
FSI seam (FR-23): FlightStream calls the external structural executable per coupling step; the executable path follows on the line after the inline arguments. EXPORT_LOAD_DISTRIBUTIONS also writes the aerodynamic load distributions file alongside the default interpolated loads file. Dry run finding (2026-07-21, reports/RPT-005): build 7012026 rejects this command as unrecognized despite the manual-exact grammar; the implemented interface is the Aeroelastic Coupling Toolbox family (SRC-003 pp.375-376, aeroelastic_coupling.yaml). Candidate broken; promotion via the next validity sweep (PLN-019).
| Argument | Specification |
|---|---|
motion_id |
int |
show_console |
enum in |
export_load_distributions |
enum in |
executable_path |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.296, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.310, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.309, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.332, same grammar as 26.120 |
| 26.101 | documented | SRC-725 pp.334-335, same grammar as 26.120 |
| 26.120 | documented | SRC-003 pp.335-336 |
| 26.121 | documented | SRC-740 p.338, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.340, unchanged from SRC-750 p.340 |
| 26.124 | documented | SRC-752 p.340, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_FSI_STRUCTURAL_NODES¶
Phase setup, layout inline. Manual: SRC-003 p.336.
Imports the structural displacement node set; the file path follows on the line after the motion index. Dry run finding (2026-07-21, reports/RPT-005): build 7012026 rejects this command as unrecognized; the implemented import is IMPORT_AEROELASTIC_STRUCTURAL_NODES (SRC-003 p.375, aeroelastic_coupling.yaml). Candidate broken; promotion via the next validity sweep (PLN-019).
| Argument | Specification |
|---|---|
motion_id |
int |
nodes_path |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.296, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.310, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.309, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.332, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.335, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.336 |
| 26.121 | documented | SRC-740 p.339, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.341, unchanged from SRC-750 p.341 |
| 26.124 | documented | SRC-752 p.341, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_GRAVITY¶
Phase setup, layout inline. Manual: SRC-003 p.333.
Gravity vector for a 6DOF motion, in the REFERENCE coordinate system. Its neighbours SET_MOTION_6DOF_INITIAL_VELOCITY and CREATE_NEW_6DOF_EXTERNAL_FORCE take their vectors in the BODY frame, so a script that sets all three reads three vectors in two different systems and the manual marks the difference only in the parameter rows. It is a vector rather than a magnitude, so the direction is the caller's: the sample points it along negative Z.
| Argument | Specification |
|---|---|
motion_id |
int |
gx |
float |
gy |
float |
gz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.294, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.308, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.307, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.330, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.332, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.333 |
| 26.121 | documented | SRC-740 p.336, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.338, unchanged from SRC-750 p.338 |
| 26.124 | documented | SRC-752 p.338, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_IS_ROTOR¶
Phase setup, layout inline. Manual: SRC-741 p.329.
Marks a February 2026 motion as a rotor or propeller. AXIS is the SLIPSTREAM CONVECTION DIRECTION rather than an axis of rotation, which the parameter row states and the argument name does not; the rotation axis of a later ROTARY motion is a different command, SET_MOTION_ROTOR_AXIS, and takes the dual letter-or-index form this one does not.
| Argument | Specification |
|---|---|
motion_id |
int |
flag |
enum in |
axis |
enum in |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.293, same grammar as 26.100 |
| 25.100 | documented | SRC-748 p.307, same grammar as 26.100 |
| 26.000 | documented | SRC-747 p.306, same grammar as 26.100. Run 2026-09-15 outside the compatibility harness, so still documented: every two-argument form let the script go on to write its log, the form with the axis left out did not, and a blade marked this way turned as the 26.120 rotary motion turns it (RPT-049). |
| 26.100 | removed | reports/RPT-049_a-rotor-on-the-builds-before-the-rotary-motion_2026-09-15.md; Measured 2026-09-15: the 26.100 manual prints the command and the 26.100 solver answers it as an unrecognized command in every form tried, the same answer and the same stopped script it gives a name no build has, while 26.000 runs it; its executable carries no command of this name. So 26.100 has no scripted way to mark a motion as a rotor, and helpers.rotary_motion writes the rotor there without it (RPT-051) |
SET_MOTION_MASS_PROPERTIES¶
Phase setup, layout inline. Manual: SRC-003 p.333.
Mass and inertia tensor of a 6DOF body. MASS is in KILOGRAMS, which the manual states; the six inertia components are named as moments and products of inertia with NO unit given, so none is recorded here even though kg m2 is the only reading consistent with the mass. The order is the three moments and then the three products, and the products are IXY, IYZ, IZX rather than the IXY, IXZ, IYZ a reader may expect: the third pairs Z with X and not X with Z.
| Argument | Specification |
|---|---|
motion_id |
int |
mass |
float [kg] |
ixx |
float |
iyy |
float |
izz |
float |
ixy |
float |
iyz |
float |
izx |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.293, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.308, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.307, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.330, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.332, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.333 |
| 26.121 | documented | SRC-740 p.336, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.338, unchanged from SRC-750 p.338 |
| 26.124 | documented | SRC-752 p.338, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_MOVING_FRAMES¶
Phase setup, layout payload_lines. Manual: SRC-003 p.332.
Attaches user-defined local frames to the motion; -1 selects all local coordinate systems and takes no index line.
| Argument | Specification |
|---|---|
motion_id |
int |
num_frames |
int |
frame_indices |
int_list (optional) |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.291, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.306, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.305, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.328, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.331, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.332 |
| 26.121 | documented | SRC-740 p.335, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.337, unchanged from SRC-750 p.337 |
| 26.124 | documented | SRC-752 p.337, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_ROTOR_AXIS¶
Phase setup, layout inline. Manual: SRC-003 p.333.
| Argument | Specification |
|---|---|
motion_id |
int |
axis |
enum in |
| Version | Status | Evidence |
|---|---|---|
| 26.101 | documented | SRC-725 p.332, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.333 |
| 26.121 | documented | SRC-740 p.336, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.338, unchanged from SRC-750 p.338 |
| 26.124 | documented | SRC-752 p.338, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_ROTOR_RPM¶
Phase setup, layout inline. Manual: SRC-003 p.333.
| Argument | Specification |
|---|---|
motion_id |
int |
rpm |
float [rev/min] |
| Version | Status | Evidence |
|---|---|---|
| 26.101 | documented | SRC-725 p.332, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.333 |
| 26.121 | documented | SRC-740 p.336, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.338, unchanged from SRC-750 p.338 |
| 26.124 | documented | SRC-752 p.338, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_SLIPSTREAM_WAKE_STABILIZATION¶
Phase setup, layout inline. Manual: SRC-003 p.333.
Stabilizes the slipstream wake of a rotor motion. NUM_BLADES is per PROPELLER rather than a total across the motion, which the manual states. The February 2026 edition takes two arguments and not three, so 26.100 overrides the grammar rather than sharing it. Emitting the blade count onto a February script would pass an argument that build does not read.
| Argument | Specification |
|---|---|
motion_id |
int |
wake_stabilization |
enum in |
num_blades |
int |
| Version | Status | Evidence |
|---|---|---|
| 26.100 | documented | SRC-741 pp.329-330 documents a TWO-argument form: the February 2026 edition has no NUM_BLADES, and the blade count arrives with the rotary motion in the May edition. |
| 26.101 | documented | SRC-725 p.332, the first edition with NUM_BLADES |
| 26.120 | documented | SRC-003 p.333 |
| 26.121 | documented | SRC-740 p.336, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.338, unchanged from SRC-750 p.338 |
| 26.124 | documented | SRC-752 p.338, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_START_TIME¶
Phase setup, layout inline. Manual: SRC-003 p.332.
Start of the motion within the solver physical time; enables converging a steady base flow before the motion begins.
| Argument | Specification |
|---|---|
motion_id |
int |
start_time |
float [s] |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.292, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.306, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.305, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.328, same grammar as 26.120; never probed on this build, so the abort measured on 26.120 and 26.121 is not claimed here |
| 26.101 | broken | reports/compat/CMP-26101_2026-08-08_full.yaml; script processing aborted at the command: the log exported before it exists, the one after it never appeared (END sentinel missing) |
| 26.120 | broken | reports/compat/CMP-26120_2026-08-08_full.yaml; script processing aborted at the command: the log exported before it exists, the one after it never appeared (END sentinel missing) |
| 26.121 | broken | reports/compat/CMP-26121_2026-08-08_full.yaml; script processing aborted at the command: the log exported before it exists, the one after it never appeared (END sentinel missing) |
| 26.123 | documented | SRC-751 p.337, unchanged from SRC-750 p.337 |
| 26.124 | documented | SRC-752 p.337, the SRC-751 file, carried from 26.123; not run on 26.124 |
SET_MOTION_VELOCITY¶
Phase setup, layout inline. Manual: SRC-741 p.329.
Velocity vector of a February 2026 Euclidean motion, in the MOTION DEFINITION coordinate system. That is a third frame in this chapter: SET_MOTION_GRAVITY reads the reference system and the 6DOF initial conditions read the body frame, so three neighbouring commands take a vector in three different places and none of the argument names says which.
| Argument | Specification |
|---|---|
motion_id |
int |
vx |
float |
vy |
float |
vz |
float |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.292, same grammar as 26.100 |
| 25.100 | documented | SRC-748 p.307, same grammar as 26.100 |
| 26.000 | documented | SRC-747 p.306, same grammar as 26.100 |
| 26.100 | documented | SRC-741 p.329 |