Stats

  • State Not Answered
  • Locked Locked
  • Replies 2
  • Subscribers 9
  • Views 2700
  • 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

Pcell Designer Geo Query land is identifying para shapes

EMaz

Hello,

I am seeing unexpected results with the land Geo Query operator. It is recognizing layers that are defined in the para group as if they are actually present in the pcell. 

elements involved = 1 group, 1 layer, 1 para instance

1) Group: gRouteSigNorth contains metals and vias - see pic - it does not contain MET1

2) Layer: MET1 which can be seen in blue in the picture above. MET1 and is part of a group called gTile, (the donut shapes) and the dut in the center (2 small blocks)

3) para instances: I have several groups which are defined in the para group which also contain MET1. In the para group they are defined in quadrant 1 with origin at 0:0

Question: When I select layer MET1, why is the MET from the para shape highlighted? The red outline below shows the MET1 identified from para instances.

The resulting land gives me two shapes... would like to only have the shape on the top. 

Thank you!

  • 0

    This is (for better or worse - I sometimes wish that we'd changed it in the past, but there's too much risk of it breaking PCells that depend upon the behaviour) the default behaviour of the layer Geo Query when used at the leaf level. In the documentation for the operator, it says:

    The body of the geo operator, otherwise all shapes in all levels of hierarchy, including para shapes.

    If you want to omit the para shapes, you could put the shapes operator inside the layer operator. The will restrict it to just the shapes in the current cellView and omit the para shapes. Note, the shapes operator doesn't include shapes down through the hierarchy, if you wanted the first part of the layer operator's behaviour (i.e. all levels of hierarchy), then you could do:

    layer ("MET1" "drawing")
    -- hierarchy (0 32)
    ---- shapes

    Hope that's clear (let me know if it's not!). This comes up rather often, so I'll get a note added to the layer operator to include these approaches.

    Andrew

  • 0 in reply to Andrew Beckett

    Thanks Andrew 

    Much appreciated.

    Erika

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.