Stats

  • Locked Locked
  • Replies 4
  • Subscribers 127
  • Views 13988
  • 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

ADEXL reverted to OCEAN mode and unable to revert back to ADE

rkic

Bit of history here...I created a ADEXL view with a test under it. I had to run a regression on the design and did that via ocean through the unix shell. The simulations ran successfully and generated all the required results. When i re-opened the ADEXL view after the ocean run, and wanted to run just one simulation using the GUI, everything pertaining to the test had switched to OCEAN. For example, when i hover the mouse under the test name, in the pink box which provides details of the test, it shows "Tool : OCEAN" Ordinarily this would be "Tool : ADE". In addition when i right click on the test and try to open the ADE-L test editor by clicking on open test editor, it opens a text file containing all the ocean commands related to that test rather than the ADE-L GUI.

How do i get the test to revert to the ADE mode?

I have my save number of history entries =1 and overwrite previous run checked. IN that since my previous run was in OCEAN, i see the history named as "Ocean.1" etc. Is the keyword Ocean somehow telling ADEXL to be in OCEAN mode?

I did find one hack. When i open the data.sdb file, i see tool set to OCEAN, if i manually edit it to be ADE, i can revert it, but i lose my design variables in the process.

 

So simply put, how should i switch the tool from OCEAN to ADE from within the GUI? Seems like a very simple question but i poured over all the manuals and could not find an answer anywhere :-(

Parents

  • My guess is that you ran the OCEAN XL script, and then opened the adexl view in ADE XL, and rather than doing RMB->View Results from the newly created history, you did RMB->Load Setup to Active. If you do that, it takes whatever setup was in place that generated those results, and replaces the active setup in ADE with this.

    Since it was an OCEAN script, it makes the resulting test an "OCEAN test" (search in cdnshelp for "OCEAN test editor" (in quotes) and you'll find some info on this).

    As an OCEAN script is more general than an ADE test setup, I think it's really a one-way operation - I don't think there's any way to go back (other than SKILL or SDB hacking).

    I did see that there was an SR which might be from you - 42652960 - which seems related. I was going to suggest logging a service request to ask for an interactive way to change this back (if possible). However, it may just be a consequence of using the wrong menu above to observe the results - I have seen other users using "Load setup to active" when they should have used "View Results", not realising the impact of the choice.

    Regards,

    Andrew.

Reply

  • My guess is that you ran the OCEAN XL script, and then opened the adexl view in ADE XL, and rather than doing RMB->View Results from the newly created history, you did RMB->Load Setup to Active. If you do that, it takes whatever setup was in place that generated those results, and replaces the active setup in ADE with this.

    Since it was an OCEAN script, it makes the resulting test an "OCEAN test" (search in cdnshelp for "OCEAN test editor" (in quotes) and you'll find some info on this).

    As an OCEAN script is more general than an ADE test setup, I think it's really a one-way operation - I don't think there's any way to go back (other than SKILL or SDB hacking).

    I did see that there was an SR which might be from you - 42652960 - which seems related. I was going to suggest logging a service request to ask for an interactive way to change this back (if possible). However, it may just be a consequence of using the wrong menu above to observe the results - I have seen other users using "Load setup to active" when they should have used "View Results", not realising the impact of the choice.

    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.