Analyze Workflow

Core loop

The Analyze page follows a repeatable loop:

1. choose lot and snapshot
2. find a suspicious test
3. inspect it in linked views
4. isolate a population by brushing or filtering
5. save or share the conclusion

Context that propagates

Most of the page shares a common context:

• selected lot
• selected snapshot
• current test
• wafer scope when applicable
• active die selection
• active scenario limits

Most analysis work depends on that shared context.

Analyze to SQL

The current analysis scope can flow into the SQL editor.

That lets you keep working from:

• the same lot
• the same brushed die subset
• the same notebook what-if limits

without rebuilding the population by hand in SQL.

Use the SQL editor when you want a custom table or grouped calculation for the same scoped population.

Cards vs. modals

• cards are for quick inspection and lightweight iteration
• modals are for higher-resolution inspection and the full interaction model

If a card is useful but too small for the task, open the modal.

Selection model

Brushing is shared state across the analysis surfaces.

• Shift + drag adds to the current selection
• Alt + Shift + drag replaces the current selection

Use selection when you want to compare a subset to the lot overall.

Saving

Save when the notebook captures:

• a meaningful test focus
• a useful selection or wafer focus
• what-if limits worth reviewing with someone else

Notebook history is easier to use when versions correspond to conclusions or review checkpoints.