• 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. $finish_current_analysis in verilogA

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 10038
  • 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

$finish_current_analysis in verilogA

Svilen64
Svilen64 over 4 years ago

Hi,

I am using a verilogA block in my simulation and it includes the statement $finish_current_analysis to stop the simulation when the event I am interested in happens. It works correctly if I simulate a single run in the Explorer. However, if I try to run Monte-Carlo simulations (still from within the Explorer) it seems the simulations don't stop. All MC runs are listed as "running" in the results window of the Explorer. Interestingly, if I open the spectre.log file for any of the MC runs I can see there that the simulations have actually finished at the time the event has happened. Bottom line, since the MC runs don't really quit I can't get my expression results and the statistics for that.
Maybe I am missing something about the use of that $finish statement in the context of MC simulations. Suggestions are welcome.

Thanks

Svilen

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    Svilen,

    I can imagine that it might move into the next Monte Carlo iteration, but I would expect that it works OK beyond that - so I wouldn't expect the Monte Carlo to stop. I don't have time today to test this out by putting together a test case - the best thing would be to contact customer support, as maybe there's a bug here...

    Andrew

    • Cancel
    • Vote Up +1 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