• 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. Info on abeLayerFromNet and abeLayerFromShapes function

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 14392
  • 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

Info on abeLayerFromNet and abeLayerFromShapes function

psill000
psill000 over 6 years ago

I am just looking for some understanding about the function abeLayerFromNet.

Does the function get only cellview objects on the net or does it extract from the hierarchy? 

Does the abeLayerFromShapes take the hierarchy path of a shape or only at cellview level?

Paul

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Paul,

    From a quick experiment, it follows the net through the hierarchy - assuming of course the net is connected to the instTerms of the instances and there are nets within those instances which are connected to the terminals. So it doesn't extract - it uses the connectivity information already in the database.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • psill000
    psill000 over 6 years ago in reply to Andrew Beckett

    Is there a way to add a property to the abeLayerToCellView shapes generated or can I put the shapes to a scratch cell?

    Paul

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to psill000

    Paul,

    If you look at the documentation for abeLayerToCellView you'll see that you can specify the output cellView (in more than one way) and that the function returns a list of shapes that are created (so you can put a property on them easily, or store them in a group).

    I just noticed I didn't answer the original question about abeLayerFromShapes. I think the answer is no - it just creates the abeLayer object from the coordinates of the shapes passed in. You can however create layers from hierarchical shapes by using abeLayerFromCellView which allows the number of levels of hierarchy to be specified.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • psill000
    psill000 over 6 years ago in reply to Andrew Beckett

    I am getting an error when I try to put a property on the shapes

    abeLayerToCellView(layAndNot "M1" ?purpose "cfill")

    tileIter = abeTileIterator(layAndNot)
    while(tile = tileIter~>next
    ;geSelectObject(tile)
    dbCreateProp(tile "viaProg" "boolean" t))

    CIW 

    *Error* dbCreateProp: Invalid database object - geoTile:236a7030

    Paul

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • psill000
    psill000 over 6 years ago in reply to Andrew Beckett

    I am getting an error when I try to put a property on the shapes

    abeLayerToCellView(layAndNot "M1" ?purpose "cfill")

    tileIter = abeTileIterator(layAndNot)
    while(tile = tileIter~>next
    ;geSelectObject(tile)
    dbCreateProp(tile "viaProg" "boolean" t))

    CIW 

    *Error* dbCreateProp: Invalid database object - geoTile:236a7030

    Paul

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to psill000

    That wasn't what you asked earlier. You can put properties on the result of abeLayerToCellView because these are shapes in the database. You can't put properties on the "abe" objects themselves because these are virtual objects that only exist in memory and aren't db objects. There's not really any benefit in being able to put properties on these. The error message is pretty clear - you're trying to add a property on a geoTile object which isn't a database object.

    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