• 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. difference between HSpice,HSpiceS,Spectre,SpectreS?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 11476
  • 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

difference between HSpice,HSpiceS,Spectre,SpectreS?

archive
archive over 17 years ago

Hi all,

What is the difference between all these simulator in Cadence? in wich case is it suitable  to use one rather than another?

Thanks in advance for your answers.


Originally posted in cdnusers.org by isazul
  • Cancel
  • archive
    archive over 17 years ago

    Well, hspice is a circuit simulator from Synopsys; spectre is a circuit simulator from Cadence. There are obviously lots of differences - and clearly I would be biased towards spectre ;-)

    For each simulator, there are two interfaces. There is hspiceD and hspiceS (hspice Direct, and hspice Socket), and
    spectre and spectreS (spectre direct, and spectre Socket).

    The "Socket" interfaces are the obsolete interfaces to the simulators. In the past, many simulators did not have a strong parameterisable language, and so what the Cadence tools did was use cdsSpice (which had a strong macro language, but was a fairly weak simulator) to act as a front end to the end simulator. All netlists were created in cdsSpice's macro language, and then translated into the destination simulator's language - without any parameterisation remaining.

    Such an approach worked, but it tended to mean that you couldn't access all the features of the underlying simulator.

    A few years ago (back in IC443, around 1999), the "direct" interfaces were introduced, and we're now cutting out the middle man and directly netlisting the right language. This is faster, more efficient, and gives greater access to the underlying simulator.

    So the hspiceD and spectre interfaces are the ones to go for. Which simulator you pick depends on your needs.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thank you a lot Andrew for your very clear and usefull answer.
    Ok for hspiceD and spectre, but in which case is it suitable to use hspiceD or spectre. For example, if I want to do a noise analysis of an analog circuit, which one is better?

    Regards

    Konin


    Originally posted in cdnusers.org by isazul
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    With spectre you also get a lot of information in ADE related to noise contributions (Results->Print->Noise Contributions) after doing a noise analysis.

    That said, hspice is a perfectly capable simulator for noise. My preference would be to use spectre though (even if you discount my allegiance to Cadence as an employee).

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Ok Andrew,
    thanks ,I learned a lot discussing with you and I hope to dicuss with you more often..;-).

    Regards,

    Konin


    Originally posted in cdnusers.org by isazul
    • 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