• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Where is the rodObj stored?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 14373
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Where is the rodObj stored?

Sylvio
Sylvio over 16 years ago

Hello,

I found an annoying behavior (bug?) of rodGetObj(...)

For IC6 I implemented a new VXL interface for layout generators (pcells which display generated/stored layout), which avoids wrapping menus. Unfortunately, all cells which are generated over this new interface (e.g. pick from schematic) don't have ROD handles, which are needed for higher level generators...

I seems, that rodGetObj("" cellView) does not create the ROD-object in the specified cellView but in pcCellView, when called from the body of a pcell...

In the documentation there is a note, that the second argument (cellView) is optional, if rodGetObj(..) is called from pcell context.

So I was sure that "optional" means something different from "is beeing ignored", isn't it?

My question is: Is this behavior intended? Is there a workaround (e.g pretend non-pcell context)?

Best Regards,

Sylvio

  • Cancel
Parents
  • Austin CAD Guy
    Austin CAD Guy over 16 years ago

     rodGetObj works as documented. The first argument is the shape ROD name, the second argument is a cellView ID for the search. The ROD name can be hierarchical INV1/M1/leftDiffPin. rodShape = rodGetObj("M14/leftDiffPin") or rodShape = rodGetObj( "leftDiffPin" instId) are the same (provided instId points to the M14 instance). Use rodGetNamedShapes to find the ROD shapes in your cellView.

    ROD applies to shapes and not to instances. If you are using rodAlign to align the instances, you have to pick a ROD shape in the instance. The shape has handles on it. You can use rodNameShape to create a ROD object from an existing shape.

    If you are using instances, you possibly would want to use the prBoundary object (not a ROD shape) as your abutment/alignment object. Since it is a design object, I don't think it can be a ROD shape. Use the bBox to calculate the edges.

    If you want to use rodAlign, create a recognition layer rectangle ROD shape and have use its handles to align.

     Ted

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Austin CAD Guy
    Austin CAD Guy over 16 years ago

     rodGetObj works as documented. The first argument is the shape ROD name, the second argument is a cellView ID for the search. The ROD name can be hierarchical INV1/M1/leftDiffPin. rodShape = rodGetObj("M14/leftDiffPin") or rodShape = rodGetObj( "leftDiffPin" instId) are the same (provided instId points to the M14 instance). Use rodGetNamedShapes to find the ROD shapes in your cellView.

    ROD applies to shapes and not to instances. If you are using rodAlign to align the instances, you have to pick a ROD shape in the instance. The shape has handles on it. You can use rodNameShape to create a ROD object from an existing shape.

    If you are using instances, you possibly would want to use the prBoundary object (not a ROD shape) as your abutment/alignment object. Since it is a design object, I don't think it can be a ROD shape. Use the bBox to calculate the edges.

    If you want to use rodAlign, create a recognition layer rectangle ROD shape and have use its handles to align.

     Ted

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information