• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Execution of ocean script in Cadence IC 6.1.5 and Cadence...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 14286
  • 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

Execution of ocean script in Cadence IC 6.1.5 and Cadence IC 5.1.41

Lings
Lings over 11 years ago

 Hello,

I started to work recently on the new Cadence IC 6.1.5 moving from IC 5.1.4. I use Ocean Scripts and noticed that the ocean script takes a longer time to execute in the new version than in the old one. To verify this, I took a simple inverter circuit and performed the DC simulation analysis using Ocean script. I looped it 10 times for analysis purpose and measured the execution time. Executing the script in old version IC 5.1.41 produced a time of 130 sec while executing the same script in new version IC 6.1.5 produced a time of 502 sec. 

Could anyone let me know the possible rootcause of this issue and possible solutions for it?

Thanks,

Lings

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    So is the python script running "ocean" each time? Or running virtuoso? What is it doing?

    Might it be the overhead of starting ocean each time that is the issue rather than the time to actally run the script? Perhaps you can add a:

    printf("START: %s\n" getCurrentTime())

    at the beginning and similar at the end (put END instead of START) - that way you can compare the time taken for the script itself. Also compare the simulation logs to see if the simulator itself is taking a different amount of time (not sure if it's the same version of spectre you're using).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    So is the python script running "ocean" each time? Or running virtuoso? What is it doing?

    Might it be the overhead of starting ocean each time that is the issue rather than the time to actally run the script? Perhaps you can add a:

    printf("START: %s\n" getCurrentTime())

    at the beginning and similar at the end (put END instead of START) - that way you can compare the time taken for the script itself. Also compare the simulation logs to see if the simulator itself is taking a different amount of time (not sure if it's the same version of spectre you're using).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information