pdaBBtypeItem

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.

<bbtype  name="..." ... > ...
  <MRL> ... </MRL>    optional
  <ModelName> ... </ModelName>   list
  <TRL> ... </TRL>    optional
  <doc> ... </doc>   list
  <extends> ... </extends>   list
  <groupRef> ... </groupRef>   list
  <tex> ... </tex>   list
  <ticket> ... </ticket>   list
</bbtype>

XSD

The schema file can be downloaded or viewed at xPDK_CompactModel_List.

Details

MRL

Type pdaMRL documentation: Manufacturing Readiness Level (MRL) as defined by the EU.

ModelName

Define a list of models that this type supports.
The model list is related to the simulation information. Type pdaCompactModelItem documentation: Define a compact model per BB type

TRL

Type pdaTRL documentation: Technology Readiness Level (TRL) as defined by the EU.

doc

Type pdaDocumentation documentation:
This field allows some (short, few lines) documentation to be written. It can be a long string, but the idea is not to replace a design manual.
This fields is like tex which allows documentation in LaTex format; doc is restricted to plain text.

extends

Define a list of basic bbtypes.
Using the extends allows to incorporate the models of the base class, like a multiple inheritance. Type pdaIdentifierExtended documentation:
Those names are mostly XML scope and thus for readability support more general naming then the pdaIdentifier.

groupRef

Type pdaIdentifier documentation:
Identifiers are used in the Python library for the getName() and


        setName()

function and can thus be used to identify the different elements in list s.
In text the specification is a letter, followed by letters, numbers, underscore. The XSD schema validation is a regular expression: [A-Za-z]([A-Za-z0-9_])*

name

Type pdaIdentifierExtended documentation:
Those names are mostly XML scope and thus for readability support more general naming then the pdaIdentifier.

tex

Type pdaTexDocumentation documentation: doc , but tex can be a long text in LaTex format to document the layer in more detail if needed.

You can document anything relevant for the topic you want to define.

Multiple paragraphs is fine. Format is Latex, so more complex content is possible.

ticket

Type pdaTicket documentation: