• 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. Find a overlap of two layers if that layer present in PCell...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 17121
  • 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

Find a overlap of two layers if that layer present in PCell also

Mahesh gunde 1
Mahesh gunde 1 over 8 years ago

Hi all,


I am writing code for two layers overlap.

but got stuck to write full code.

Requirement:

Using layers: "od", "nt_n"

if "od" layer present in pcell and if its overlapping this nt_n which is in shape.


my code:

MARKER_LPP = list("marker" "error")
procedure( ntn_check()
odList   =  setof(i geGetEditCellView()->shapes car(i->lpp)=="od")
ntnList  =  setof(i geGetEditCellView()->shapes car(i->lpp)=="nt_n")
nt_n_var = dbLayerAnd(geGetEditCellView() MARKER_LPP odList ntnList  )
)

This code is checking for only shapes overlap, its ignoring if layers present are in instances.

I want to know if any shapes are overlapping with Pcell layers also.

Kindly help me on this.

Thanks,

Mahesh

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

    Mahesh,

    I agree with Lawrence - maybe this is a cultural thing, but (other than it not being standard outside of Indian English) it did suggest that you were expecting Lawrence (who doesn't work for Cadence, just kindly helping out colleagues from other organisations) to solve your problem for you.

    You might want to look at the "abe" (Advanced Boolean Engine) functions, such as abeLayerAnd. These were added in IC617, but I wouldn't use them if you're using the first few ISRs. Probably ISR8 and later (roughly speaking) should be OK, because the interface to them changed slightly because they were inconsistent with other functions in SKILL. The code below however isn't dependent upon any of these arguments that changed. These can find shapes through the hierarchy (the default behaviour) - for example:

    abeInit(geGetEditCellView())
    od=abeLayerFromCellView("od")
    nt_n=abeLayerFromCellView("nt_n")
    overlaps=abeNewLayer()
    abeLayerAndNot(od nt_n overlaps)
    ; or could use abeLayerToHilightSet - see the manual
    abeLayerToCellView(overlaps MARKER_LPP)

    Note, this code has not been tested - it was just to point you in the (possibly) right direction.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Mahesh,

    I agree with Lawrence - maybe this is a cultural thing, but (other than it not being standard outside of Indian English) it did suggest that you were expecting Lawrence (who doesn't work for Cadence, just kindly helping out colleagues from other organisations) to solve your problem for you.

    You might want to look at the "abe" (Advanced Boolean Engine) functions, such as abeLayerAnd. These were added in IC617, but I wouldn't use them if you're using the first few ISRs. Probably ISR8 and later (roughly speaking) should be OK, because the interface to them changed slightly because they were inconsistent with other functions in SKILL. The code below however isn't dependent upon any of these arguments that changed. These can find shapes through the hierarchy (the default behaviour) - for example:

    abeInit(geGetEditCellView())
    od=abeLayerFromCellView("od")
    nt_n=abeLayerFromCellView("nt_n")
    overlaps=abeNewLayer()
    abeLayerAndNot(od nt_n overlaps)
    ; or could use abeLayerToHilightSet - see the manual
    abeLayerToCellView(overlaps MARKER_LPP)

    Note, this code has not been tested - it was just to point you in the (possibly) right direction.

    Regards,

    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