• 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 SKILL
  3. ocean run corner on the termination of an error is encountered...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 14448
  • 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 corner on the termination of an error is encountered!!!!

xianweng
xianweng over 13 years ago

hello,

Run with the ocean corner, write the results in txt, the error is encountered in some corner on the next stop, and how to display an error and then continue to run forever? Just use soon, thank you advice 

for example:

if I want to seek GB, GAIN
PM = phaseMargin (VF ("/ V"))
GB = gainProd (VF ("/ V"))
GAIN = value(dB20(VF("/V")) 1)
if(PM&&GB&&GAIN fprintf(p, "%f %f %f \n"  PM GB GAIN) fprintf(p, "%s\n" "error"))
It is an error "Gain dose not cross one" when i run ocean,then  the simulation stops, but when I comment GB GAIN ,It is still an error "Gain dose not cross one", but the simulation can continue

How to make the simulation continue with errors

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 13 years ago
    It's probably due to something failing in your fprintf after the run() command. Most likely, the results are not present, and so any results access you're doing is returning nil, resulting in an error in either a calculation or in the expected type in the arguments to printf.

    I normally recommend using constructs like:

    when(member('dcOp results())
    ; do calculations and fprintf
    )

    The first argument to member might be 'tran or whatever analysis you're trying to get the results from - see what they're called by calling results() in a successful run.

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 13 years ago
    It's probably due to something failing in your fprintf after the run() command. Most likely, the results are not present, and so any results access you're doing is returning nil, resulting in an error in either a calculation or in the expected type in the arguments to printf.

    I normally recommend using constructs like:

    when(member('dcOp results())
    ; do calculations and fprintf
    )

    The first argument to member might be 'tran or whatever analysis you're trying to get the results from - see what they're called by calling results() in a successful run.

    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