• 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. ocean run() recreates netlist

Stats

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

ocean run() recreates netlist

kkdesbois
kkdesbois over 1 year ago

Hello,

When using the ocean command run() after generating and manually modifyng the netlist, I observe that the netlist is recreated.
Is there a way to only run a simulation and not netlist&run?

Laurent.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    Laurent,

    If you use design("/path/to/netlist/netlist") then the core design won't get re-netlisted. The input.scs does get regenerated (because it includes design variables, model references, analyses which are dependent upon what you've done in OCEAN), but if you edit the netlist file, it won't get recreated.

    Even if you use design(lib cell view) then it wouldn't normally recreate it unless something changed (as far as I know), but to be sure, using the design(pathToNetlist) form should avoid the problem.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kkdesbois
    kkdesbois over 1 year ago in reply to Andrew Beckett

    Hello Andrew,
    Thanks you for the answer.

    Actually, my description was wrong : the file I modify manually is input.scs and not netlist.
    So it makes sense that it is recreated by run().

    If I do my modifications inside netlist, they are included in the final simulation, even if I don't use design("/path/to/netlist/netlist") befor run()

    Sorry for the inconvenience.

    Laurent.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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