xPDK_CompactModel_List
This section in a xPDK extends from xPDK_Header.The Compact Model List file provides a table with building block types. Per building block type a list of models is defined that describes what type of (compact) model should be defined for a BB/Model definition file using the Circuit Simulation file.
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.
<xPDK_CompactModel_List name="..." ... > ...
<MRL> ... </MRL> optional
<TRL> ... </TRL> optional
<bbtype> ... </bbtype> list
<doc> ... </doc> list
<groupRef> ... </groupRef> list
<license> ... </license>
<modeltype> ... </modeltype> list
<tex> ... </tex> list
<version> ... </version>
</xPDK_CompactModel_List>
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.TRL
Type pdaTRL documentation: Technology Readiness Level (TRL) as defined by the EU.bbtype
Define the type of building block.A building block type is used to define the models that such types support. This is the same for all foundries and needs to be supported by the circuit simulation software, so alignment between parties is key.
Type pdaBBtypeItem documentation: The BBType name is used for refences.
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.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_])*
license
Stichting PDAFlow Foundation. See http://www.pdaflow.org/xpdk_license.php. Type pdaLicense documentation:State the basic conditions of using the file and typically refer to legal documents.
License information should be compact enough to be clear as reference. The reference is expected to be to signed documents like Non Disclose Agreements (NDA) or service contracts and so on.
modeltype
Define the type of model.This defines the properties and parameters a models has. This is the same for all foundries and needs to be supported by the circuit simulation software, so alignment between parties is key.
Type pdaModelTypeItem documentation: Define a compact model per BB type
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.