Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13259
  • 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 session and o_session

ShrikantTI

Hi All,

Please can you explain difference between session and o_session in ADE.

Ex :

winid = hiGetCurrentWindow()

winid~>sevSession

**************** Return Value : sevSession6

and

asiGetSession(hiGetCurrentWindow()) 

 ************* Return Value : stdobj@0x184c0b94

 

Both these values belong to the ADE session.  In some of the function session values in input and other especially asi* fucntions o_session in the input. Please can you elaborate on the difference?

Regards,

Shrikant 

Parents

  • Shrikant,

    They are for different layers in the application. The "sev" session is for the "Simulation EnVironment" - this is the ADE graphical windows. So the things that need "sev" sessions are related to the simulation user interface.

    The "asi" session is for the underlying OASIS layer (Open Analog Simulator Interface Socket). This is the API by which the simulator is plugged in - and it is not related to the user interface. This means that OCEAN for example uses the asi layer, but does not use the sev layer. The ADE interface uses the sev layer which interfaces to the asi layer.

    Hope that clarifies things.

    Andrew.

     

Reply

  • Shrikant,

    They are for different layers in the application. The "sev" session is for the "Simulation EnVironment" - this is the ADE graphical windows. So the things that need "sev" sessions are related to the simulation user interface.

    The "asi" session is for the underlying OASIS layer (Open Analog Simulator Interface Socket). This is the API by which the simulator is plugged in - and it is not related to the user interface. This means that OCEAN for example uses the asi layer, but does not use the sev layer. The ADE interface uses the sev layer which interfaces to the asi layer.

    Hope that clarifies things.

    Andrew.

     

Children
No Data

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.