Stats

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

to check spacing between the CPO layer in each Poly layer

Shivangi Chauhan

Hi ,

I want to check the spacing between the cpo layer in each poly in 16nm and when I am using dbGetNeighbour command it is taking the other poly's CPO if it is closest to that  cpo. can anyone help me with the skill command or code for the same.I have attached the image for the same.

Thank you

  • 'dbGetNeighbor' returns a list containing information about the closest neighboring shape in the specified direction of the given layer-purpose pair. Shapes that overlap the searching box are ignored. The related (to CPO) poly will overlap (by definition of it's function). There is no true CPO-Poly spacing in this context. It's not clear what you are trying to achieve.

  • in reply to RobMan

    I want to write a script if poly is routing more than specific height then it will flag error in 16nm  as the poly is continuous in 16nm tech , So for that I am taking reference of CPO layer if the spacing between the CPO layer is more than the specified value we can say poly is routing greater than specified value for each poly.

  • in reply to Shivangi Chauhan

    You might be better analysing the poly shapes. Use...

      leLayerAndNot(cv list("poly" drawing") list("CPO" "drawing") list("y0! "drawing")

    and...

      leSizeShape( shape '(0 0 shrinkVal shrinkVal))

    N.B. The shrinkVal will be 0.5 x maxLength.

    There is obviously more to it than that. And not sure what you expect to manage hierarchical shapes. It's likely to get complicated. Probably best to create a Pegasus (or PVS) DRC rule.

  • in reply to RobMan

    okay, Thank you for this reply!!

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.