• 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. is it possible to extract the subcircuit names/models and...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 2441
  • 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

is it possible to extract the subcircuit names/models and the associated pins from input.scs ?

marcelpreda
marcelpreda over 6 years ago

Hi there,

I have the netlist file input.scs , on top is spectre but may include hspice files.

I need a script/utility/command to extract from the entire hierarchy all the subcircuit definitions and the associated pin names of for each subcircuit.

The order of pin names should be the same as in netlist.

I assume that somehow spectre is doing all this stuff internally, is there any possibility to dump this info in a flat text file to be parsed after that?

Thank you,

Marcel

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

    Hi Marcel,

    Add an info analysis such as this into the netlist:

    subcktInf info what=subckts where=file

    (you can do this in ADE via the Outputs->Save All form). 

    This will produce a file called input.info.subckts in the netlist directory (unless you specify a file to write it to) which includes the names of each subckt and the terminals (in order) for each subckt.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • marcelpreda
    marcelpreda over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks a lot, it worked, with the note taht teh name of the file is actually subckts.info.subckts .

    I have next question: for some subcircuits there is no info about teh parameters and pins (they are empty strings).

    My guess is that this is happening for the subcircuits which are not used in my design, but are defined in the model files. Is that true?

    Also, is there any documentation about the format of this file, or a skill API to interrogate this database?

    Best Regards,

    Marcel 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • marcelpreda
    marcelpreda over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks a lot, it worked, with the note taht teh name of the file is actually subckts.info.subckts .

    I have next question: for some subcircuits there is no info about teh parameters and pins (they are empty strings).

    My guess is that this is happening for the subcircuits which are not used in my design, but are defined in the model files. Is that true?

    Also, is there any documentation about the format of this file, or a skill API to interrogate this database?

    Best Regards,

    Marcel 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to marcelpreda

    Hi Marcel,

    The subckts.info.subckts is a "PSF" database that is saved into the psf directory if you have where=rawfile specified - there's an entry on the Outputs->Save All form which saves that by default. If you want to process the PSF results, you can simply do:

    selectResult('subckts) ; to avoid having to add ?results 'subckts on the end of the outputs() or pv() functions below:
    foreach(subckt outputs()
      terminals=pv(subckt "subckt_terminals")
      params=pv(subckt "subckt_params")
      unless(blankstrp(terminals)
        printf("%s : %s : %s\n" subckt terminals params)
      )
    )

    You're right - unused subckts (e.g. from model files) are output with an empty terminal list.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • marcelpreda
    marcelpreda over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks again.

    You are very kind, not too much work left for me: I just had to copy->paste :)

    Best Regards,

    Marcel

    • 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