Mingcedar

Product: Mingcedar Scan SCAN

Scan and review the result table | Mingcedar Scan

Verify the project name and full path, then check symbolic and absolute addresses, types, scan periods, and counts against the selected scope.

Published Updated

<div class="manual-doc-article manual-doc-article-section"><h2 id="scan">Step 4: Scan and review the result table</h2>

Confirm the result project before reviewing fields, counts, and filter state.

<div class="doc-card-list">

<article class="doc-card">

<h3 id="scan-item-1">Result review items</h3>

<p>Verify the project name and full path, then check symbolic and absolute addresses, types, scan periods, and counts against the selected scope.</p>

</article>

<article class="doc-card">

<h3 id="scan-item-2">Review addresses and verification status together</h3>

<p>Review symbolic paths and absolute addresses alongside <code>addressState</code>, <code>addressSource</code>, and <code>addressConfidence</code>. <code>absolute_unverified</code> rows are review-only and excluded from communication imports; address text alone does not prove collection eligibility.</p>

</article>

<article class="doc-card">

<h3 id="scan-item-3">Absolute addresses depend on project metadata</h3>

<p>A standard-DB member must have a constructed absolute address to enter the result. Derived layouts, unverified offset semantics, unsupported communication types, or normalized-code conflicts can leave a row unverified. Optimized or unknown layouts and members without an address are skipped rather than exported as symbolic-only rows.</p>

</article>

<article class="doc-card">

<h3 id="scan-item-4">Data types use a reusable scalar vocabulary</h3>

<p>Review lists support scalar Boolean, integer, floating-point, string, and date/time types. Structures and arrays export supported scalar children only. Communication imports support fewer types; see Export Rules.</p>

</article>

<article class="doc-card">

<h3 id="scan-item-5">Use table operations</h3>

<p>Use selection, filtering, deletion of selected rows, clear selection, restore all, and selected-only view to narrow the target result.</p>

</article>

<article class="doc-card doc-card-warn">

<h3 id="scan-item-6">Do not export too early</h3>

<p>If the table contains content outside the intended delivery scope, adjust scope or rules before exporting.</p>

</article>

<article class="doc-card">

<h3 id="scan-item-7">Project-source consistency check</h3>

<p>Filtering and export compare the result and current project paths. A mismatch stops the operation and clears results; rescan to continue.</p>

</article>

<article class="doc-card">

<h3 id="scan-item-8">Display when search has no matches</h3>

<p>An unmatched search shows a no-match message and total result count. Clear or change the search to view the existing results.</p>

</article>

</div>

<div class="docs-note-grid manual-doc-image-grid">

<figure class="docs-note-card manual-doc-image-card" id="scan-image-1">

<img src="/WEB_img/HQScan/main.png" alt="Mingcedar Scan workspace and point preview" loading="lazy" decoding="async" />

<figcaption>

<strong>Figure 1: Scan workspace and point preview</strong>

<p>The workspace combines project selection, DB scan scope, environment state, and point preview. Review addresses, types, and counts after scanning.</p>

</figcaption>

</figure>

</div>

</div>