• 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. I am not able to change multiplier value

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 10016
  • 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

I am not able to change multiplier value

Purbayan
Purbayan over 3 years ago

I am using this skill code

where NPNid is the object id of the npn

cdf = cdfGetInstCDF(NPNid)
FinalValue= nth(0 cdf~>parameters)->value="NPN_PAR"
Multipliervalue= nth(14 cdf->parameters)->value=" 1 "

The problem is that when i run the command Multipliervalue= nth(14 cdf->parameters)->value=" 1 " from CIW the cdf value gets changed but when i run the same line in skill code it doesn't change the value from "".

  • Cancel
Parents
  • Purbayan
    Purbayan over 3 years ago

    Looks like i was able to fix it just restarting cadence.

    But can anyone let me know why it happens. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Purbayan
    Purbayan over 3 years ago

    Looks like i was able to fix it just restarting cadence.

    But can anyone let me know why it happens. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to Purbayan

    First of all, you should never change the values using the nth() element in the parameters list. That's a really bad idea as a) it's not very efficient and b) I wouldn't ever want to rely on the order of the parameters list. Use cdfFindParamByName() instead.

    That said, I can't see why this would have failed in a way that restarting Virtuoso would help. CDF is pretty robust and so it seems extremely unlikely to me that it would be the instance CDF that misbehaves in a way that requires a restart - I've never seen that happen. More likely would be some aspect of your code - maybe a variable that was not declared locally and so was set to something other than what you thought it was; it might not be that, but that's far more likely than some CDF mess up.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Purbayan
    Purbayan over 3 years ago in reply to Andrew Beckett

    Thank you Andrew for the response.

    cdfFindParamByName(), I didn't knew that it existed. I would definitely implement it in my code and also thank you for those suggestions.

    Yours

    Purbayan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to Purbayan

    You can also use:

    cdf~>model~>value="blah"
    cdf~>m~>value="1"

    (assuming the parameters are called model and m, that is). The cdfFindParamByName is particularly useful if you need to look up a parameter where the name is in a variable or it happens to clash with a reserved slot name on the CDF object (for example, if you had a parameter called "id").

    Andrew

    • 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