Ctrl+K

piel.integration.gdsfactory_openlane

piel.integration.gdsfactory_openlane#

There are a number of ways to generate gdsfactory integration.

It is worth noting that GDSFactory has already the following PDKs installed: * SKY130nm https://gdsfactory.github.io/skywater130/ * GF180nm https://gdsfactory.github.io/gf180/

Module Contents#

Functions#

create_gdsfactory_component_from_openlane(...)

This function cretes a gdsfactory layout component that can be included in the network codesign of the device, or that can be used for interconnection codesign.
create_gdsfactory_component_from_openlane(design_name_v1: str | None = None, design_directory: piel.types.piel_path_types | None = None, run_name: str | None = None, v1: bool = True) → gdsfactory.Component[source]#

This function cretes a gdsfactory layout component that can be included in the network codesign of the device, or that can be used for interconnection codesign.

It will look into the latest design run and extract the final OpenLane-generated GDS. You do not have to have run this with OpenLane2 as it just looks at the latest run.

Parameters:

  • design_name_v1 (str) – Design name of the v1 design that can be found within $OPENLANE_ROOT/”<latest>”/designs.

  • design_directory (piel_path_types) – Design directory PATH.

  • run_name (str) – Name of the run to extract the GDS from. If None, it will look at the latest run.

  • v1 (bool) – If True, it will import the design from the OpenLane v1 configuration.

Returns:

GDSFactory component.

Return type:

component(gf.Component)

Contents