Health Visualizer

Understand why a model is heavy and which families are responsible for the most elements. Health Visualizer provides a structured visual analysis of model element composition using a two-tier scanning architecture. Where ReViewer gives a high-level dashboard, Health Visualizer lets you drill into the internal structure of the element hierarchy -- down to individual family types and their geometry characteristics. It is the right tool when you need to understand why a model is heavy, which families are responsible for the most elements, or which types have geometry issues.

flowchart TD
    M["Model"] --> QS["QuickScan\n~500ms"]
    M --> DS["DeepScan\n~10-60s"]
 
    QS --> Cat["Category\ne.g. Walls"]
    Cat --> Fam["Family\ne.g. Basic Wall"]
    Fam --> Typ["Type\ne.g. Generic - 8in"]
    Typ --> Count["Element Count"]
 
    DS --> Geo["+ Geometry Analysis"]
    Geo --> Faces["Face Count"]
    Geo --> Verts["Vertex Count"]
    Geo --> Issues["Geometry Issues"]
 
    style QS fill:#3b82f6,color:#fff,stroke:#2563eb
    style DS fill:#8b5cf6,color:#fff,stroke:#7c3aed
    style Issues fill:#ef4444,color:#fff,stroke:#dc2626

Two-Tier Scanning

Health Visualizer uses two scan modes with different depth/speed trade-offs:

QuickScan (~500ms) builds a three-level hierarchy:

1. Category (for example, Walls, Doors, Structural Framing)
2. Family (for example, Basic Wall, Single-Flush Door, W-Shape)
3. Type (for example, Generic - 8", 36" x 84", W12x26)

QuickScan collects element counts at each level and renders them immediately. Use QuickScan to get a rapid overview of element distribution without waiting for a full geometry analysis.

DeepScan extends QuickScan with per-element geometry metrics and issue detection. DeepScan detects 40+ issue types, including:

• Elements with null or degenerate geometry
• Elements placed outside the project extents
• Elements with missing or invalid host references
• Elements with parameter values that conflict with their type definition
• Families with excessive polygon counts relative to their category peers
• Types with unused or redundant parameters

DeepScan takes longer to complete depending on model size and element count. A progress bar displays the scan status by category.

Visualization

Results render in a D3.js interactive chart embedded in a WebView2 panel. The default view is a sunburst chart showing the full Category > Family > Type hierarchy. Click any segment to zoom into that subtree. A breadcrumb trail above the chart shows your current position in the hierarchy and provides one-click navigation back to any ancestor level.

At more than 2,000 elements in the current view, the tool automatically switches to a treemap layout. Treemaps scale better at high element counts because they avoid the visual crowding that affects sunbursts with many thin outer segments. You can manually switch between chart types using the toolbar regardless of element count.

Reading the Chart

Chart segments are sized proportionally to element count. Color indicates health status when DeepScan results are available:

• Blue/neutral: No issues detected
• Yellow: One or more medium-severity issues detected in this subtree
• Orange: One or more high-severity issues detected
• Red: One or more critical issues detected

Hover over any segment to see a tooltip with the exact element count, issue count, and the most severe issue type present.

Drill-Down Navigation

Click any segment in the sunburst or any cell in the treemap to navigate into that node. The chart re-renders to fill the panel with the selected subtree, making it easier to analyze a specific category or family in detail. Use the breadcrumb trail to navigate back up the hierarchy. The breadcrumb also shows the element count at each ancestor level so you maintain orientation as you drill in.

Typical Workflow

1. Open Health Visualizer and run QuickScan to get an immediate overview.
2. Identify categories or families with unexpectedly high element counts.
3. Click into those nodes to see the Family > Type breakdown.
4. Run DeepScan to add geometry issue detection.
5. Review red and orange segments; use the element IDs from the detail panel to locate problem elements in the model.
6. Address issues using the appropriate tool (for example, use Type Swap to consolidate redundant types, or Wipe Hub to remove unused families).

Last updated: 2026-02-19