Skip to main content
VLSI Korea

Semiconductor graph

KLayout
Methods ↗

6 entities and 9 documented connections shown.

Connections

6 entities · 9 claims
100%

Drag the map or use pan buttons to move. Tab to a node or connection and press Enter to inspect its evidence. Arrows follow the actual claim direction.

STARTING ENTITYDIRECT CONNECTIONSSECOND STEPUses tool · SUPPORTEDUses toolDepends on · SUPPORTEDDepends onUses tool · SUPPORTEDUses toolUses PDK · SUPPORTEDUses PDKUses tool · SUPPORTEDUses toolDepends on · SUPPORTEDDepends onUses tool · SUPPORTEDUses toolDepends on · SUPPORTEDDepends onUses tool · SUPPORTEDUses toolOpenLane 2 · open source projectOPEN SOURCE PROJECTOpenLane 2Yosys · eda toolEDA TOOLYosysSKY130 Open PDK · pdkPDKSKY130 Open PDKKLayout · eda toolEDA TOOLSTARTKLayoutOpenROAD · eda toolEDA TOOLOpenROADOpenROAD Flow Scripts · open source projectOPEN SOURCE PROJECTOpenROAD FlowScripts
CompanyChip / productTechnologyPlace / facility
Select a connection for its evidence
Relationships & evidence (9)
Every displayed connection is a scoped claim. Arrows follow subject to object.
SubjectRelationshipObjectStatusEvidence
OpenROAD Flow ScriptsKLayoutSUPPORTEDValidity dates not established
Why are these connected?

KLayout is documented for the finishing stage. This is not a verified signoff result.

OpenROAD Flow Scripts README

The OpenROAD Project · Tier A · Primary source · supports

The ORFS flow diagram assigns GDSII generation and DRC/LVS checks to KLayout.

Location: Pinned README.md line 43: GDSII generation and layout checks

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
OpenLane 2YosysSUPPORTEDValidity dates not established
Why are these connected?

OpenLane describes Yosys among its infrastructure components.

openlane2 pinned upstream documentation

Official openlane2 repository · Tier A · Primary source · supports

OpenLane describes Yosys among its infrastructure components.

Location: Readme / ASIC infrastructure components

Published
Not stated
Retrieved
2026-10-13

Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.

Full claim history →
OpenROAD Flow ScriptsYosysSUPPORTEDValidity dates not established
Why are these connected?

The OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow.

openroad pinned upstream documentation

Official openroad repository · Tier A · Primary source · supports

The OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow.

Location: README / RTL-GDSII Using OpenROAD-flow-scripts

Published
Not stated
Retrieved
2026-10-13

Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.

Full claim history →
OpenROAD Flow ScriptsSKY130 Open PDKSUPPORTEDValidity dates not established
Why are these connected?

The README names SKY130 among open PDKs supported in OpenROAD-flow-scripts; a selected platform and library configuration is required.

openroad pinned upstream documentation

Official openroad repository · Tier A · Primary source · supports

The README names SKY130 among open PDKs supported in OpenROAD-flow-scripts; a selected platform and library configuration is required.

Location: README / PDK Support

Published
Not stated
Retrieved
2026-10-13

Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.

Full claim history →
OpenROAD Flow ScriptsOpenROADSUPPORTEDValidity dates not established
Why are these connected?

ORFS documents OpenROAD use. Its README restricts guarantees to the latest matching OpenROAD/ORFS and warns that third-party versions are not guaranteed.

OpenROAD Flow Scripts README

The OpenROAD Project · Tier A · Primary source · supports

The ORFS installation documentation identifies OpenROAD among its provided flow applications.

Location: Pinned README.md line 89: Physical implementation flow

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
OpenLane 2OpenROADSUPPORTEDValidity dates not established
Why are these connected?

OpenLane describes OpenROAD among its infrastructure components.

openlane2 pinned upstream documentation

Official openlane2 repository · Tier A · Primary source · supports

OpenLane describes OpenROAD among its infrastructure components.

Location: Readme / ASIC infrastructure components

Published
Not stated
Retrieved
2026-10-13

Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.

Full claim history →
OpenROAD Flow ScriptsKLayoutSUPPORTEDValidity dates not established
Why are these connected?

The described ORFS finishing stage uses KLayout for GDSII output and DRC/LVS checks.

openroad pinned upstream documentation

Official openroad repository · Tier A · Primary source · supports

The described ORFS finishing stage uses KLayout for GDSII output and DRC/LVS checks.

Location: README / ORFS Finishing

Published
Not stated
Retrieved
2026-10-13

Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.

Full claim history →
OpenLane 2KLayoutSUPPORTEDValidity dates not established
Why are these connected?

OpenLane describes KLayout among its infrastructure components.

openlane2 pinned upstream documentation

Official openlane2 repository · Tier A · Primary source · supports

OpenLane describes KLayout among its infrastructure components.

Location: Readme / ASIC infrastructure components

Published
Not stated
Retrieved
2026-10-13

Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.

Full claim history →
OpenROAD Flow ScriptsYosysSUPPORTEDValidity dates not established
Why are these connected?

Yosys is documented for the synthesis stage of OpenROAD Flow Scripts at this source revision.

OpenROAD Flow Scripts README

The OpenROAD Project · Tier A · Primary source · supports

The ORFS flow diagram assigns logic synthesis to Yosys.

Location: Pinned README.md line 19: RTL synthesis

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
Find an evidence path

Find a documented path

From KLayout · up to two relationship steps.

A path retains its original claims. Shared technology does not establish a supply contract.

6 nodes · 9 claims
Scope

Relationships may describe different dates. A path does not establish simultaneous activity. Bounded source-backed collection. Missing or filtered connections do not establish absence. Supported does not mean independently verified.