Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 2066
  • 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 script - parametric analysis

surreyian

Hello,

 i'm trying to use ocean to run parametric analysis. in the ocean reference guide,

 paramAnalysis("temp" ?values '(27)
   paramAnalysis("vddaval" ?values '(2.375 3.6)
    )
    )
tempAnalysis=paramAnalysis("temp" ?values '(27 125))
paramRun('tempAnalysis)

i can choose to  run only temp or vddaval, according to the ocean reference guide. 

When I run the ocean script using load "xxx.ocn" in CIW. The simulation complete without error, however there is no result. 

If i use both loops, I am able to get the result.

paramAnalysis("temp" ?values '(27)
   paramAnalysis("vddaval" ?values '(2.375 3.6)
    )
    )
paramRun()

I'm not sure what went wrong.

 

 

 

  • If you use the first example, it should run a parametric analysis over temperature. I tried it, and it works fine (the nested paramAnalysis is completely pointless, since only the "    paramAnalysis("vddaval" ?values '(2.375 3.6)" is used, but apart from that all is OK.

    Which version are you using (what does getVersion(t) return when you call it at the OCEAN prompt or in the CIW)? Are you using distributed processing, or normal local simulation runs?

    Andrew.

  •  Hello andrew,

     using "sub-version  IC6.1.5-64b.500.10 ", using distrubued processing.

     The simulation runs fine with the nested paramAnalysis (temp and vddaval), i am able to view the results after simulaiton. 

    However if I tried to run only temp in the nested paramAnalysis, the simulation completed with errors, but there is no results. 

  • OK, you've hit a specific problem that was introduced in ISR10, is there in ISR11, and has been fixed in ISR12 (due out on 13th July). If you didn't use distributed processing, it works fine. Note that this is not specific to OCEAN - it happens in ADE L too. For reference, the CCR number is 1023986.

    Andrew.

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.