Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 13286
  • 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

ADE_XL active database for multiple sessions

jasongong

Hi all,

i met some issue with ADEXL and hoping someone here can help.

say i open on ADE_XL session  (i.e. the ADEXL view) for sim1 first, and then i  open another ADEXL view for another simulation  sim2 bench.

when i want to go back to view the sim1 to view the simulation results and open the calculator by clicking the calculator button in sim1 ADEXL, the active (so called context by cadence) database is still point to the sim2. 

another problem is that when i run a single point run simulation,  when i click the "plot all" to plot the results, the active database is 

always pointing to the Interactive.<n>/1/<test_name>/psf/     even when i manually open the top psf and make it context database, if i rerun the

simulation, the leaf psf will be loaded automatically by results browser and become context database.  

any suggestion on this?

thanks

jason

  • Jason,

    Which sub-version are you using (Help->About in the CIW will tell you)? I'm not sure the behaviour you're describing is what I see - generally if you open the calculator from the right mouse button (context) menu over the outputs, it would make that point the context. If you start the calculator from the pulldown menu, it should make the root of the active history results the active setup (with one of the results databases anyway).

    Regards,

    Andrew.

  • Hi Andrew, the version is the IC6.1.6-64b.500.13.2. in fact i am getting confused about the context database even in ADE_L. i tried following behavior: 1. run ADE_L for sim1, 2. run ADE_L for sim2. 3. open "direct plot" from results pull down menu from ADE_L window for sim1 and plot 1 signal from sim1. 4. open direct plot from results pull down menu from ADE_L window for sim2 and plot another signal from sim2. 5. go back to sim1 graph (VIVA) window with signal i just plotted, click "browser", "results", "open results", interestingly, the loaded database is sim2. also if i click "calculator" button from VIVA of my sim1 window, the calculator also point to sim2 database. so it seems that VIVA or calculator will not automatically associated with the database/ADE_L from which it is brought up.

  • In general there is no memory of which "context" result database was active - there are a few issues here and there with multiple ADE L windows getting out of sync. In general with ADE XL though this doesn't happen.

    In ADE L in the results browser you might have to pick the correct database and do RMB->Set Context (or pick in the calculator from the cyclic field at the top). In ADE L it's sometimes necessary to do Results->Select to reset the active results. 

    My experiments of doing something similar to you worked fine (I was using ISR14, not ISR13), but there may be some specific reason why it's not working. Ideally report the specifics of your issue to customer support and we can aim to fix this. There's occasionally a response that "multiple ADE sessions aren't supported" but that's not correct - it was supposed to have been designed this way, but occasionally there have been particular cases where insufficient testing of multiple session interactions was done and the sessions interfere with each other. Most of those that I know of have gone now though...

    Regards,

    Andrew.

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.