• 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 SKILL
  3. Force increment step in parameter

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 15405
  • 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

Force increment step in parameter

Dimitris Kar
Dimitris Kar over 11 years ago

Hi,

 

I am trying to force the minimum increment in parameters that user defines.

 I managed to implement the min max to force the limits of my parameter (i.e. if 3<=x<=10, I write x=max(x 3)   x=min(x 10))

 I can not find the correct expresion on setting the acceptable step i.e. if the grid is 0.1, then values of x.xxx are not accepted.

 

An suggestions will be warmly welcomed!

 

Many thanks!

 

BR,

  • Cancel
Parents
  • Dimitris Kar
    Dimitris Kar over 11 years ago

     Hi !

     

    I have a new question, regarding the use of the parametrized value in the above code. 

     

    Say I need to "call" another input parameter, i.e. param2

    I will modify the procedure as follows: 

    ;o------------------------------------------------------------------------------------------o; 

    procedure(SR(param1 param2 upper grid)
      let((value dep dep1 libID cellID)
        libID="My_lib"
        cellID="My_PCELL"
        value=get(cdfgData param1)->value
      

        dep = car(setof(p cdfGetBaseCellCDF(ddGetObj(libID cellID))->parameters p->name==symbolToString(param2)))->value

       get(cdfgData param1)->value=round((value/float(grid)))*grid

    ;o------------------------------------------------------------------------------------------o;

     

     

    Although "primitive", the dep is getting my desired parameter. 

     

    My problem is the following: 

     

    I need a conditional statement, that will depend the lower/upper limit of param1 from the param2 input. 

    I tried  to use a

                value=      case( dep 

                                              (min(max(dep lower) x.xxx) value1)

                                              (min(max(dep yy.yyy) zz.zzz) value2))

     

    When trying to implement it, I get no results...

     

    Any syggestion how to implement it? 

     

    Thanks! 

     

    D.

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Dimitris Kar
    Dimitris Kar over 11 years ago

     Hi !

     

    I have a new question, regarding the use of the parametrized value in the above code. 

     

    Say I need to "call" another input parameter, i.e. param2

    I will modify the procedure as follows: 

    ;o------------------------------------------------------------------------------------------o; 

    procedure(SR(param1 param2 upper grid)
      let((value dep dep1 libID cellID)
        libID="My_lib"
        cellID="My_PCELL"
        value=get(cdfgData param1)->value
      

        dep = car(setof(p cdfGetBaseCellCDF(ddGetObj(libID cellID))->parameters p->name==symbolToString(param2)))->value

       get(cdfgData param1)->value=round((value/float(grid)))*grid

    ;o------------------------------------------------------------------------------------------o;

     

     

    Although "primitive", the dep is getting my desired parameter. 

     

    My problem is the following: 

     

    I need a conditional statement, that will depend the lower/upper limit of param1 from the param2 input. 

    I tried  to use a

                value=      case( dep 

                                              (min(max(dep lower) x.xxx) value1)

                                              (min(max(dep yy.yyy) zz.zzz) value2))

     

    When trying to implement it, I get no results...

     

    Any syggestion how to implement it? 

     

    Thanks! 

     

    D.

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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