Issue link: https://resources.pcb.cadence.com/i/1180274
Allegro Constraint Compiler User Guide Allegro Constraint Compiler October 2019 6 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. Overview The power of Constraint Compiler is the ability to leverage data-agnostic constraints that can be developed once, validated and placed in a central library for future use in other designs. All designs are not exactly alike and may have slightly different net names or component reference designators. Constraint Compiler acknowledge this fact and provides a mapping table to correlate constraint and design-specific information and generates a standard Constraint Manager difference report to review changes that will be made to the design. You can run the compiler in either validation mode (report-only mode) or apply mode to incorporate the changes to the design with compiler options to merge or replace existing constraints. The following illustration shows an overview of process flow for Constraint Compiler. Design guides once transposed into the agnostic format can be stored in the constraint library for use in future designs. The data tables in the constraint library should be structured to be generic as possible to allow it to be leveraged with any design. Any design-specific objects should be stored as alias variables that can be updated through a mapping data table on a per design basis. Special table keys can be entered in the constraint library data table for filtering tables using the query functions of the compiler. Advantages of Constraining Designs Using Constraint Compiler The Constraint Compiler is capable of redirecting constraint information with absolutely no manual intervention and without any errors into a design.