• 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. is dbReplacePropList not recommended for pcell? (in docu...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 5370
  • 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

is dbReplacePropList not recommended for pcell? (in docu')

Adrian Nistor
Adrian Nistor over 13 years ago

 Hello,

My purpose is (when dealing with abuttment function) to set more parameters on a instance. In order to avoid the pcell to be evaluated after each parameter is changed, something like the "Edit parameters" form was needed in order to provide the list of changes, and then , somehow, apply all changes once. 

dbReplacePropList looked perfect for this purpose, BUT in documentation it sais:

Replaces a list of properties of a given object with the specified list of properties. This function should not be used to replace properties of a pcell instance because the pcell parameters will not be evaluated by this function.

It's not clear at all for me what this information is about. After testing the function... it seems to work. But ... is it ok to use it? or not?

 

 

Thank you,

Best Regards,

Adrian

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

    Adrian,

    There have been a number of CCRs on this, and solution 11017546 covers this. I believe the behaviour is a bit different in more recent versions, but I do know there is a fix planned for IC616. The trick I always used in the past was to use dbReplacePropList and then use a single dbReplaceProp to force re-evaluation. I think the trouble in IC615 (for example) was that dbReplacePropList was causing multiple pcell evaluations rather than just one at the end - but I've not re-checked to be sure.

    Regards,

    Andrew.

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

    Adrian,

    There have been a number of CCRs on this, and solution 11017546 covers this. I believe the behaviour is a bit different in more recent versions, but I do know there is a fix planned for IC616. The trick I always used in the past was to use dbReplacePropList and then use a single dbReplaceProp to force re-evaluation. I think the trouble in IC615 (for example) was that dbReplacePropList was causing multiple pcell evaluations rather than just one at the end - but I've not re-checked to be sure.

    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