• 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. Disappearing geometry

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13091
  • 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

Disappearing geometry

Dean1138
Dean1138 over 15 years ago

I have a pCell where contacts are repeated as the width increases -

pitch = 12 .0

repeats = (wu + 4.0)/12.0

 This works as expected for all widths EXCEPT the default, minimum, width in the CDF which is 8.0.  When "wu" is 8.0, the contact disappears.  If I make the CDF default 7.0 then the contact does not disappear when "wu" is 8.0 but then the instance has to be touched by a callback which then enforces the minimum "wu" value of 8.0

Is there a way to avoid having to call the callback for every instance?

Is there a way to automatically call the callback upon instantiation?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    My wild guess is that you have the CDF default for "wu" different than the pcell default. When you define the pcell (with pcDefinePCell), what is the default value for "wu"? And what is the default value in the CDF (you already said it is 8.0).

    If they are different, then what could happen is that the default value does not get stored on the instance when placed, and so it actually picks up the pcell default, not the CDF default, and hence it misbehaves.

    It's either this or some kind of floating point rounding error. Since you gave so little of the code, I can't really tell.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Dean1138
    Dean1138 over 15 years ago

    The pcell parameter default was indeed, another number.  When it was changed to the correct value, the problem went away.

    Thanks,

    Dean

    • 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