0.975Highest triage priorityUNKNOWNInspect metric contract
LVS / short / highWorst caseUNKNOWNInspect metric contract
18 casesSweep rowsUNKNOWNInspect metric contract
SIMULATION / SA-EDA-PV-001-DRC-LVS-TRIAGE-001
Physical verification DRC/LVS error triage
PV Triage
Replay DRC and LVS issue classes as evidence cards with report confidence, triage priority, likely root cause, and safe next check.
EXPLORE
Start with the observable.
Use this page when the simulation is the primary artifact. The linked lesson explains the concept; the linked lab keeps the visual replay surface available.
- Separate DRC geometry evidence from LVS connectivity evidence.
- Read report confidence, triage priority, and fix risk before editing a layout.
- Use safe next checks as vocabulary, not as signoff instructions.
RUN CARD
Conditions before conclusions.
This page replays saved physical-verification triage rows and does not run Magic, Netgen, rule decks, repository code, or signoff workflows.
Primary knobs
- Issue family
- Issue class
- Severity
Saved outputs
- Report confidence
- Triage priority
- Fix-risk proxy
- Likely root cause
- Safe next check
EXPORT
Download the public artifacts.
These exports are the supported public files for review. PDK files and restricted third-party material are not redistributed.
Dataset JSON
/data/physical-verification-drc-lvs-error-triage-web-v1.json
Open file ->Dataset CSV
/data/physical-verification-drc-lvs-error-triage-v65.csv
Open file ->v65 daily signal summary CSV
/data/v65-daily-signal-summary.csv
Open file ->v65 daily signal model script
/data/v65_daily_signal_sims.mjs
Open file ->v65 daily signal model card
/data/v65-daily-signal-model-card.md
Open file ->METHODS
How the number was made.
Methods are written for citation discipline: the extraction rule matters as much as the plotted value.
Issue families are grouped into DRC geometry markers and LVS connectivity/topology mismatches.
Keep this method attached when reusing the figure or metric.
Triage priority combines issue-class base risk with severity level.
Keep this method attached when reusing the figure or metric.
Safe next checks are evidence-literacy prompts and deliberately avoid tool commands or PDK details.
Keep this method attached when reusing the figure or metric.
LIMITS
What this page does not claim.
The MVP is useful because the limits are visible. These statements prevent a teaching simulation from being cited as silicon evidence.
No PDK rules, GDS, netlists, repository code, extracted parasitics, or signoff reports are redistributed.
Carry this boundary into any derivative note, paper draft, or slide.
No equivalence to foundry signoff, physical-design closure, or tapeout readiness is claimed.
Carry this boundary into any derivative note, paper draft, or slide.
Real work requires rights-clean PDK setup, tool logs, versioned decks, layout ownership, and review by the design/process owner.
Carry this boundary into any derivative note, paper draft, or slide.
EVIDENCE
Trace the claim back to artifacts.
The evidence route remains the catalog-level browser; this page is the simulation-level reading card.
The dataset preserves each issue family, class, severity, and safe next-check row.
SA-EDA-PV-001-DRC-LVS-TRIAGE-001
CSV export supports a paper-methods note on what DRC and LVS can and cannot prove.
SA-EDA-PV-001-DRC-LVS-TRIAGE-001
The EDA domain page now has a simulation object instead of borrowing an SRAM card.
SA-EDA-PV-001-DRC-LVS-TRIAGE-001
Source spine
These links anchor the public teaching model. They do not convert the replay into a qualified process recipe or signoff result.
Public execution boundary
No server-side live ngspice execution, uploads, accounts, payments, comments, newsletter signup, or job/event submissions are active on this page.