Synopsys, Inc.

Dassault Systemes Americas Corp.

Dassault Systemes Enovia Corporation

Dassault Systems Enovia Corporation

Dana Rigg

Mahesh Raghavan

Peter Haynes

Lawrence Steven Bach

Guy R Richardson

Semyon Reyfman

Kenneth Cox

Mitch Mastellone

Peter Elliott Haynes

In one aspect, a computer-implemented method for managing conflicts in a logical component hierarchy is provided. The logical component hierarchy includes an ancestor component and a descendant component associated with the ancestor component. The method uses a computer device in communication with a memory. The method includes determining, by the computer device, a requirement to replace the descendant component, within the logical component hierarchy, with an overriding component. The overriding component is associated with the ancestor component by an overriding reference. The method also includes replacing the descendant component with the overriding component within the logical component hierarchy.

Methods and systems for resolving conflicts in hierarchically-referenced data

A computer-implemented method for filtering components from a logical component hierarchy is provided. The method uses a computing device having a processor and a memory. The method includes identifying, in the memory, a filter associated with the logical component hierarchy. The method also includes comparing, by the processor, a sub-component of the logical component hierarchy with the filter. The method further includes identifying the sub-component for filtration based on the comparison of the sub-component with the filter. The method also includes filtering the sub-component from the logical component hierarchy.

Methods and systems for filtering components in hierarchically-referenced data

Described are methods, systems, and apparatus, including computer program products for managing a hierarchy of modules. A user can select a first hierarchy or a second hierarchy, where the first hierarchy includes a module and a first sub-module. The module is associated with a component and the first sub-module is associated with a first sub-component of the component. The module is associated with the first sub-module using a first hierarchical reference of a first type. The second hierarchy includes the module and a second sub-module, where the second sub-module is associated with the first sub-component. The module is associated with the second sub-module using a second hierarchical reference of a second type that is different from the first type.

Managing hierarchies of components

Adding a layer of abstraction to the generation of a runset for DRC rules, by defining a meta language hides from the user the language of a specific verification tool (also called &ldquo;native language&rdquo;). The meta language can be used directly by the user to express in a file (also called &ldquo;meta runset&rdquo;) the DRC rules to be used to create an input for the verification tool in the native language (also called simply &ldquo;runset&rdquo;). A runset generator uses DRC rules supplied by a user to generate a runset in a native language (that is identified by the user). The runset generator can use templates to generate a runset. Each template (also called &ldquo;DRC template&rdquo;) contains code (can be in source form or in object form) for implementation of a DRC rule or derived layer in the native language of a specific verification tool (such as HERCULES). Thus implementation of DRC rules is hidden from the novice user. During automatic generation of DRC rules, the location in a runset of a derived layer specified by the user is optimized, by automatically inserting such a definition immediately prior to a DRC rule that uses the definition (also called &ldquo;just in time&rdquo; layer definition). Such just-in-time layer definition reduces memory usage of the verification tool, and ensures that unused physical layers or derived layers do not appear in the automatically generated runset.

Method and system for automatic generation of DRC rules with just in time definition of derived layers

A method automatically specifies a unique number of an error layer for each DRC rule in a runset. Therefore, all errors related to a given DRC rule are reported by a layout verification tool in the uniquely specified error layer. Furthermore, the method also automatically specifies a unique number of a filter layer that has the same extent as a quality assurance (QA) cell for testing the DRC rule. The filter layer is logically operated (e.g. ANDed) with the error layer to uniquely identify a failure related to the DRC rule (i.e. errors from all other QA cells are filtered out). The QA cells are generated automatically by use of a library of templates. During regression testing, the first time a DRC runset is run against a test design or QA cell library the results are manually verified and stored as &ldquo;expected&rdquo; results. Thereafter when the runset changes or a new version of the verification tool becomes available the test data may be used to identify any differences in the new results, by automatic comparison with the expected results. Specifically, the regression testing method graphically compares the new test results with the expected results and highlights the differences. A utility automatically compares a first set and a second set of shapes in the two sets of results, and can be used for comparison of any two drawings (not necessarily integrated circuit layouts).

Growing community of inventors

Austin, TX, United States of America

Dana Rigg