Stats

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

  • Reinice,

    Unfortnately the code was not designed to cope with symbol pcells (which is what symbol_xform views are) - when loading the mapping file, it looks up various pieces of information in the source and destination symbols to work out the mapping; with symbol pcells it would have to do this per variant - and right now it doesn't do that (and would be a reasonably big change to do so).

    The reason why symbol_xform is a pcell is in order to emulate the "mag" attribute that used to exist in the CDB database in IC5141; this allowed you to scale an instance by a magnification factor. OpenAccess does not support this, so it was emulated by creating a wrapper pcell which had a parameter "mag" to effectively do the same thing.

    Given that I don't really have time at the moment to update the SKILL code to  support symbol pcells (I'd need to put together enough test data to try it out too), maybe you can do a search and replace and change your source schematic to use symbol instead of symbol_xform? Problem could be that if the mag factor has been set to something other than 1.0, it might mess up the schematic.

    I did have a look at the code, and have some ideas how to fix it to support symbol_xform views, but it needs more thought (as well as the work to modify the code) - and unfortunately I'm unlikely to have the time in the next few days due to work commitments.

    Regards,

    Andrew.

Reply

  • Reinice,

    Unfortnately the code was not designed to cope with symbol pcells (which is what symbol_xform views are) - when loading the mapping file, it looks up various pieces of information in the source and destination symbols to work out the mapping; with symbol pcells it would have to do this per variant - and right now it doesn't do that (and would be a reasonably big change to do so).

    The reason why symbol_xform is a pcell is in order to emulate the "mag" attribute that used to exist in the CDB database in IC5141; this allowed you to scale an instance by a magnification factor. OpenAccess does not support this, so it was emulated by creating a wrapper pcell which had a parameter "mag" to effectively do the same thing.

    Given that I don't really have time at the moment to update the SKILL code to  support symbol pcells (I'd need to put together enough test data to try it out too), maybe you can do a search and replace and change your source schematic to use symbol instead of symbol_xform? Problem could be that if the mag factor has been set to something other than 1.0, it might mess up the schematic.

    I did have a look at the code, and have some ideas how to fix it to support symbol_xform views, but it needs more thought (as well as the work to modify the code) - and unfortunately I'm unlikely to have the time in the next few days due to work commitments.

    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.