HiNC-2025-win-desktop-Deploy/App/wwwroot/HiAPI-docsite/manual/run/watching-the-run.html

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
      <title>Watching the Run | HiAPI-C# 2025 </title>
      <meta name="viewport" content="width=device-width, initial-scale=1.0">
      <meta name="title" content="Watching the Run | HiAPI-C# 2025 ">
      
      
      <link rel="icon" href="../../img/HiAPI.favicon.ico">
      <link rel="stylesheet" href="../../public/docfx.min.css">
      <link rel="stylesheet" href="../../public/main.css">
      <meta name="docfx:navrel" content="../../toc.html">
      <meta name="docfx:tocrel" content="toc.html">
      
      <meta name="docfx:rel" content="../../">
      
      
      
      <meta name="loc:inThisArticle" content="In this article">
      <meta name="loc:searchResultsCount" content="{count} results for &quot;{query}&quot;">
      <meta name="loc:searchNoResults" content="No results for &quot;{query}&quot;">
      <meta name="loc:tocFilter" content="Filter by title">
      <meta name="loc:nextArticle" content="Next">
      <meta name="loc:prevArticle" content="Previous">
      <meta name="loc:themeLight" content="Light">
      <meta name="loc:themeDark" content="Dark">
      <meta name="loc:themeAuto" content="Auto">
      <meta name="loc:changeTheme" content="Change theme">
      <meta name="loc:copy" content="Copy">
      <meta name="loc:downloadPdf" content="Download PDF">

      <script type="module" src="./../../public/docfx.min.js"></script>

      <script>
        const theme = localStorage.getItem('theme') || 'auto'
        document.documentElement.setAttribute('data-bs-theme', theme === 'auto' ? (window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light') : theme)
      </script>

  </head>

  <body class="tex2jax_ignore" data-layout="" data-yaml-mime="">
    <header class="bg-body border-bottom">
      <nav id="autocollapse" class="navbar navbar-expand-md" role="navigation">
        <div class="container-xxl flex-nowrap">
          <a class="navbar-brand" href="../../index.html">
            <img id="logo" class="svg" src="../../img/HiAPI.logo.png" alt="">
            
          </a>
          <button class="btn btn-lg d-md-none border-0" type="button" data-bs-toggle="collapse" data-bs-target="#navpanel" aria-controls="navpanel" aria-expanded="false" aria-label="Toggle navigation">
            <i class="bi bi-three-dots"></i>
          </button>
          <div class="collapse navbar-collapse" id="navpanel">
            <div id="navbar">
              <form class="search" role="search" id="search">
                <i class="bi bi-search"></i>
                <input class="form-control" id="search-query" type="search" disabled placeholder="Search" autocomplete="off" aria-label="Search">
              </form>
            </div>
          </div>
        </div>
      </nav>
    </header>

    <main class="container-xxl">
      <div class="toc-offcanvas">
        <div class="offcanvas-md offcanvas-start" tabindex="-1" id="tocOffcanvas" aria-labelledby="tocOffcanvasLabel">
          <div class="offcanvas-header">
            <h5 class="offcanvas-title" id="tocOffcanvasLabel">Table of Contents</h5>
            <button type="button" class="btn-close" data-bs-dismiss="offcanvas" data-bs-target="#tocOffcanvas" aria-label="Close"></button>
          </div>
          <div class="offcanvas-body">
            <nav class="toc" id="toc"></nav>
          </div>
        </div>
      </div>

      <div class="content">
        <div class="actionbar">
          <button class="btn btn-lg border-0 d-md-none" type="button" data-bs-toggle="offcanvas" data-bs-target="#tocOffcanvas" aria-controls="tocOffcanvas" aria-expanded="false" aria-label="Show table of contents">
            <i class="bi bi-list"></i>
          </button>

          <nav id="breadcrumb"></nav>
        </div>

        <article data-uid="">
          <h1 id="watching-the-run">Watching the Run</h1>

<p>A run shows itself two ways at once, and they answer different questions. The canvas shows what is
happening now. The strip charts show the <strong>whole mission</strong> as one picture, so they are where you find
out <em>where</em> the interesting part is. Use the charts to choose a moment; use the canvas and the Step
Info column to look at it.</p>
<h2 id="where-it-is">Where it is</h2>
<p>The Execution page at <code>/execution</code>, in the two middle columns: the 3D canvas with the Session
Messages panel beneath it, and the <strong>Strip Charts</strong> column beside it. Both columns are switched on
and off from the quick-toggles on the menu bar, and every panel inside them folds to its own header.</p>
<h2 id="the-canvas">The canvas</h2>
<p><strong>What the canvas draws is a choice, not a fixed set.</strong> It opens showing the workpiece, the fixture,
the dimension bar and the tool path. The machine and the tool are <em>not</em> drawn until you ask for
them — which is usually what you want, because a five-axis machine at home position fills the frame
and hides the cut you came to watch.</p>
<p>The panel header carries the generic camera control — a <strong>View</strong> menu of seven presets: Isometric,
Front, Back, Right, Left, Top and Bottom — and beside it the four that belong to a run:</p>
<table>
<thead>
<tr>
<th>Control</th>
<th>What it does</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Tool Path</strong></td>
<td>Shows or hides the tool path through the whole program</td>
</tr>
<tr>
<td><strong>Path Points</strong></td>
<td>Adds the per-position dot markers along it. Editable only while Tool Path is on</td>
</tr>
<tr>
<td><strong>Scene ▾</strong></td>
<td>Which elements are drawn, in three groups</td>
</tr>
<tr>
<td><strong>Meshed Geom ▾</strong></td>
<td>The workpiece's rendering-cache budget, and the ideal-versus-actual difference display</td>
</tr>
</tbody>
</table>
<p>The <strong>Scene</strong> menu groups its checkboxes the way the renderer groups them: <strong>Solid</strong> — Machine, Tool,
Workpiece, Fixture; <strong>Coordinate</strong> — Program Zero, ISO Coordinate, and Heidenhain Coordinate on a
Heidenhain project only; <strong>Display Aids</strong> — Dimension Bar, Color Scale Bar. The tool path is
deliberately not in this menu: its own button owns it, and Path Points hangs off that.</p>
<p>Under <strong>Meshed Geom</strong> sit two rows, each opening a panel of its own: <em>Graphic Cache</em>, the memory
budget for the workpiece's rendering cache, and <em>Diff Visual Radius</em>, which displays the difference
between the ideal geometry and the actual one. The second carries a badge reading <strong>None</strong> or
<strong>Diff</strong>, so the menu answers &ldquo;did this run leave a difference?&rdquo; without your opening the row.</p>
<p>Collapsing the canvas does not disconnect it. The panel keeps it mounted and simply stops it drawing,
so re-expanding is instant rather than a fresh connection.</p>
<p>The <strong>Scene</strong> menu open over the canvas at <code>/execution</code>, with the Strip Charts column beside it. The
three groups are the ones listed above, and the ticked boxes are the set the page opens with —
Workpiece, Fixture and Dimension Bar — with Machine and Tool unticked.</p>
<p><img src="watching-the-run-img/scene-menu.en.png" alt="The Execution page with the Scene dropdown open over the 3D canvas, showing Solid with Machine, Tool, Workpiece and Fixture, Coordinate with Program Zero and ISO Coordinate, and Display Aids with Dimension Bar and Color Scale Bar; Workpiece, Fixture and Dimension Bar are ticked, and the Strip Charts column stands to the right"></p>
<h2 id="the-three-strip-charts">The three strip charts</h2>
<p>One group bar drives three charts, and each of them plots <strong>the whole mission rather than the current
moment</strong>:</p>
<table>
<thead>
<tr>
<th>Chart</th>
<th>What it plots</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Availability Chart</strong></td>
<td>Five ratios: yielding stress, max spindle torque, max spindle power, spindle working temperature, thermal yield</td>
</tr>
<tr>
<td><strong>Surface Roughness Chart</strong></td>
<td>Re-cut depth, program-side cusp, and tip deflection in X / Y / Z, in µm</td>
</tr>
<tr>
<td><strong>Color Index Time Chart</strong></td>
<td>One property you pick, from every step property the run can quantify</td>
</tr>
</tbody>
</table>
<p>Each series is drawn as a <strong>band between its minimum and its maximum</strong>, not as a line through
samples: the window is downsampled to the width it has on screen, so what you are reading is the
shape of the run — where the spindle is loaded, where surface quality degrades, where thermal limits
are approached — rather than individual values. The values themselves are in the legend panel down
the side of each chart, which follows the cursor and can be dragged wider.</p>
<p>All three carry a <strong>Y-axis range</strong> editor in their header — <em>Fit</em> to the data, <em>Lock</em> to a minimum
and maximum you type, or <em>Symmetric</em> about zero with a bound; locking one is how you compare two
parts of a run without the axis moving under you. The
Color Index chart adds two more: the property picker, which is a type-to-filter list of every
quantifiable step property, and <strong>Colors</strong>, which edits the colour guide. Colors is worth
understanding before you touch it: it drives the <strong>colour of the workpiece in the 3D scene</strong> and the
colour scale bar, not the line in the chart.</p>
<h3 id="the-group-bar">The group bar</h3>
<table>
<thead>
<tr>
<th>Control</th>
<th>What it does</th>
</tr>
</thead>
<tbody>
<tr>
<td>Range chip</td>
<td>The slice of the mission currently shown, against its total step count</td>
</tr>
<tr>
<td>Cursor readout</td>
<td>The x-value under the pointer, shared by all three charts</td>
</tr>
<tr>
<td><strong>X-axis mode</strong></td>
<td><em>Time (s)</em> or <em>Step index</em>, applied to all three at once</td>
</tr>
<tr>
<td><strong>Fit view</strong></td>
<td>Fits the 3D canvas to the tool path — the one control here that acts on the canvas</td>
</tr>
<tr>
<td><strong>Stick to live end</strong></td>
<td>Keeps the window's right edge pinned to the running end of the mission</td>
</tr>
<tr>
<td><strong>Reset display range</strong></td>
<td>Back to the whole mission, and re-arms stick-to-end</td>
</tr>
<tr>
<td><strong>Reload</strong></td>
<td>Re-fetches all three charts</td>
</tr>
</tbody>
</table>
<p>Stick-to-end turns itself <strong>off</strong> the moment you pan or zoom, because both of those set a definite
right edge. That is the behaviour you want while a run is going — you can look at something without
being dragged back to the live end — and <em>Reset display range</em> is how you re-arm it.</p>
<h2 id="reading-a-chart-with-the-pointer">Reading a chart with the pointer</h2>
<p>The three charts share one window and one selection, so a gesture on any of them moves all three.</p>
<table>
<thead>
<tr>
<th>Gesture</th>
<th>What it does</th>
</tr>
</thead>
<tbody>
<tr>
<td>Click</td>
<td>Selects that step — this is what fills the Step Info column</td>
</tr>
<tr>
<td>Drag left or right</td>
<td>Sweeps a range and zooms to it on release</td>
</tr>
<tr>
<td>Right-drag or middle-drag</td>
<td>Pans</td>
</tr>
<tr>
<td>Wheel</td>
<td>Zooms about the pointer</td>
</tr>
<tr>
<td>Hover</td>
<td>Puts that x-value in the group bar's cursor readout</td>
</tr>
<tr>
<td>One finger / two fingers</td>
<td>Pans / pinch-zooms, on a touch screen</td>
</tr>
</tbody>
</table>
<p>A left drag shorter than a few pixels counts as a click, so selecting a step does not need a steady
hand.</p>
<p>Before anything has run, all three read <strong>No mission data</strong>. A chart that has data but no physics
behind it reads <strong>No physics data</strong> instead — that is what the Availability chart looks like when
the run produced no physics results.</p>
<p>The three charts with the demo mission paused part way through and a step selected. The vertical rule
crossing all three at the same place is that selection; the range chip on the group bar names the
window, the x-axis is in seconds, and each chart's legend stands down its right side with one entry
per series — five on each of the first two, one on the Color Index chart, which plots the single
property named in its header.</p>
<p><img src="watching-the-run-img/strip-charts.en.png" alt="The Execution page's Strip Charts column filled from a paused run: an Availability Chart, a Surface Roughness Chart and a Color Index Time Chart stacked under one group bar, each showing banded series across the mission timeline with a legend listing its series down the right side, and the 3D canvas showing the part-machined block to the left"></p>
<h2 id="see-also">See Also</h2>
<ul>
<li><a href="index.html">Running a Simulation</a> — the rest of running a job</li>
<li><a href="running-a-simulation.html">Starting and Stepping</a> — the transport that makes these fill</li>
<li><a href="inspecting-a-step.html">Inspecting a Step</a> — the per-step detail a click on these charts opens</li>
<li><a href="../basics/the-app-window.html">The Application Window</a> — the column quick-toggles that show and hide these two columns</li>
<li><a class="xref" href="../../anatomy/execution/strip-charts.html">Strip Charts</a> — the components behind this column: the shared window, the pointer contract and the data behind each series</li>
<li><a class="xref" href="../../anatomy/execution/execution-extended-renderingcanvas-tool-bar.html">Execution Extended RenderingCanvas Tool Bar</a> — the component behind the canvas header's run controls</li>
</ul>

</article>

        <div class="contribution d-print-none">
        </div>

        <div class="next-article d-print-none border-top" id="nextArticle"></div>

      </div>

      <div class="affix">
        <nav id="affix"></nav>
      </div>
    </main>

    <div class="container-xxl search-results" id="search-results"></div>

    <footer class="border-top text-secondary">
      <div class="container-xxl">
        <div class="flex-fill">
          <span> Copyright © 2025 <a href='https://superhightech.com.tw'>Tech Coordinate</a>. All rights reserved. <a href='https://superhightech.com.tw'>超級高科技股份有限公司</a> © 2025 版權所有 </span>
        </div>
      </div>
    </footer>
  </body>
</html>