Issue link: https://resources.pcb.cadence.com/i/1180266
Working with Design Partitions Design Partitioning October 2019 22 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. File Management Considerations Once exported, the team can move partition files to other locations and even rename them. Locations can be on or off the network. When off the network, refresh capability is disabled, along with any messaging that may come from the master. Cadence recommends all files to be resident on the network, preferably stored on a central server, to ensure accessibility. During the course of the design process, it is common to save the database. Different names may be used to reflect the stage of the design; after_place, after_route for example. Frequent name changing results in consequences as each team member must update the Workflow Manger and browse to the updated file. Cadence recommends using the same database name throughout the process for efficient file management. This ensures each team member has access to the latest file, assuming periodic saves, and minimizes interruptions during the flow. Tip Consider using the Allegro write command to save a copy of the database while keeping the current file active. The Allegro Partition Editor The Partition Editor is a version of the Allegro editor that works only with partition files. Although functionally identical to the Allegro editor, the Partition Editor has its own set of commands and menus. When the export process creates a partition file, it is an exact copy of the master design. It has all the same logical and physical data as the master design as well as the parameters of all the other partitions present at the time of export. However, all the database elements not owned by the partition have been marked read-only. Because of this, when the partition file is opened, only the objects owned by the partition display at full intensity; the remaining objects are dimmed. The partition boundary is also displayed at full intensity. This gives the partition designer a visual cue as to the working area and the objects that must be placed and routed. The partition designer cannot add elements outside the partition boundary and perform global database actions that would conflict with the master design. These actions include refreshing padstacks and symbols, importing data, and editing the stackup. In some cases, the entire command is not present in the Partition Editor; in other cases, the command user interface has been modified to behave in a read-only manner.