• 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 Design
  3. Any option in VLS to save one particular layer in hierarchy...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 13747
  • 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

Any option in VLS to save one particular layer in hierarchy to a new view?

ssram
ssram over 9 years ago

Hi,

I've a layout which has hierarchies and groups in it. I need to save one particular layer or couple of layers selectively to a new view/cell. For example, I've got Matal5 in different hierarchies and groups and VIAs. I need to save just Metal5 to a new view/cell. How do i do this? The easiest method for me would be to do some kind of operation when i've only the intended layers made selectable/visible in the LSW. I do not want to flatten the whole hierarchy/group/VIA manually since its a really complex layout with too many of them.

Thanks

Sooraj

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

    Hi Sooraj,

    There are various articles on Cadence Online Support to allow you to do this kind of thing. Currently there's no built-in UI to do this because it's a relatively unusual request - but easy enough to write SKILL.

    In IC617/ICADV122 there are some new SKILL APIs (the "abe" functions (Advanced Boolean Engine)) which will make this much easier and more performant, however, be cautious about using them until about IC617 ISR5 since the arguments are changing slightly as they settle down,

    Before that you can take a look at this article.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • shlomo34
    shlomo34 over 3 years ago in reply to Andrew Beckett

    Hi, I am currently having the same issue. From your answer it sounds like the methodology was a work in progress 6 years ago - what is the best method right now?

    The script in your linked article looks promising - would it be possible to modify it to select multiple named layers rather than just one?

    Will this script run in a reasonable time with a very large layout (multiple GB if fully flattened) or might a different approach be faster?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • shlomo34
    shlomo34 over 3 years ago in reply to Andrew Beckett

    Hi, I am currently having the same issue. From your answer it sounds like the methodology was a work in progress 6 years ago - what is the best method right now?

    The script in your linked article looks promising - would it be possible to modify it to select multiple named layers rather than just one?

    Will this script run in a reasonable time with a very large layout (multiple GB if fully flattened) or might a different approach be faster?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to shlomo34

    The performance is likely to depend mostly on the number of objects there are to be "flattened" and the complexity of the hierarchy in the hierarchy traversal. It's hard to generalise. There's not particularly any benefit in updating the code to select multiple layers - you might just as well call it in a loop, iterating over the layers.

    Another approach would be to use the abe functions as I mentioned before. Something as simple as:

    abeInit(srcCv)
    M1=abeLayerFromCellView("Metal1")
    abeLayerToCellView(M1 "Metal1" ?cvId dstCv)
    abeDone()

    would copy the shapes on one layer (throughout the hierarchy) from a srcCv to a dstCv id. Note that the "abe" functions are limited to octalinear shapes (multiples of 45 degree angles), but providing that's OK, they're very likely to be the fastest approach. The code is also very simple...

    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