# LVS creates a report but no graph PDF

Check the graph-output switches and Graphviz path separately from the connectivity result.

## Compatibility

Public Windows LVS v1.1.05; published manual matches package

Published guidance with release-applicability limits. Confirm package applicability before following this guide.

**KB-LVS-001 · verified workaround**: Require the current report to explicitly pass connectivity, alongside a normal process exit and fresh outputs. The supplied client rejects the reproduced exit-zero failed comparisons.

## Check the requested outputs

1. Read the LVS report and output directory to establish whether the comparison itself completed.
2. Check SETTINGS/OUTPUT. The manual documents WRITE_DOT_GRAPHS and WRITE_DOT_GRAPHS_PDF as separate switches, both disabled by default.
3. For PDF generation, use an existing compatible Graphviz dot command. On the checked Windows v1.1.05, a full path with spaces failed even when that executable existed; embedded quotes did not recover it. Make its directory available to the LVS child process PATH and configure the simple command name, or use the complete teaching client’s --dot selection.
4. Repeat the example and inspect the newly produced outputs.

## Interpret the result

A missing visualisation is not by itself proof that layout and schematic differ. Conversely, a successfully rendered graph is not a passing connectivity comparison. Keep the comparison report with the visual evidence.

## Distinguish the comparison from rendering failure

The complete version-specific JTL check produced a current LVS PASSED!!! report and four DOT graphs while a full Graphviz path with spaces produced no PDFs. A bare dot command available through the child PATH recovered all four PDFs. The default example disables PDF generation; WRITE_DOT_GRAPHS, WRITE_DOT_GRAPHS_PDF and DELETE_DEBUG_FILES govern different artifacts.

Retain debug files when inspecting DOT output: the teaching settings set DELETE_DEBUG_FILES to false. Require the expected current PDF set after requesting it. A missing/failed renderer can leave the product exit code at 0, and a failed comparison can also return 0. Parse the current comparison report and check requested visualization artifacts separately.

The checked client in the linked first-use guide uses --dot with an existing executable path, child-only PATH discovery and a new results directory. KB-LVS-001/002 track these observed behaviours; Linux rendering and product repairs are not claimed.

## Sources and verification details

Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.

- VAL-057: Public Windows InductEx-LVS v1.1.05 (27 July 2026). Current public Windows LVS v1.1.05 executable and shipped JTL derivative: current pass report, label/connectivity failures, missing-cell rejection, explicit Graphviz failure/recovery and complete standard-library client. Windows/Linux package manuals match the published PDF byte for byte; Linux runtime, maintained source, numerical compact models and final installation are not qualified. Actual browser-downloaded complete five-input LVS JTL ZIP and exact PowerShell 7 article/README command with only executable selections changed; fresh folder with spaces. Separate documented optional Graphviz client route produces four PDFs. Both preserve the same four DOT graph hashes; no numerical compact-model, Linux runtime or final-installation qualification Shipped JTL topology example only. No numerical parameter accuracy, DRC, compact-model extraction, Linux execution, maintained-source authority or final installation qualification.


- published:lvs-manual-1.1.05: Sections 1.4, 6.1.10 and 6.1.11
- validation:lvs-workflow-20261104: VAL-057 current report/DOT/PDF checks and Windows path failure/recovery

- Windows v1.1.05 report/rendering distinction and child-PATH recovery are now checked. Maintained source, other platforms and arbitrary rendering paths remain unqualified.

## Related guides

- [Start an LVS comparison with the correct settings and technology files](/knowledge-base/lvs-first-settings)
- [The command runs an older installation than expected](/knowledge-base/tool-command-wrong-version)