• 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 Design
  3. comparission of two GDS

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 128
  • Views 18132
  • 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

comparission of two GDS

sailesh
sailesh over 15 years ago

 Hi Frn'z

       u can get me the logic for this,

I  have two layout, they has to be compared and difference has to be given. I have done till getting the shapes and their corresponding metal layers & coordinates.Iam not able move further

 

 

 

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

    Can you please try to write using proper English words? There's no tax on characters in the forum, and using SMS abbreviations is unnecessary. "Frn'z" and "u" make it harder to read. This comment is aimed not just at you, but all people who use the forum - some of us find it really hard to read such strange abbreviations.

    Anyway, the conventional way to do this kind of comparison is to do an XOR (Exclusive OR) in a physical verfication tool, such as Assura, PVS or Calibre. Writing the rule deck is generally pretty easy for these tools - consult the documentation.

    It will almost certainly be much easier to write the rules, and faster to run, than trying to write some SKILL to do it. You could use functions like leLayerXor() or dbLayerXor() in SKILL, but I think using a physical verification tool is by far the most efficient.

    Regards,

    Andrew.

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

    Can you please try to write using proper English words? There's no tax on characters in the forum, and using SMS abbreviations is unnecessary. "Frn'z" and "u" make it harder to read. This comment is aimed not just at you, but all people who use the forum - some of us find it really hard to read such strange abbreviations.

    Anyway, the conventional way to do this kind of comparison is to do an XOR (Exclusive OR) in a physical verfication tool, such as Assura, PVS or Calibre. Writing the rule deck is generally pretty easy for these tools - consult the documentation.

    It will almost certainly be much easier to write the rules, and faster to run, than trying to write some SKILL to do it. You could use functions like leLayerXor() or dbLayerXor() in SKILL, but I think using a physical verification tool is by far the most efficient.

    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