Stats

  • Locked Locked
  • Replies 3
  • Subscribers 124
  • Views 13845
  • 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

How to make wavescan respect result changes?

archive

Hi,

If I have ocean save the result of a simulation from within CIW to a directory next to the standard "schematic" results in the ADE->results->select dialog I can easily jump back and forth between results and have AWD update the current waveform with results from that simulation result set. Jumping from single run to montecarlo to corner is no problem, AWD just updates the currently drawn waveforms with the data from the selected result set.

If I try to do the same with wavescan, there is no way to get wavescan to understand the change other than getting a new waveform window. The reload menu item does not make a change and resizing the window (a hidden trick) to redraw the waves with new data does also not work. I have to get a new window and then I have to select all the signals I want to see again. I personally stick to AWD but I have colleagues who "like" wavescan better and don't want to change.

Maybe this is actually a bug in wavescan that has to be reported?
--
Svenn


Originally posted in cdnusers.org by svenn
Parents
  • archive

    Hi, I think I may have the answer to your problem, because I encountered something similar not long ago.  The problem, in my case, arose when  I was bouncing back and forth between using AWD and Wavescan to display my results.  When I used Wavescan, and tried to reload a new database of simulation results (run via LSF) and view the results, I found that the Wavescan window would not update to the new results, but continued to display results from the old database.

    The solution turned out to be as follows:  When working in ADE, if you have "AWD" selected as your waveform tool in Session-->Options, then this problem occurs in which Wavescan will not automatically update its database when you are loading different simulation results.  The simplest solution is to leave "Wavescan" selected as your waveform viewing tool.  Then, Wavescan will automatically update its results with each new database of results you select.  (You can still leave your AWD windows and calculator open at the same time, if you want, so there is no need to leave the Session setting on "AWD".)

    An alternative solution is to close and then reopen the Wavescan calculator each time you load new data.  You can see in the calculator's banner window which set of data it is actually "looking" at.

    - Hugh


    Originally posted in cdnusers.org by Hugh
Reply
  • archive

    Hi, I think I may have the answer to your problem, because I encountered something similar not long ago.  The problem, in my case, arose when  I was bouncing back and forth between using AWD and Wavescan to display my results.  When I used Wavescan, and tried to reload a new database of simulation results (run via LSF) and view the results, I found that the Wavescan window would not update to the new results, but continued to display results from the old database.

    The solution turned out to be as follows:  When working in ADE, if you have "AWD" selected as your waveform tool in Session-->Options, then this problem occurs in which Wavescan will not automatically update its database when you are loading different simulation results.  The simplest solution is to leave "Wavescan" selected as your waveform viewing tool.  Then, Wavescan will automatically update its results with each new database of results you select.  (You can still leave your AWD windows and calculator open at the same time, if you want, so there is no need to leave the Session setting on "AWD".)

    An alternative solution is to close and then reopen the Wavescan calculator each time you load new data.  You can see in the calculator's banner window which set of data it is actually "looking" at.

    - Hugh


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