Mission

Mission is a branch of the Execution page's Control Tree, reached as /execution?tree=execution/mission. It holds the command list a run executes: the project's own command is always a list, and nested lists read as sub-trees, so the branch is the mission and the mission is a tree of commands.

Each command type has its own editor panel. The pages below document one type each; the root panel documents the list itself — adding, ordering and removing what the run will play.

Ordered by where a command falls in a run: the branch root and its container first, then what is set up before the run, what the run plays, and what happens after it.

Pages

• Mission Root Panel — The branch root: the command list, and how a mission is assembled
• List Command Panel — The container command; a nested one becomes a sub-tree of the mission
• PreSetting Command Panel — What is applied to the machine state before the run reaches a program
• NC Optimization Option Panel — The optimizer's options as a command in the list, so a run can change them mid-mission
• NcFile Command Panel — Playing a program file from disk
• NcCode Command Panel — Playing NC text held in the project rather than in a file
• Script Command Panel — Driving the session from C# script rather than from NC
• PostExecution Command Panel — What runs once the program above it has finished

The pages above do not cover every command kind a mission can hold. Three more ship an editor of their own — Machining Motion Resolution, Record Meshed Geom and Export Meshed Geom — and the rest fall back to a generic field editor built from the scalars the command declares, so a kind becomes addable and editable before anyone writes a panel for it. The set on offer is whatever the server's command catalog returns, which is why this folder cannot be a closed list.

See Also

• Execution Page — the run cockpit this branch belongs to