• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Difference parameter and iPar

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 17288
  • 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

Difference parameter and iPar

Clidre
Clidre over 9 years ago

Hello,

I have a question about iPar.

What is the difference between using a parameter and using iPar? Example: In a Mosfet instance, I put

Length=Ln   

Width=2*iPar("Ln")

 

So I need to put the parameter Ln and then I use iPar to refer to that parameter. But I can also put

Length=Ln   

Width=2*Ln

 

And it works the same. Thus I don't understand the usefulness of iPar and the difference between the 2 examples above.

 

Thanks!

  • Cancel
  • skillUser
    skillUser over 9 years ago

    Hi,

    The iPar() statement obtains the value of the instance parameter from that same instance, and this should work whether the parameter is a fixed number or a design variable or even another expression to be evaluated.  In the second case it looks like you either have a global variable or a design variable "Ln" which is being used in both instance parameters.  I think that the first case is the most flexible.

    I'm sure that Andrew might also be able to offer more insight, but in my opinion the first method, using iPar(), is the way to go.

    Hope this helps,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information