Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 5903
  • 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

Re-loading (and/or controlling) History Items in ADEXL view

Michele Ancis

Hi all,

due to a mix of design manager software "issue" and Virtuoso crash, I can no longer see the list of history items I had when I reload my ADE XL view.

Basically, I had my ADE XL open in "read" mode and all these items are no longer available in the history pane.

However, the data is still in the simulation/results directory.

My question is whether you know of a simple way of re-integrating these items back in the view, so that I can access them from the common interface through a simple RMB->View Results...

I can think of ways of loading the data (as in with the Results Browser or OpenResults() from a script) and then go from there, but any solution I can devise is relatively cumbersome, especially because not all of my history items have meaningful names ;-) and refer to different simulations so I'll have to sift through them quite a bit.

Thanks as usual for helping!!

Michele

Parents

  • Michele,

    Michele Ancis said:
    just finding the way to reinsert the DB handle into the ADE XL view and go from there...

    This is the bit which requires the large-scale hacking. There's no "just" about it. It's more than just a handle - the history contains all the state information, pointers to results locations, and various other things - and there aren't public APIs to do all this anyway. It could be done, but it's really a good way of corrupting  your ADE XL database if you get it wrong.

    The RDB viewer that you used doesn't have an export, but what you could use is similar to code that I pointed you at before:

    http://community.cadence.com/cadence_technology_forums/f/38/p/32425/1341416#1341416

    In that post, go down to the bit starting axlReadHistoryResDB, and from that point onwards you can see the code to traverse the result database and then print it out. Rather than using axlReadHistoryResDB, you could use rdb=axlReadResDB("/path/to/Interactive.2.rdb") - you don't have to have an ADE XL view open to do this. If all the data you want is scalar, this should be pretty straightforward. 

    This approach shouldn't be Mission Impossible ;-)

    Regards,

    Andrew.

Reply

  • Michele,

    Michele Ancis said:
    just finding the way to reinsert the DB handle into the ADE XL view and go from there...

    This is the bit which requires the large-scale hacking. There's no "just" about it. It's more than just a handle - the history contains all the state information, pointers to results locations, and various other things - and there aren't public APIs to do all this anyway. It could be done, but it's really a good way of corrupting  your ADE XL database if you get it wrong.

    The RDB viewer that you used doesn't have an export, but what you could use is similar to code that I pointed you at before:

    http://community.cadence.com/cadence_technology_forums/f/38/p/32425/1341416#1341416

    In that post, go down to the bit starting axlReadHistoryResDB, and from that point onwards you can see the code to traverse the result database and then print it out. Rather than using axlReadHistoryResDB, you could use rdb=axlReadResDB("/path/to/Interactive.2.rdb") - you don't have to have an ADE XL view open to do this. If all the data you want is scalar, this should be pretty straightforward. 

    This approach shouldn't be Mission Impossible ;-)

    Regards,

    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.