Stats

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

Most efficient db function to move all shapes in a design?

jaleco

Working in ic5141, what is the most efficient way to move all shapes in a design using the db functions?

I'm dealing with millions of shapes and would like to use a function like Move Origin, but this is not a db function.

Is it more efficient to create a figure group, add each shape to the group and move the group, or to select and move each shape?

Neither seem like good options for a list of millions of shapes.

Parents

  • Hi,

    Here's another idea to try: create the new cellview yourself (dbOpenCellViewByType()) and then either move the figures (dbMoveFig()) or copy them (dbCopyFig()) with the appropriate transform (if any) so that they end up at the right place in the new cellview.  Another thing to try is to reduce the sets of shapes into batches, e.g. call geSelectFig() multiple times, or select/identify the shapes another way (for example, based on the layer-purpose pair that they are on?) - sometimes the selection operation alone can take a long time if dealing with lots of shapes, and with SKILL you don't necessarily need to 'select' them, just obtain their dbId's. I would expect the lower-level functions (e.g. "db" prefix rather than "le" prefix) to be faster and/or more efficient than the higher level functions.

    Hopefully this might help you?

    Regards,

    Lawrence.

Reply

  • Hi,

    Here's another idea to try: create the new cellview yourself (dbOpenCellViewByType()) and then either move the figures (dbMoveFig()) or copy them (dbCopyFig()) with the appropriate transform (if any) so that they end up at the right place in the new cellview.  Another thing to try is to reduce the sets of shapes into batches, e.g. call geSelectFig() multiple times, or select/identify the shapes another way (for example, based on the layer-purpose pair that they are on?) - sometimes the selection operation alone can take a long time if dealing with lots of shapes, and with SKILL you don't necessarily need to 'select' them, just obtain their dbId's. I would expect the lower-level functions (e.g. "db" prefix rather than "le" prefix) to be faster and/or more efficient than the higher level functions.

    Hopefully this might help you?

    Regards,

    Lawrence.

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.