Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 14455
  • 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

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

Parents
  • Yes, that's right. Put another way, it's not the failure of the simulation that causes the SKILL code to stop, but a lack of error detection and an assumption that a valid result is available.

    When coding, it's always wise to put in sufficient error checking - and the when() is just a simple way of checking it.

    Strictly speaking, you might need more thorough error checking - for example, if you were using, say, cross() to find the time when a signal crossed a threshold, and in a particular corner it didn't, then cross would return nil. If the code that processes the result of the cross function doesn't have something to specifically handle this unexpected value, that could also cause it to fail.

    You could also be lazy and do:

    run()
    errset(
    {
    ; your calculations and fprintf statements
    }
    t
    ) ; errset

    The errset will trap any errors in the body - and stop it from halting - but it is not very elegant. The "t" as the second argument is there to ensure it prints out the error message.

    Regards,

    Andrew
Reply
  • Yes, that's right. Put another way, it's not the failure of the simulation that causes the SKILL code to stop, but a lack of error detection and an assumption that a valid result is available.

    When coding, it's always wise to put in sufficient error checking - and the when() is just a simple way of checking it.

    Strictly speaking, you might need more thorough error checking - for example, if you were using, say, cross() to find the time when a signal crossed a threshold, and in a particular corner it didn't, then cross would return nil. If the code that processes the result of the cross function doesn't have something to specifically handle this unexpected value, that could also cause it to fail.

    You could also be lazy and do:

    run()
    errset(
    {
    ; your calculations and fprintf statements
    }
    t
    ) ; errset

    The errset will trap any errors in the body - and stop it from halting - but it is not very elegant. The "t" as the second argument is there to ensure it prints out the error message.

    Regards,

    Andrew
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.