• 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. Measuring Layout Geometry

Stats

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

Measuring Layout Geometry

rafaelon
rafaelon over 8 years ago

Hello friends from Cadence,

I have a layout with 1M transistors. I would like to obtain some information from it.

For example, the width and length of a specific interconnection.

I don't want to use the ruler. How could I do it using Skill language or other way?

Thanks,

Rafael

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Rafael,

    This doesn't make any sense to me (and I don't think there's anything built-in to do this, because it seems a strange thing to want to do - I can't see what use this has). The table format you describe would be a bit odd, because all branches are on the VDD net - so wouldn't it just list VDD for all segments? Also, what do you mean by a "branch" - you could have a main VDD trunk (with bends in it) with branches coming off that trunk (which might have bends in them) and then twigs coming off each of those branches. What do you consider to be a branch? Any time the track changes direction? It's rather hard to determine what you really want here - maybe a picture would help? Why do you need this information anyway?

    Not that I can necessarily write this for you - but I might be able to steer you in the right direction to write it yourself, assuming that there is some way of distinguishing what you mean by a branch.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Rafael,

    This doesn't make any sense to me (and I don't think there's anything built-in to do this, because it seems a strange thing to want to do - I can't see what use this has). The table format you describe would be a bit odd, because all branches are on the VDD net - so wouldn't it just list VDD for all segments? Also, what do you mean by a "branch" - you could have a main VDD trunk (with bends in it) with branches coming off that trunk (which might have bends in them) and then twigs coming off each of those branches. What do you consider to be a branch? Any time the track changes direction? It's rather hard to determine what you really want here - maybe a picture would help? Why do you need this information anyway?

    Not that I can necessarily write this for you - but I might be able to steer you in the right direction to write it yourself, assuming that there is some way of distinguishing what you mean by a branch.

    Regards,

    Andrew.

    • 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