• 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. Temporarily Flattening Pcells

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 142
  • Views 16615
  • 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

Temporarily Flattening Pcells

archive
archive over 17 years ago

I am using the bounding boxes of all shapes in a cell database at all hierarchy levels.
I run into problems when encountering PCells that are stretched or otherwise altered since when opening the pcell I loose all the parameters.

Is there any way to access the drawn shapes in a pcell with parameters?

I searched and found this:

You can't - these only work with database objects in the current cellView. You'd need to flatten first, or use a verification tool (e.g. Diva, Assura) to do the layer manipulation. You could use dbFlattenInst() to bring everything to the current cellView, or copy the source shapes to dummy shapes in the top cellView and then work on those.

I've used a flow in the past where I've used dbGetOverlaps to find hierarchical shapes, work out the transformation by concatenating all the transforms, and then use dbCopyFig to copy into the top level cellView, and then use dbLayerAnd on these shapes - and then delete the "flattened" copies.

Regards,

Andrew.

The data must be there because the shapes in a pcell have to be drawn. Can I access those "drawn" bBoxes through SKILL?


Originally posted in cdnusers.org by ahamlett
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Can't quite remember where I said that, but I'm 99% sure you're quoting me in the wrong context.

    You definitely can access the shapes in an evaluated pcell. If you have an instance of the pcell in your layout, then doing:

    instId~>master

    will give you the cellView ID of the "subMaster" of the pcell - i.e. the layout of the particular variant that has been instantiated. A pcell consists of the "superMaster" (which is what you get when you open it directly), and a collection of "subMasters" - one per variant. The subMaster is a readonly representation of all the objects in the layout, and you can read the shapes and so on it in it in exactly the way you would with any other layout.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    Can't quite remember where I said that, but I'm 99% sure you're quoting me in the wrong context.

    You definitely can access the shapes in an evaluated pcell. If you have an instance of the pcell in your layout, then doing:

    instId~>master

    will give you the cellView ID of the "subMaster" of the pcell - i.e. the layout of the particular variant that has been instantiated. A pcell consists of the "superMaster" (which is what you get when you open it directly), and a collection of "subMasters" - one per variant. The subMaster is a readonly representation of all the objects in the layout, and you can read the shapes and so on it in it in exactly the way you would with any other layout.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • 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