• 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. What's the difference between cellView~>prBoundary and cellView...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 5222
  • 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

What's the difference between cellView~>prBoundary and cellView->shapes->lpp ?

Zelli
Zelli over 12 years ago

when lpp=list("prBoundary" "boundary") ?

 I mean, what's the cellView~>prBoundary supposed to do?

Thank you.

  • Cancel
  • skillUser
    skillUser over 12 years ago

     Hi Zelli,

    The prBoundary is the place & route boundary that instances and shapes should be placed within. The automated Place & Route tools will operate within the confines of this boundary. In IC51x and earlier the prBoundary was a shape on a specific layer-purpose pair (e.g. "prBoundary" "boundary" or "prBoundary" "drawing").

    cellView~>shapes~>lpp is something else entirely: in a cellview a shape exists on a specific layer-purpose pair, querying all the shapes of the cellview (cellView~>shapes) will obtain a list of all of the shape database objects, and further querying for the 'lpp' attribute will apply that query to each of the shapes (as long as you use the "~>" operator, not the "->" operator), so the compound query returns a list of the lpps, one for each shape. If you just want to see the lpps used in the cellview, do cellView~>lpps to obtain a list of the LP (layer-purpose) objects. The lpp query is not equivalent to the lpps query; the lpp attribute of a shape is a list of the layer and purpose, the lpps attribute of the cellview is a list of the LP db objects.

    Hopefully this answers your questions?

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Zelli
    Zelli over 12 years ago

     Thank you, Lawrence. Your explanation about ~> is very useful because I've never used it.

    Still, I would like to know something about cellView~>prBoundary.  Do you mean that a kind of Encounter can use the prBoundary instead of ("prBoundary" "boundary")?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 12 years ago

    If you are using the IC61x release of virtuoso, the underlying database OpenAccess (OA) - this uses a prBoundary object to represent the place and router boundary, rather than a shape on a specific layer.  The recent versions of Encounter operate on the OA database so they should understand the prBoundary object. I don't work with Encounter tools, so I'm not able to provide much more assistance on that topic, sorry.

    Please state the versions that you are using and perhaps we can give better answers.

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Zelli
    Zelli over 12 years ago

     I don't know the release of Virtuoso because it's a holiday and I'm at home. But I know it's a newer version than the one I've used before.
    Then how they create that prBounary? Somehow through menus?
    What about LEF?  Are the shapes still in use or not?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    As Lawrence pointed out, prBoundary is now a specific object in OpenAccess, and tools that need a boundary (such as various parts of the Virtuoso Layout Suite, such as VLS-XL and the space based router, placers, etc, and also Encounter) will create such an object. 

    For example VLS-XL creates one when you do a generate all from source. Also you can create them manually with the Create->P&R Objects menu.

    No Cadence tool is using shapes on the prBoundary/boundary layer purpose pair any more.

    LEF will also use the prBoundary object.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Zelli
    Zelli over 12 years ago

    Thank you very much, Andrew.
    The question is now answered :)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • johnmck8
    johnmck8 over 12 years ago

    Andrew,

    I get that prBoundary is now an object but is there an object equivalent to cellView~>shapes~>lpp?

     

    Thanks so much,

    John 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    John,

    I don't understand the question. The lpp attribute of a shape (so what you get when doing cellView~>shapes~>lpp) is a list of layerName and purpose - that is the same in OA as in CDB. Why would it be an object now?

    The change with OA was to implement specific objects for things where previously shapes on particular layer purpose pairs had special meaning.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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