Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 15640
  • 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

Copy adexl view without history

Clidre

Hello,

I would like to have 2 adexl views and I would like to create a copy of the first adexl view without the History. The reason is that I want to simulate at the same time with two different servers, so I need a adexl that is not locked while the other one is running.

If I just copy-paste the first adexl, I get the History (saved in server1), but this is annoying because from server 2 I cannot access that history. Therefore I would like to create a copy with all the settings, but the history of the copied adexl view should be empty.

Do you know a way to do it?

Thanks 

  • Andrew Beckett

    Rather than doing a copy in the library manager (assuming that’s what you meant, as there’s no “paste” involved), create a new empty adexl view and do File->Import to import the tests from the original view.

    Regards,

    Andrew

  • Clidre
    Thanks a lot, Andrew! Yes, I was referring to a copy in the Library Manager and there's no paste involved.
    Can you please clarify the difference between "Import" and "Load Setup state"? I tried the latter before reading your reply: I saved the setup state of the original ADEXL, created a new one and then I tried to Load the setup state, but I could not find anything saved...
  • Andrew Beckett

    Setup States are a mechanism to allow you to save some or all of the current setup into a named "state" within the adexl view. It allows you to keep several configurations of simulation setup, variables, etc within the view and restore them easily. This is useful if you are (say) using a bunch of parameterisation for optimisation, but don't want that enabled when you're doing sweeps and corners (for example).

    Since it saves within the view, it's not an export/import mechanism for importing to another view.

    Regards,

    Andrew.

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.