• 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. SKILL Variable

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 145
  • Views 18706
  • 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

SKILL Variable

hrishikesh
hrishikesh over 12 years ago

I am new to Cadence SKILL. I am trying to understand a SKILL script file containing many procedures. Many of these procedures use a variable which holds a constant list. But it doesn't seem to be assigned anywhere in the script file. Can you suggest any possible place from where it could be assigned? Is there any way in SKILL to import variables from another file?

  • Cancel
Parents
  • mtwadeCU
    mtwadeCU over 12 years ago

    I'm having a similar problem, so I thought I'd add on to this thread. I have an existing library that I wanted to copy to a new library and change the reference libraries to the new library. I did this using the "copy wizard," and it seemed to work for the most part. However, I have SKILL scripts where I'm trying to create PCELLs in this new library, and I'm running into problems. 

     I am using an optional input parameter for my script called "dbDelta" which is set at the top of the script (before the "let" statement) using the following syntax: (dbDelta list(1.0 1.0))

     It was causing errors that it's never caused before, so I used the setguard() function mentioned above to see where this variable was being changed. The setguard() function told me:

    Variable dbDelta set to '('('('('((1.0 1.0)))))) in "(path of script I'm working with)" 

    It seems that the error is a result of copying the old library to a new library and using the "update instances" option in the "copy wizard". Nowhere in my script am I setting the value of dbDelta other than the top, and if I change the name of dbDelta to anything else, the problem goes away. Thoughts? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • mtwadeCU
    mtwadeCU over 12 years ago

    I'm having a similar problem, so I thought I'd add on to this thread. I have an existing library that I wanted to copy to a new library and change the reference libraries to the new library. I did this using the "copy wizard," and it seemed to work for the most part. However, I have SKILL scripts where I'm trying to create PCELLs in this new library, and I'm running into problems. 

     I am using an optional input parameter for my script called "dbDelta" which is set at the top of the script (before the "let" statement) using the following syntax: (dbDelta list(1.0 1.0))

     It was causing errors that it's never caused before, so I used the setguard() function mentioned above to see where this variable was being changed. The setguard() function told me:

    Variable dbDelta set to '('('('('((1.0 1.0)))))) in "(path of script I'm working with)" 

    It seems that the error is a result of copying the old library to a new library and using the "update instances" option in the "copy wizard". Nowhere in my script am I setting the value of dbDelta other than the top, and if I change the name of dbDelta to anything else, the problem goes away. Thoughts? 

    • 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