• 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. transient noise simulation

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 7042
  • 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

transient noise simulation

analog2
analog2 over 2 years ago

hi guys,

i'm running transient noise simulation, while trying to use this "noise contribution" option, to cancel the noise in few inverter stages:

in pre-layout simulation it works perfectly. however, once using extraction, it doesn't recognize the instance names inside the extracted region.

does someone have an idea how to solve it? maybe the syntax inside the "instance list" supposed to be different in this case?

Thx

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

    The trouble is likely to be that the extraction has probably flattened the hierarchy, and so using hierarchical instances is simply not going to work in this case...

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 2 years ago in reply to Andrew Beckett

    Dear analog2,

    analog2 said:
    does someone have an idea how to solve it?

    Andrew is correct, but I thought I would offer a technique I often used to maintain the hierarchy and yet provide a good estimate of the layout parasitics that the flattened hierarchy will produce. In Figure 1, I basically re-define each of the instances you include in your noise options panel as both the instance itself and the layout features that interconnect it to its neighbors. In this fashion, I can still use my top level schematic, but with a config view, will instantiate the extracted view of the newly defined layout boundaries for each instance. In this fashion, there are no layout features between each instance as the layouts of each directly abut. Hence, if you want to enable or disable the noise of N instances, you will create N layouts of each of the N instances where the layout of each includes the traces between it and its neighbors. I hope my explanation makes some sense analog2!

    Shawn

    Figure 1

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ShawnLogan
    ShawnLogan over 2 years ago in reply to Andrew Beckett

    Dear analog2,

    analog2 said:
    does someone have an idea how to solve it?

    Andrew is correct, but I thought I would offer a technique I often used to maintain the hierarchy and yet provide a good estimate of the layout parasitics that the flattened hierarchy will produce. In Figure 1, I basically re-define each of the instances you include in your noise options panel as both the instance itself and the layout features that interconnect it to its neighbors. In this fashion, I can still use my top level schematic, but with a config view, will instantiate the extracted view of the newly defined layout boundaries for each instance. In this fashion, there are no layout features between each instance as the layouts of each directly abut. Hence, if you want to enable or disable the noise of N instances, you will create N layouts of each of the N instances where the layout of each includes the traces between it and its neighbors. I hope my explanation makes some sense analog2!

    Shawn

    Figure 1

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • analog2
    analog2 over 2 years ago in reply to ShawnLogan

    Thx Logan for the suggestion. it sound like a good option.

    while considering your methodology, i guess i can use only 2 abutted layouts where i have the noised region & the non-noised region.

    • 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