• 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. puzzle about the session defination

Stats

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

puzzle about the session defination

imagesensor123
imagesensor123 over 13 years ago

Hi all,

    i saw in the artsit skill guide, there are several "session". ususally, we can use the sevSession(O_entry) to get a simulation environment session, the return value is "session", and many times, i saw the required data type is "o_session", is it the same thing? could you please give some introduction abou the "session" , and what's the session indeed.

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Because you can have multiple ADE sessions, many of the functions require something to tell it which session you're talking about.

    The simulation environment ("sev") needs to know which simulation environment you're talking about, so that's a "sevSession". The underlying OASIS layer (which is the Analog Simulation Interface, "asi") requires the asi session. A sevSession is actually just a symbol, and a asi session is an instance of a class. Typically the sev functions expect a sev session (such as sevSession(hiGetCurrentWindow()) and the asi functions expect an asi session (such as asiGetCurrentSession()). There are some functions like sevEnvironment(sevSessionId) which will return the asi session corresponding to the sev session. 

    It's all about which layer in the system you're dealing with. For example, OCEAN is all built on top of the "asi" layer - there is no simulation environment (sev) at all - because there's no UI.

    That was probably as clear as mud ;-)

    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