• 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. extract connectivity using skill

Stats

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

extract connectivity using skill

posh
posh over 15 years ago

Hi all,

I am a new Skill User, iam trying to write a code for extracting a net from one cellview and put it into a different cellview (only the extracted net). i have read some previous threads but most of them were pointed to VXL. i do not have a VXL licence. so can anyone hint me how to extract a net using skill in VLE.

 

thanks

Harish Poshala 

 

  • Cancel
Parents
  • skillUser
    skillUser over 15 years ago

     Hi Harish,

    I will add to what Derek and Andrew have said by providing an outline of how I would approach this in SKILL code:

    1. Get a starting point (xy provided perhaps by enterPoint() or
      enterPoints()) or starting shape from the user
    2. Obtain the object at the starting point (use gePointToFig()
      or dbGetOverlaps() with a depth of 0 for this)
    3. Check that the object is on a routing layer
    4. Add this object to the list of connected shapes
    5. Use dbGetTrueOverlaps() to find objects overlapping this
      shapes' bounding box (decide the hierarchy depth you wish to
      use)
    6. Filter the objects to remove non-adjacent connectivity layers
      compared to the current object, also filter any shape that is
      already on the list of connected shapes
    7. Add these objects to the list of connected shapes
    8. Repeat from Step 5. (recursive?) to follow connected shapes

    The above is just an outline for finding the "connected" shapes in a similar fashion to the Mark Net feature. You may wish to add highlights to show what is being processed. The decision of whether something is connected will depend on the layers used, you may wish to use information from the Technology File (IC5141) or the viaDefs (IC61x) similar to how Mark Net works.

    I hope that this information is helpful to you.

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 15 years ago

     Hi Harish,

    I will add to what Derek and Andrew have said by providing an outline of how I would approach this in SKILL code:

    1. Get a starting point (xy provided perhaps by enterPoint() or
      enterPoints()) or starting shape from the user
    2. Obtain the object at the starting point (use gePointToFig()
      or dbGetOverlaps() with a depth of 0 for this)
    3. Check that the object is on a routing layer
    4. Add this object to the list of connected shapes
    5. Use dbGetTrueOverlaps() to find objects overlapping this
      shapes' bounding box (decide the hierarchy depth you wish to
      use)
    6. Filter the objects to remove non-adjacent connectivity layers
      compared to the current object, also filter any shape that is
      already on the list of connected shapes
    7. Add these objects to the list of connected shapes
    8. Repeat from Step 5. (recursive?) to follow connected shapes

    The above is just an outline for finding the "connected" shapes in a similar fashion to the Mark Net feature. You may wish to add highlights to show what is being processed. The decision of whether something is connected will depend on the layers used, you may wish to use information from the Technology File (IC5141) or the viaDefs (IC61x) similar to how Mark Net works.

    I hope that this information is helpful to you.

    Best regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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