- summary set-stop-phase command documentation
Controls the phase where agents stop when running by decision.
Options `-A` and `-B` are optional and mutually exclusive. If not specified, the default is `-B`.
Only one of `-a`, `-d`, `-i`, `-o`, `-p` must be selected.
With no options, reports the current stop phase.
|| `-A, --after` || Stop after specified phase. || || `-B, --before` || Stop before specified phase (the default). || || `-a, --apply` || Select the apply phase. || || `-d, --decision` || Select the decision phase. || || `-i, --input` || Select the input phase. || || `-o, --output` || Select the output phase. || || `-p, --proposal` || Select the proposal phase. ||
When running by decision cycle it can be helpful to have agents stop at a particular point in its execution cycle. This command allows the user to control which phase Soar stops in. The precise definition is that "running for _n_ decisions and stopping before phase _ph_ means to run until the decision cycle counter has increased by _n_ and then stop when the next phase is _ph_". The phase sequence (as of this writing) is: input, proposal, decision, apply, output. Stopping after one phase is exactly equivalent to stopping before the next phase.
On initialization Soar defaults to stopping before the input phase (or after the output phase, however you like to think of it).
Setting the stop phase applies to all agents.