E
How Virtuoso Layout Editor Works with ROD Objects
The following tables summarize the level of support for how Virtuoso® Layout XL commands work on relative object design (ROD) objects in the current release.
Using commands that are not fully supported for ROD objects could cause the objects to lose the ROD information associated with them, changing the objects into ordinary shapes.
|
Create and name new rectangles as ROD objects using the Create Rectangle form. |
|
|
|
Create and name new polygons as ROD objects using the Create Polygon form. |
|
|
Create and name paths as ROD objects using the Create Path form. |
|
Create and name new multipart paths as ROD objects using the Create Multipart Path form. This form lets you choose a template from your technology file, load templates from an ASCII file, and save form values as a template in your technology file (if you have write permission) or in an ASCII file. |
|
|
|
You cannot create a label as a ROD object. However, you can make an existing label a ROD object by assigning it a name with the |
|
|
An instance is automatically a ROD object because it has a unique name. The ROD object name is the same as the instance name. |
|
|
Create and name new pins as ROD objects using the Create Pin Shape form. |
|
You cannot create a pin from a label as a ROD object. However, you can make an existing pin a ROD object by assigning it a name with the |
|
|
Circles are supported as ROD objects. However, there is no user interface for naming a circle; use the |
|
|
Ellipses are supported as ROD objects. However, there is no user interface for naming an ellipse; use the |
|
|
Donuts are supported as ROD objects. However, there is no user interface for naming a donut; use the |
|
|
You cannot create a shape using a layer generation operation as a ROD object. However, you can make a generated shape a ROD object by assigning it a name with the |
The Mosaic is not supported as ROD objects:
|
|
|
|
|
|
|
|
Moving ROD objects is supported as follows:
|
|
|
Copying ROD objects is supported as follows:
|
|
|
The Stretch command fully supports ROD objects, including stretchable parameterized cells (Pcells). |
|
|
Except for multipart paths and multipart rectangles, all reshapable ROD objects remain ROD objects after a Reshape operation. When you reshape any ROD object, all alignments to that object are deleted. |
|
|
The Delete command fully supports ROD objects. When you delete using the Net Interconnect option, all ROD objects on the selected net are deleted, except for pins. For multipart paths (MPP) and multipart rectangles (MPR), when the master path or master rectangle is on the selected net, the MPP or MPR and all subparts are deleted; otherwise, no part of the MPP or MPR is deleted. When you delete a segment of an MPP with the Path Segment option, the remaining segments of the MPP become two separate multipart paths, each with its own name. |
|
|
|
|
|
You can search for any ROD object by name, including rectangles, paths, polygons, and text display objects. |
|
|
Merge is not supported for ROD objects. When ROD objects are merged, the resulting shape is not a ROD object. |
|
The Flatten command fully supports ROD objects. To preserve the attributes of ROD objects (such as object name, alignments, multipart path subparts, and master rectangles in multipart rectangles), turn on the Preserve ROD Objects button in the Flatten form. When this option is off, ROD objects become ordinary unnamed objects, the subparts of multipart paths become ordinary paths and rectangles, and the master rectangles in multipart rectangles become ordinary, unnamed rectangles.
However if the ROD object is at top (zero-level) it does not get flattened using the Flatten command.
The system assigns the flattened object a name based on the hierarchical name of the ROD object by replacing slashes with dashes. For example, when you flatten the ROD object |
|
|
Most shapes lose ROD attributes when they are chopped. For multipart paths, the effect of a chop depends on what parts are choppable and how you chop them. For details, see Chopping Multipart Paths. When you chop the master rectangle of a multipart rectangle, all subrectangles are deleted and the shapes resulting from chopping the master rectangle are regular, unnamed database shapes. When you chop any ROD object, all alignments to that object are deleted. |
|
|
The Modify Corner command supports ROD polygons and ROD rectangles, except for master rectangles that are a part of a multipart rectangle. |
|
|
|
The Size command supports ROD objects. However, when you size a multipart path (MPP), the master path becomes a ROD polygon and inherits its name from the original MPP; all subparts become ordinary, unnamed database shapes. When you size any ROD object, all alignments to that object are deleted. |
|
|
Except for ellipses, circles, donuts, multipart paths, and multipart rectangles, ROD objects remain ROD objects after a split operation. When you split any ROD object, all alignments to that object are deleted. |
|
The Convert To Polygon command fully supports ROD objects, except for rectangles and multipart rectangles. The Convert To Polygon command has no affect on rectangles and multipart rectangles. When you convert a multipart path, the polygon resulting from the master path is a ROD object and takes the name of the multipart path. Subparts, if any, become unnamed, ordinary database shapes (paths and rectangles). Subparts are not converted to polygons. When you convert any ROD object (except rectangles and multipart rectangles) to a polygon, all alignments to the converted object are deleted. |
|
|
|
With the exception of multipart rectangles the Rotate command supports the rotation of ROD objects, unless there are alignments. Avoid rotating aligned ROD objects because aligned handle names are not updated after the rotation, so the results might not be what you want. For multipart rectangles with subrectangles offset from the master rectangle corners, avoid rotation unless the offsets are all equal. The Rotate command does not rotate these offsets. |
|
|
The Yank command does not support ROD objects. The Yank command copies only the shapes, but not the names of the shapes or the alignments. When you paste, the result is unnamed, unaligned, non-ROD shapes. |
|
|
The Paste command does not support ROD objects. If you yank and paste ROD objects, the result is unnamed, unaligned, non-ROD shapes. |
Return to top