Dynamic Categories

Some categories are divided into multiple classifications according to the process area in which the measurement is applied, or the type of component involved in the measurement, or the component side used in the measurement.

For example, the Comp. Spacing category (c2c) appears as several sub-classifications:

smt:c2c;soic_sot_nn — This category includes measurements that are in the SMT process area, between the narrow side of soic components (the first ‘n’) and the narrow side of sot components (the second ‘n’).

fs_smt:c2c;tsop_tsop_wn — This category includes measurements that are in the overlap area between FS and SMT process areas (or that start in one and end in the other), between the wide side of a tsop component and the narrow side of another tsop component.

In the documentation, this sort of classification is indicated by entries such as this:

Full internal name: <Area>:c2c;<PkgTypeA>_<PkgTypeB>_<CompSide><CompSide>

  • <Area> — The process area name.

  • <PkgType> — The types of components involved. See “Classification by Component Type”.

  • <CompSide><CompSide> — The sides of the components that the measurement touches: w or n. If only one component is involved, there will be only one <CompSide> (if, for example, the other feature measured is a rout feature, where specifying its narrow or wide side is irrelevant). See “Classification by Component Side”.

A single wildcard asterisk (*) can be used alone in ERF models to represent the <Area>, the <PkgType>, or the <CompSide><CompSide> fields, to indicate that all measurements are to be classified by this entry. A wildcard character along with other characters to form a string is not allowed.

  • This usage of wildcards is legal: *:c2c;tsop_tsop_*

    It indicates component spacing in all process areas, between two tsop components regardless of the side involved.

  • This usage of wildcards is NOT legal: *:c2c;*conn_tsop_*

    This is not allowed because the string *conn is an illegal use of the single wildcard character rule.

Ranges can use exact name specification or wildcards. The wildcard character asterisk (*) is used to indicate all measurements in areas of not otherwise defined ranges.

  • SMT:c2c;1210_soj_nn=50, 50, 50.1 — This category reports measurements in the SMT area, between the narrow side of one component and the narrow side of the other.

  • *:c2c;1210_soj_*=50, 50, 50.1 — This category reports measurements in all process areas, between two components, regardless of the side involved.

Ranges with two entity types must be ordered alphabetically.

  • Correct — *:c2c;axial_sot_*

  • Incorrect — *:c2c;sot_axial_*

Range order in the ERF affects the order of matching.

  • This order yields exact results, because results of process area SMT between 1210 and soj are reported to the first category, and the second category reports results that do not fall into the first category, but are measured between the narrow sides of 1210 and any other type of component.

    SMT:c2c;1210_soj_nn=50,50,50.1
    *:c2c;1210_*_nn=100,100,100.1
  • This order results in no results being reported to the second category, because the more general category will already have reported those results.

    *:c2c;1210_*_nn=100,100,100.1
    SMT:c2c;1210_soj_nn=50,50,50.1