Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 14284
  • 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

how to run Corner analysis over parametric analysis

archive

Hi, there:
    I try to run Corner analysis over parameter analysis like this

loadPcf("xxxxx.pcf")
parameterAnalysis("id" ?values '(90u 100u 110u))
cornerRun()    
cornerMeas()

but the results have no parameter result. only corner simulation result.

How to do a corner analysis over parameter analysis?


Thanks


Originally posted in cdnusers.org by julian2007
  • archive

    Hi, I try to overcome this but ....

    I think I have done something dumb as shown below
    foreach(device '("tt" "ss" "ff")
    foreach(element '("typ" "min" "max")
    modelFile(
    '("/xx/xx/1.scs" sprintf(nil "%s" device))
    '("/xx/xx/2.scs" sprintf(nil "%s" element))
    )
    paramAnalysis("id" ?values '(90u 100u 110u)
    paramAnalysis("vd" ?values '(1.62u 1.8u)))
    paramRun()
    )
    )

    which does not work, seems that foreach statement can not be nested and the sprintf can not give the model file a right section definition.

    Can someone give me some tested script to do all that job? It is such a tedious work to manually write down several hundreds corners definition in a pcf file.

    Thanks


    Originally posted in cdnusers.org by julian2007
  • archive

    hi, any ideas?


    Originally posted in cdnusers.org by julian2007
  • archive

    Nesting foreach isn't a problem. The problem is that you have quoted lists in the call to modelFile, and so these won't get evaluated.

    Your call to modelFile should be:

      modelFile(
        list("/xx/xx/1.scs" device)
        list("/xx/xx/2.scs" element)
      )
    There was no need to have the sprintf's in there - you can pass the variables directly. Quoted lists don't evaluate anything within the '(...), whereas the list() function evaluates all its arguments before creating the list.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett

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.