Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13612
  • 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

changing the location of netlist creation in loop

Suryansh Singh

Hello

Please refer to the link below:

https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/35371/creatnetlist-with-ocean-in-a-specific-directory,

I am trying to do a similar thing i.e. changing the location of netlist creation. I did set the "startup" env var before the simulator call but I have to run the createNetlist command multiple times and in different directories ( I am changing the directory as I want to change models and then simulate the netlist and do not want to overwrite). So, in that case, would it be a good idea to set this variable in every iteration?

Please guide me on this. 

Also, I notice that if I interrupt my skill script(Ctrl+C) before it completes itself (since I have a lot of cases and it takes time) and then if I rerun it after making suitable changes, I get the following error :

 *Error* (Default-reader-method) generic:asiGetName class:list

Could you help me understand the reason for this?

Regards

Suryansh Singh     

  • Andrew Beckett

    Hi Suryansh,

    Setting it in each iteration is fine, but you have to call the simulator() function after changing it because otherwise it won't have an effect, as I stated in the other link.

    I wouldn't expect the error to occur if re-initialising the OCEAN session by calling simulator() - most likely the control-C has left the session state in an incomplete status and it's confused, but I'd expect doing simulator('spectre) again would fix it because it is like closing and re-opening ADE (you could try calling ocnCloseSession() too).

    Regards,

    Andrew.

  • Suryansh Singh
    in reply to Andrew Beckett

    Hello Andrew,

    Thanks for the reply. And yes, if I do ocnCLoseSession() I don't see the error.


    Regards

    Suryansh Singh 

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.