• 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. how to re-evaluate the pcell submaster

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 16249
  • 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 re-evaluate the pcell submaster

phenixgj
phenixgj over 15 years ago

I use  IC613 and openaccess database. Is there any skill command to update/refresh the pcell submaster?

Thanks.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 15 years ago

     Derek,

    My guess was that the code was referencing some data outside of the parameters, which was changing.

    This is bad design of a pcell. It's OK to reference static data (e.g. info from the tech file), but referencing some data which may change during a session is not safe - all communication should be via the pcell parameters - as that will trigger pcell re-eval where necessary.

    Or maybe it's that the pcells are being developed and the code is being changed. If it was SKILL code, this is handled automatically - if you redefine the pcell, it triggers a re-eval of all variants - and in IC614 you can use the SKILL Development Environment to single step through your pcell code, reload it, and see the effect of changes. But I wouldn't know how to force any python code to get re-loaded.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 15 years ago

     Derek,

    My guess was that the code was referencing some data outside of the parameters, which was changing.

    This is bad design of a pcell. It's OK to reference static data (e.g. info from the tech file), but referencing some data which may change during a session is not safe - all communication should be via the pcell parameters - as that will trigger pcell re-eval where necessary.

    Or maybe it's that the pcells are being developed and the code is being changed. If it was SKILL code, this is handled automatically - if you redefine the pcell, it triggers a re-eval of all variants - and in IC614 you can use the SKILL Development Environment to single step through your pcell code, reload it, and see the effect of changes. But I wouldn't know how to force any python code to get re-loaded.

    Regards,

    Andrew.

    • 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