• 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. get the overlap area of adjacent metals in single hiera...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 17344
  • 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

get the overlap area of adjacent metals in single hierarchy

naresh9005
naresh9005 over 6 years ago

Hi 

we are trying to find the overlapping area of adjacent metals(i.e metal1 to metal2, and metal2 to metal3 and so on ) in a single hierarchy.

we are using "dbLayerStraddl()"  function but it is creating a new shape over the first input layer list. but we required the only common area between the two layers.

please help with this problem .

procedure(metalOverlap()
prog( ()
cv=geGetEditCellView()

layer1=list()
layer2=list()

foreach(a cv~>shapes
when(a~>layerName == "MET2"
layer1=cons(a layer1)
)
when(a~>layerName == "MET3"
layer2=cons(a layer2)
)
)
ov=dbLayerStraddl(cv "POLY" layer1 layer2)
)
)
hiSetBindKey("Layout" "ShiftCtrl<Key>q" "metalOverlap()")

  • Cancel
Parents
  • RK56
    RK56 over 6 years ago

    Hi,

    You can try with Advanced Boolean engine functions which have far better outcome. You can control which hierarchy layer you need to process. Check abeLayerFromCellView()

    -Ramakrishnan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • naresh9005
    naresh9005 over 6 years ago in reply to RK56

    Thank you for your replay, 

    our layout cell view has only one hierarchy, but we want to get the overlapping area with coordinates, could you help me with more details?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RK56
    RK56 over 6 years ago in reply to naresh9005

    Hi,

    Try this to implement using ABE. I copied this script from cadence documentation and modified

    abeInit( geGetEditCellView() )

    M1 = abeLayerFromCellView( "Metal1" ?startLevel 0 ?stopLevel 1 )

    M2 = abeLayerFromCellView( "Metal2" ?purpose "drawing" ?startLevel 0 ?stopLevel 1)

    overlapLayer = abeNewLayer()

    abeLayerAnd( M1 M2 overlapLayer)

    abeLayerToCellView( overlapLayer "marker" ?purpose "error" )

    abeDone()

    You can iterate over the overlapLayer and get all shapes coordinates. Modify the layer names as per your need.

    -Ramakrishnan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Saravanan PK
    Saravanan PK over 5 years ago in reply to RK56

    Hi Ramakrishnan,

    what will be the case if I want to find the overlap of the same metals? above code works fine, if both metals are different.

    Thanks,

    Saravanan.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Saravanan PK

    There's no capability to do a self-and operation with the abeLayer functions - there's some discussion of this in an internal change request (CCR 1522996) but that was just a question to R&D, not an enhancement.

    Normally you'd use a physical verification tool to do this - they typically offer a means of doing a self-and on unmerged layers. Diva and Assura support this via a single layer input to geomAnd, and PVS supports it by providing the same (unmerged) input data as both inputs to the and command in the PVS rule language. Other physical verification tools are available ;-)

    So I'd say the answer is to write a short physical verification rule deck to generate the data you need.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Saravanan PK

    There's no capability to do a self-and operation with the abeLayer functions - there's some discussion of this in an internal change request (CCR 1522996) but that was just a question to R&D, not an enhancement.

    Normally you'd use a physical verification tool to do this - they typically offer a means of doing a self-and on unmerged layers. Diva and Assura support this via a single layer input to geomAnd, and PVS supports it by providing the same (unmerged) input data as both inputs to the and command in the PVS rule language. Other physical verification tools are available ;-)

    So I'd say the answer is to write a short physical verification rule deck to generate the data you need.

    Andrew.

    • 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