• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Bringing shapes up from lower level cells

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 13599
  • 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

Bringing shapes up from lower level cells

Michael L
Michael L over 10 years ago

 I am trying to copy a specific set of layers in all lower level cells up to the current level of hierarchy.  My current code is as follows:

 

info = geGetWindowCellView()

bbox = info~>bBox

all_objects = leSearchHierarchy( info bbox 32 "any shape" nil )

epi_objects = nil

foreach( shape all_objects

   layername = substring( shape~>layerName 1 3 )

   if( layername == "EPI" then

      epi_objects = cons( dbCopyFig( shape info ) epi_objects )

   )

)
 

 

This doesn't work correctly.  It copies each EPI from the lower level cell relatve to it's origin, to the top level relative to it's origin.  That is, they are all shoved down and to the left...  I want the EPI objects to be placed "where they belong", over their hieractical positions. 

Can someone please tell me how to fix it?

  • Cancel
  • tweeks
    tweeks over 10 years ago

    There are multiple solutions.

    One of them is to use dbGetHierPathTransform() (assuming leSearchHierarchy() returns a hierarchical path like dbGetOverlaps() and friends), then dbConcatTransform() with dbTransformPoint(), dbTransformPointList(), or dbTransformBBox(), depending on what sort of shape it is.

    Another solution is to use the rod* functions, which can name the shapes and give you their transformed coordinates automatically.

    Yet another solution would be to copy the subcells and flatten the copies, deleting what you don't want. :)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • theopaone
    theopaone over 10 years ago

     dbCopyFig has a third argument, a transform. You can calculate the hierarchy transform and put it into the dbCopyFig call.

    Ted

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tweeks
    tweeks over 10 years ago
    I never noticed that!  That's quite handy.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information