Stats

  • Locked Locked
  • Replies 4
  • Subscribers 142
  • Views 13759
  • 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

openResults() bug in 6.1.5?

markbeck

I'm encountering a bug in version  6.1.5.500.1

I am seeing a bug when I do the following:

  1. Run a paramRun transient simulation
  2. Issue an openResults() command to open the result set
  3. selectResults('tran)

This results in a error "results 'tran not found".

However, if I exit virtuoso and restart, I can issue the openResults and selectResults('tran) command and virtuoso is able to see the new results.

Is anyone else seeing this bug?

Mark

 

 

Parents
  • markbeck

    Thanks for the response, 

    Unfortunately your suggestion doesn't seem to work.

    I'm not convinced that it's entirely NFS since I do not see any of this type of behavior with virtuoso 6.1.4.  Also, I don't see this type of behaviour when I'm doing a simple transient/dc.  I only see this when I'm doing a paramRun() simulation.

    Perhaps something got broken between 6.1.4 and 6.1.5 in regards to how a param run is read?

    Is there another way (inside of Virtuoso) to force the results cache to re-fresh from disk?

    Mark

Reply
  • markbeck

    Thanks for the response, 

    Unfortunately your suggestion doesn't seem to work.

    I'm not convinced that it's entirely NFS since I do not see any of this type of behavior with virtuoso 6.1.4.  Also, I don't see this type of behaviour when I'm doing a simple transient/dc.  I only see this when I'm doing a paramRun() simulation.

    Perhaps something got broken between 6.1.4 and 6.1.5 in regards to how a param run is read?

    Is there another way (inside of Virtuoso) to force the results cache to re-fresh from disk?

    Mark

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.