deploy.

App/wwwroot/HiAPI-docsite/manual/run/the-other-commands.html

@@ -152,7 +152,7 @@ add and nothing to look for.</p>
 <p><strong>NC Optimization Config</strong> is the Optimization category's one command, and it exists so the
 optimizer's settings sit at a point in the run rather than over all of it. Everything played below
 it optimizes under those values, and a second one further down re-points them mid-mission.</p>
-<p>Its own node carries four switches — <strong>Enable Optimization</strong>, <strong>Enable Feedrate Optimization</strong>,
+<p>Its own node carries five switches. The fifth, <strong>Omit Leading Zero in Output (.348, not 0.348)</strong>, only formats the numbers written out; the other four steer the optimizer — <strong>Enable Optimization</strong>, <strong>Enable Feedrate Optimization</strong>,
 <strong>Enable Depth Splition</strong> and <strong>Enable Interpolation</strong> — and the values live on five child nodes
 beneath it:</p>
 <table>
@@ -191,10 +191,11 @@ optimizer is on, which is the first switch on its panel.</p>
 <p>The command takes no title: its row always reads <strong>NC Optimization Config</strong>. What each quantity
 means, and why an optimized result can look wrong, is
 <a href="../../technique/nc-optimization/index.html">NC Optimization</a>.</p>
-<p>The demo mission's optimizer command, at <code>/execution?tree=execution/mission/1</code>, sitting above the
-two program groups it governs. The four switches are on the command's own panel; the five value
-nodes are indented under it in the tree.</p>
-<p><img src="the-other-commands-img/nc-optimization-config.en.png" alt="The NC Optimization Config command selected in the Mission branch, with Distances, Feedrate, Motion Dynamics, Force and Safety and Compensation child nodes listed beneath it, and the panel below showing the Enable Optimization, Enable Feedrate Optimization, Enable Depth Splition and Enable Interpolation checkboxes"></p>
+<p>The demo mission's optimizer command, at <code>/execution?tree=execution/mission/7</code>. In this mission it
+sits below both program groups rather than above them, so the ordering rule at the top of this
+section is what decides how much of the run it reaches. The five switches are on the command's own
+panel; the five value nodes are indented under it in the tree.</p>
+<p><img src="the-other-commands-img/nc-optimization-config.en.png" alt="The NC Optimization Config command selected in the Mission branch, with Distances, Feedrate, Motion Dynamics, Force and Safety and Compensation child nodes listed beneath it, and the panel below showing the Enable Optimization, Enable Feedrate Optimization, Enable Depth Splition and Enable Interpolation checkboxes ticked above an unticked Omit Leading Zero in Output checkbox"></p>
 <h2 id="writing-out-what-the-run-produced">Writing out what the run produced</h2>
 <p>The <strong>Output</strong> category holds three commands: <strong>Post-Execution</strong>, <strong>Record Meshed Geometry</strong> and
 <strong>Export Meshed Geometry (STL)</strong>.</p>
@@ -257,7 +258,7 @@ not what can be prepared. The outputs are written in an order of the command's o
 step files, optimization, the writeback, then the geometry difference — which is not the order the
 tree lists them in, and which matters only if you are reading their timestamps.</p>
 <p>The demo mission's Post-Execution command with <strong>Step Files Output</strong> selected, at
-<code>/execution?tree=execution/mission/5/step-files</code>. Each output is a child node with its own
+<code>/execution?tree=execution/mission/8/step-files</code>. Each output is a child node with its own
 checkbox — that tick is what switches the output on — and the template field for the selected one
 sits in the panel below.</p>
 <p><img src="the-other-commands-img/post-execution.en.png" alt="The Post-Execution command in the Mission branch with its five child nodes, each carrying its own checkbox, and the Step File Template field in the panel below"></p>