• 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. Hierarchical Net Name Preservation in Quantus

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 125
  • Views 5972
  • 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

Hierarchical Net Name Preservation in Quantus

Anas Wanas
Anas Wanas over 2 years ago

Hi everyone,

We use the qreduce command in Quantus to apply frequency based reduction on an RCC DSPF netlist (generated by a different extraction tool). The options we use for the DSPF netlist change the hierarchical separator from slash to dot as well as preserve the original hierarchical net names so that we have statements such as save Xamp.vs (where vs is a non-port net inside amp subcircuit) work in both schematic and post-layout extractions (can be convenient for testing, even though we know the physical location of vs in the PEX netlist wiggles a bit).

By default, RCC netlists will also generate Xamp.vs, Xamp.vs:1, Xamp.vs:2 , ... , Xamp.vs:99 etc. which are reduced in number by qreduce. The issue is that since qreduce cannot understand that Xamp.vs is a "special" net, it usually removes it, keeping some of the other ":number" nets only (ex. Xamp.vs:76). This breaks the idea of having the hierarchical net names be the same in schematic and layout, so are there any special options or workarounds in qreduce to keep this 'special' net name from being removed?

Theoretically, one can create a script that sweeps over all hierarchical nets in the reduced netlist so that it replaces all instances of the first colon-named net it finds ex. Xamp.vs:76 with Xamp.vs, and repeat for all nets, but I was hoping for a built-in option.

Regards,

Anas

  • 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