• 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. Regarding "dbGetTrueOverlaps()"

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 144
  • Views 6570
  • 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

Regarding "dbGetTrueOverlaps()"

Neeraj Vardhan
Neeraj Vardhan over 12 years ago

Hi,

I am writing a code to get all instances under a marker layer. I tried to use dbGetTrueOverlaps() but it failed with an error of "*Error* dbGetTrueOverlaps: Invalid bBox - (((-0.915 0.025) (4.695 3.135)))". I have mentioned the code below, 

 

 procedure(nvGetVia3()

cv=geGetEditCellView()

x=geGetSelSet()

y=x~>bBox

shape_new=dbGetTrueOverlaps(cv y)

)

 

Thanks & Regards

Neeraj 

 

  • Cancel
  • dmay
    dmay over 12 years ago

    This operation is different in 5.1.41 as comapred with 6.1.x since vias are instances in the old version and via objects in the new version. Here are two ways you could do this:

    5.1.41
    via5s = setof(x dbProduceOverlapInst(geGetEditCellView() shape~>bBox 0) x~>cellName == "VIA5")

    6.1.5:
    via5s = setof(x dbViaQuery(geGetEditCellView() shape~>bBox 0 0) x~>cellName == "VIA5")

    In the examples above, shape refers to the object you're using for your bBox. It could be car(selectedSet()).

    Derek

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

    Derek,

    Your IC615 code will only work for customVias. Probably best to do x~>viaHeader~>viaDefName=="VIA5" rather than looking at x~>cellName; this will work for both customVias and stdVias.

    The IC5141 code is of course fine, since vias are just instances.

    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