Stats

  • Locked Locked
  • Replies 9
  • Subscribers 142
  • Views 20375
  • 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

Changing cellName in a code

archive

Hi , I want to change the cellName of an instance "i2_09" to "i3_09" in a code. But im not able to set it using car(geGetSelSet())~>cellName="i3_09" or dbSet as this attribute is not valid for set. So Im using dbCreateInst to create "i3_09". Is there any other way to change the cellName without using "dbCreate*"


Originally posted in cdnusers.org by rimser9
Parents

  • If the property is called (say) "w", then you can do instId~>w=value . Note that the value needs to be the correct type - if your pcell is expecting a string, make it a string and so on. dbReplaceProp() should work too. The chances are you either supplied the wrong type, or you got the parameter name wrong.

    You can find the parameter names by doing:

    instId~>master~>superMaster~>parameters~>value~>name

    instId could be car(geGetSelSet()) if you have the instance selected.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
Reply

  • If the property is called (say) "w", then you can do instId~>w=value . Note that the value needs to be the correct type - if your pcell is expecting a string, make it a string and so on. dbReplaceProp() should work too. The chances are you either supplied the wrong type, or you got the parameter name wrong.

    You can find the parameter names by doing:

    instId~>master~>superMaster~>parameters~>value~>name

    instId could be car(geGetSelSet()) if you have the instance selected.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
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.