software

Define the software versions to use with this PDK.
This information is used in the design manual creation but can be embedded in the software specific design kit also

Structure

The attributes and elements are shown below, in a sorted per type fashion.
In case a list is printed after an element, it indicates that you can have many, otherwise it should be a single element. With a optional it tells the element is not required.

XSD

The schema file can be downloaded or viewed at Epiphany.

Details

feature

Type feature documentation: Define the features that are availble for use with this PDK in the given software.
This information is used in the design manual creation but can be embedded in the software specific design kit also.

layer Provide the layer / color maps for display so you can load gds files from other software easily also.
layout Defines a `layout-only' scope design kit, suitable for basic chip design.
autorouter List the xsection/mcs's for which auto-routing are enabled.
basic-connector List the xsection/mcs's for which basic connectors are enabled.
The basic connectors are the straight / cosine / sine / bezier shapes, so single waveguide segment.
advanced-connector List the xsection/mcs's for which advanced connectors are enabled.
The advanced connectors are multi-segment waveguides like arc/straight/arc but also the way-point routers that can go around shapes but are not fully automated.
crossing-resolver List the xsection/mcs's for which crossing-resolver code is enabled.
A crossing-resolver automatically chops up waveguides that are crossing into waveguides that connect to a (pdk provided) crossing element.
busrouter List the xsection/mcs's for which busrouter code is enabled.
A busrouter allows to have a N:N connector style track that is typically complex in definition as it is oriented at multi-segment tracks.
dietemplate List the die-templates.
This depends a bit on the design kit - for 'chip' list the packaging providers. For packages (assembly design kits), you can set the list of chip providers that are configured.
Use 'unpackaged' for chip's basic die template.
schematic-capture Support schematic capture.
Schematic capture is typically done via a 'drag & drop' interface but it can also be done with scripting. The software should be able (at least) to export the schematic to a common netlist format so for example 'layout versus schematic' verification software can import it and compare a GDS against the original design.
processflow List the proces flows that use the mask-layers and some proces / material information to give a 2D/sideview (like in OptoDesigner) or full 3D model (with TCAD).
Instead of proces flows, you can also list the resulting waveguides or other design aspects (like RF routing).
sideview List the 'waveguides' for which mode solvers, thermo-optics, electro-optics, SOA, ... can be used. This may include non-photonics like RF tracks too.
topview List the 'waveguides' for which propagation algorithms can be easily applied, so having the 2D or 3D structure set up inside the design kit. This may include non-photonics like RF tracks too.
circuit Describe the scope of the circuit modelling shortly.
drc Describe the scope of the geometrical design rule checking shortly.
lvs Describe the scope of the geometrical design rule checking shortly.
release-notes Give the file-name with the release notes, relative to the design kits root directory, so it can be included in the design kit as additional information.
In case there are multiple release notes, for example from different vendors, it can be in the 'software' sections. For the foundry-provided release notes, it can be in the BB-section directly.
collaborative-projects List the collaborative projects which have enabled this design kit. This information will be put in the design kit and can be used to refer to project websites or mark up the typical "funded by ..." reference information.
This field is typically used outside the 'software' array, but may apply per software vendor also.

name

Type epSoftware documentation: See pdaIdentifier; defined in Epiphany.xsd to avoid cross-includes.