Stats

  • Locked Locked
  • Replies 19
  • Subscribers 143
  • Views 25447
  • 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

Deleting Schematic instance and instantiating another device on the same origin

archive

Dear All,

I am looking to do the following thing using SKILL

1. Open a schematic and look for a specific instance.

2. Delete the instance.

3. Instantiate another cell at the same origin (Both the symbols match in pin locations.)

 

I am not able to identify, how I can get the origin of the original instance before deleting it. Any kind of help is much appreciated.

 

Please help!

 

Thanks,

Vijay

Parents

  •  Vijay,

    Try using the code that Lawrence pointed you to (this was written by me, BTW), and use the ?order argument to specify the parameters you are changing. With many PDKs specifying just a single parameter is sufficient because all the callbacks are essentially the same.

    So you could do:

    CCSinvokeInstCdfCallbacks(instId ?order list("w"))

    to just invoke the "w" callback on the instance. The default behaviour is to call it for every parameter - sometimes this can be rather expensive if the callbacks are long, and if the callbacks are really common to all parameters, you're just repeating the same computation over and over again.

    Trying to interact with a form as you are doing in your code will be much harder, because something maybe blocking (I really wouldn't go down that route as it can get messy quickly).

    Regards,

    Andrew.

     

Reply

  •  Vijay,

    Try using the code that Lawrence pointed you to (this was written by me, BTW), and use the ?order argument to specify the parameters you are changing. With many PDKs specifying just a single parameter is sufficient because all the callbacks are essentially the same.

    So you could do:

    CCSinvokeInstCdfCallbacks(instId ?order list("w"))

    to just invoke the "w" callback on the instance. The default behaviour is to call it for every parameter - sometimes this can be rather expensive if the callbacks are long, and if the callbacks are really common to all parameters, you're just repeating the same computation over and over again.

    Trying to interact with a form as you are doing in your code will be much harder, because something maybe blocking (I really wouldn't go down that route as it can get messy quickly).

    Regards,

    Andrew.

     

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.