Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 14245
  • 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

Oceanscript fails to carry on once a simulation bombs

uzzy
Hello, I use oceanscripting to run my PVT sims in Cadence. However, while running the oceanscript, I have observed that if the simulation fails( due to some convergence issues) during one of the conditions in the script and the evaluated result returns "nil", printf/fprintf functions cannot handle "nil" data and thereby the script bombs and the rest of the conditions in the oceanscript do not get simulated. I would like to know if there is a workaround for this problem. Is there a way I could print the "nil" result as 0.0 in my result file and make the oceanscript carry on with the rest of the simulation conditions. Regards, Uzzy
Parents

  •  Uzzy,

    I tend to use things like:

    when(member('tran results())
      ; do the stuff that depends upon the transient having run
    )

    If the tran didn't run because of a problem (you could use a similar approach for other analyses), there will be no results in the simulation result database - so checking for it is an easy way of catching gross failure.

    Alternatively, using the approach proposed by Quek (the unless bit) is a good idea. I'm less keen on the %L approach - it's less flexible in how it can be formatted, and it doesn't help if you tried doing:

    outData=v("/out" ?result 'tran)
    double=outData*2

    in this case the double calculation will fail if the tran results are not present, because it will try to do nil*2.

    Regards,

    Andrew.

Reply

  •  Uzzy,

    I tend to use things like:

    when(member('tran results())
      ; do the stuff that depends upon the transient having run
    )

    If the tran didn't run because of a problem (you could use a similar approach for other analyses), there will be no results in the simulation result database - so checking for it is an easy way of catching gross failure.

    Alternatively, using the approach proposed by Quek (the unless bit) is a good idea. I'm less keen on the %L approach - it's less flexible in how it can be formatted, and it doesn't help if you tried doing:

    outData=v("/out" ?result 'tran)
    double=outData*2

    in this case the double calculation will fail if the tran results are not present, because it will try to do nil*2.

    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.