Stats

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

Create new PCell attributes or properties to hold a list of object identifiers

Dynamic Duo

Dear All,

I am trying to do the following with SKILL in IC6.1.5.500.12:
================================
Given: an object identifier of a schematic instance Inst0_sch = db: 0x15b7f112, where Inst0_sch is a MOSFET PCell

Obj: assign a list of object identifiers (from the same schematic) listA = list( db:0x15b7f345 db:0x15b7f456 db:0x15b7f678 ) to Inst0_sch as a new attribute or property: "impactNeighbors"
================================

I am thinking this would make query much easier, sort of to minic the reference/pointers in C/C++.
But haven't been able to get it work. Somehow I cannot make new attributes.. And in making a new property, I did not see supported valueType of l_objId?

Alternatively we can define a global list of lists: memlist_, to hold these "impactNeighbors", then assign the list index as a new property to Inst0_sch, e.g.,
dbSetq(Inst0_sch 32 "impactNeighbors"), where nth(32 memlist_) is listA..

But I'd strongly prefer the first way.. Could anyone give me some pointers?

Thanks a bunch!
Duo

Parents

  • Actually it's not wierd. Only certain object types are supported as property types - these are strings, integers, floats and lists (there are some other types which are represented as these - so "time" is a special string, for example). If it's an ILList type (i.e. a list), it can only be a list containing strings, integers, floats and lists. So you can't store a list containing a table, or a list containing a file port, or a list containing a database object. It probably ought to error out if you try to store a list containing other object types, but it doesn't for historical reasons (and quite possibly for performance reasons).

    If you are trying to create relationships between objects that you want to store in the database, you should use groups not properties (e.g. using dbCreateGroup). The benefit of these is that they allow ordered and unordered groups, and can tidy up after themselves when a member object is deleted, say.

    Regards,

    Andrew.

Reply

  • Actually it's not wierd. Only certain object types are supported as property types - these are strings, integers, floats and lists (there are some other types which are represented as these - so "time" is a special string, for example). If it's an ILList type (i.e. a list), it can only be a list containing strings, integers, floats and lists. So you can't store a list containing a table, or a list containing a file port, or a list containing a database object. It probably ought to error out if you try to store a list containing other object types, but it doesn't for historical reasons (and quite possibly for performance reasons).

    If you are trying to create relationships between objects that you want to store in the database, you should use groups not properties (e.g. using dbCreateGroup). The benefit of these is that they allow ordered and unordered groups, and can tidy up after themselves when a member object is deleted, say.

    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.