• 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. RF Design
  3. Symbol view vs. spectre view

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 17931
  • 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

Symbol view vs. spectre view

Magistus
Magistus over 12 years ago

Hi,

I'm a little bit confused. I want to simulate some schematics using Spectre. The Cells i used have different Views. Until now i always used the symbol-view. But now i wondering: What are the other views used for? There are these views:


Should i use the spectre-view if i want to simulate using Spectre?

Thank you for all answers!

  • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 12 years ago

    You should always use the symbol view for building your schematics. The spectre view is used as a so-called stop view. Interestingly, the best explanation of the function of a stop view seems to be on Agilent's website at http://cp.literature.agilent.com/litweb/pdf/ads2008/dynlnkug/ads2008/Using_Switch_Views,_Stop_Views_and_the_Hierarchy_Editor.html 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Actually, this is documented in the Virtuoso Analog Design Environment L User Guide (in cdnshelp, or look at <ICinstDir>/doc/anasimhelp/anasimhelp.pdf ). There's a section called "How the Netlister Expands Hierarchy" which explains this. In fact Agilent's site seems to have lifted exactly the same flowchart from the ADE documentation ;-)

    It also refers to the hierarchy editor user guide (from the same document), which gives more control.

    The idea is that having determined how the netlister expands the hierarchy, once it reaches a stopping view, it will then use the information in the Simulation Information section of the CDF for that component to determine how the instance formatted in the netlister. 

    Typically the stop view is usually just a copy of the symbol, and is just a marker to tell it where to stop - it doesn't really need much information from the view itself - except the terminals. The terminals may potentially have additional (inherited) terminals for adding bulk terminals to 3 terminal transistors (for example), but in most cases the stopping view looks identical to the symbol view.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 12 years ago

    Andrew Beckett said:

    Actually, this is documented in the Virtuoso Analog Design Environment L User Guide (in cdnshelp, or look at <ICinstDir>/doc/anasimhelp/anasimhelp.pdf ). There's a section called "How the Netlister Expands Hierarchy" which explains this. In fact Agilent's site seems to have lifted exactly the same flowchart from the ADE documentation ;-)

    Thanks for letting me know, Andrew. For some reason, this document does not show up when I search support.cadence.com for "stop view".

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Magistus
    Magistus over 12 years ago

    I will read the User Guide an monday and write again if further questions occur.

    Thank you Frank and 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