C

---

Load CDBA Type Tables

---

When you load a technology file, you can get some unexpected results if all of the following conditions are true:

• The technology file version is not specified.
• The default value for a constraint is not specified.
• The value table is associated with a constraint other than the following:
  • allowedSpacingRanges
  • minCutClassSpacing
  • minSpacing with index twoWidth
  • minViaSpacing
  • viaSpacing

This is because such constraints are interpreted using the "CDBA type" table. A "CDBA type" table is stored as a 1-D or 2-D "OA type" table, but the contents of the specified and missing entries in a "CDBA type" table are populated differently as compared to an "OA type" table. A 1-D table cannot have "missing" entries, but a 2-D table can have "missing" entries.

The syntax of a "CDBA type" table allows you to specify the interpolation type, which is used to fill in the missing entries based on the nearest neighboring entries. For example, in a "snap down" table, if the n^th entry is missing, the n+1^th entry is copied to the n^th entry. If it is not possible to interpolate the entry (for example, in a table in which the interpolation type is "=="), the entry is set to 0.

Additionally, only one "CDBA style" table can be parsed, adjusted, and stored for a given constraint definition and layer. If multiple tables are defined, only the last one is stored and converted; a warning is not displayed.