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

     So, after some poking around, it appears more like this is some sort of interaction between NTFS and Virtuoso.  It's as though Virtuoso is looking at the network results and depending on when it last looked, it will respond with the data or just what's in memory.

     So I'm going to re-phrase the question into:

    Is there a way to force virtuoso to re-load from the network drive when I issue an openResults() command (as opposed to merely presenting what it thinks is the results are based on what it has in memory)?

     Mark

Reply
  • markbeck

     So, after some poking around, it appears more like this is some sort of interaction between NTFS and Virtuoso.  It's as though Virtuoso is looking at the network results and depending on when it last looked, it will respond with the data or just what's in memory.

     So I'm going to re-phrase the question into:

    Is there a way to force virtuoso to re-load from the network drive when I issue an openResults() command (as opposed to merely presenting what it thinks is the results are based on what it has in memory)?

     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.