Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 17366
  • 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 use a design variable inside value()?

yayla

 Hi everyone,

 I want to use one of the design variable inside value() for histogram bin but I couldn't achieve. I have looked ocean and skill references and this is my final point:

 desVar("fin" 1G)

 value(db(v("/out" ?result "pss_fd") (evalstring(desVar("fin"))/8*3) ?histoDisplay nil ?noOfHistoBins 1)

 

but I couldn't get any. When I changed evalstring() part to a number, it works. Do you know how I can solve this problem?

 

Thanks,

yayla

 

  •  Hi,

     I still have the problem above. I am wondering whether there is anyone who can help.

     

    Thanks,

    yayla

  • You probably should use VAR("fin") or pv("top-level" "fin" ?result 'designParamVals) to get the value from the simulation results.

    Andrew.

  •  Hi Andrew,

     Thanks for your reply. "fin" is one of my design variable that I changin in in parametric analysis. Hence, is it enough to define "fin" VAR("fin") or should I also define it inside desVar()?

    Thanks,

     yayla

  • Yayla,

    You will still need to define the variable using desVar(), and then vary it using paramAnalysis(). The VAR() will pick up the value used in the simulation itself. Put another way, the desVar() defines the variable before the simulation is run, and the VAR() function refers to the value from the simulation itself.

    If doing a parametric sweep, you may then find that VAR() is returning a waveform - depending on the version you have, this might cause a problem when used as the interpolation value of the value() function - but try it and see. I think that was fixed some time ago (there's a workaround using famMap() if it doesn't).

    Andrew.

  •  Andrew,

     I really appreciate your help. I will try as soon as possible.

    Thanks,

     yayla

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.