xPDK schema format extensions for OptoCompiler This schema defines a few OptoCompiler extensions for different items. The schema is located at: http://pdaflow.org/xsd/ per instance of the standard.
The schema is located at: http://pdaflow.org/xsd/ per instance of the standard.
  • License for general users / automation / ...:
    Use unmodified.
  • License for PDAFlow members:
    Allow to extend / modify / update in alignment with the other PDAFlow members.
Specify that the electrical tag library will be added to the OptoDesigner 02-file/
This pcell library will be used in the BBs to generate a spt-based side-file for mask assembly. Define the 'OpenAccess' purpose for a layer.
This will be used in writing to the tech-file and if a layer does not have it specified, it will be used as drawing.
You can add your own values in addition to the standard provided names:
  • redundant
  • gapFill
  • annotation
  • OPCAntiSerif
  • OPCSerif
  • slot
  • fill
  • drawing
  • fatal
  • critical
  • soCritical
  • soError
  • ackWarn
  • info
  • track
  • blockage
  • warning
  • tool1
  • tool0
  • label
  • flight
  • error
  • annotate
  • drawing1
  • drawing2
  • drawing3
  • drawing4
  • drawing5
  • drawing6
  • drawing7
  • drawing8
  • drawing9
  • boundary
  • pin
  • net
  • cell
  • all
 Define the function value in OptoCompiler tech file, section 'function' Mark for routing in in OptoCompiler tech file, section 'constraintGroups' This pcell fails in OptoCompiler PyCell; reason is listed in the string.
The BB definition needs to be fixed. Define the symbol view to copy.
For pcells it is handy to start with an existing symbol view in the OA database. Using an existing view saves errors and makes life easier. The default library to search in is the photonicLib; you can use the symbolLibName to select another library. Another option is to use the symbolViewTemplate field to create a symbol view based on a template. Define the library to copy the symbol view from.
See symbolView. Define the symbol view to use as basis.
When using this field, the OptoCompiler PDK will use this shape as template and generate the symbol based on the pre-defined template. This is an alternative of using the symbolView use. Use this for BBs that describe a die-template as (p)cell. Use this for BBs that describe a logo as (p)cell. Use this for BBs that is intended for the service supplier but can be placed by the designer. Typical examples are alignment loops, process control monitors or die-markers like cell numbers. This BB is a bio/gas/... type of sensor, normally a phase-change aspect. This BB is an electrical IO, can be DC or RF. Define OA-Tech ID.
The OA Tech file needs to have unique numbers that are PDK version constant for design migration. The default behavior is to use for layer definitions 65536*gds_number+gds_datatype and for the xsection the value 10000+N with N being the index in the xsection list.
Those values are very likely to be unique per PDK, but the xsection numbers are unlikely to be PDK version constant (adding or removing xsection's will fail this).
You can overrule the Tech ID with this field; the range is 256-10000 to avoid overlapping the default range. The number is free within this range, but as guideline:
  • 1000 - 1999 use this range for optical layers
  • 2000 - 2999 use this range for electrical layers
  • 3000 - 3999 use this range for mask annotations
  • 4000 - 4999 use this range for LVS recognition
 Define OA-Tech layer connection.
This field can be used to link layers and/or xsections; this tells that routing-wise ('design intent') they are directly connecting, possibly with a byLayer value.
You can define the connection in either layer/xsection, no need to define it twice.
For layer/xsection's that connect to more than one, define them from one layer, otherwise multiple lines will be written in the tech file.
Only use this for layers that have at least one of techLayerRouting='true' or techIncludeElectricalTag='true'. Define a byLayer, see OA-Tech docu. Define tech maskNumber.
This number somewhat reflects the layerstack and is used in LVS. The lower numbers should be the lower layers in the chip. The range does not need to be continous. MCS annotation to specify this xsection/layer/applayer is marking all waveguides.
This information is intended for Layout-vs-Schematic (LVS) with ICvalidator in OptoCompiler.