• 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. Parasitic node coordinates

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13397
  • 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

Parasitic node coordinates

Audi Austin
Audi Austin over 5 years ago

Howdy,

            In the netlist generated after parasitic extraction, nodes have been added at fracture points to add parasitic devices. For example, in the image below, I'm referring to the nodes IN#1 and IN#2. Is there a way to determine their co-ordinates relative to the layout co-ordinate system? I could not find them in the Skill command reference and when I query the parasitic elements in the extracted view, it gives the graphical pin locations of the elements rather than the physical.

Thanks

Audi

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Audi,

    Assuming you're talking about Quantus QRC as the extractor (you didn't say), and  you're generating an extracted view, the "xy" coordinate of the presistor/pcapacitor should related to the fractured shape that it is formed from (this is why the components are shown on the extracted view in the right place). The components also end up with an X and Y property on the instances (which matches the ~>xy origin of the component, so it's redundant I think). You can also find the shape for a particular fractured piece and if you look at shape~>net that's the sub-node and you'll find shape~>instTerms to find which presistor/pcapacitor components are connected to it.

    Alternatively, if you output Transistor DSPF, you can choose (on the netlisting tab in Quantus) to output the X and Y locations into the DSPF.

    If you're talking about a non-Cadence extractor, you'd have to ask the vendor for that extractor.

    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