Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 15646
  • 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

emtpy space in cellview when fit zoom

psill000

What I have tried

procedure(updateBBox()
    foreach(lll getEditRep()~>lpps
        if(lll~>layerName=="changedLayer" then
            foreach(shape lll~>shapes dbDeleteObject(shape))
        )
    )
)

foreach( steiner geGetWindowCellView()~>steiners
   dbDeleteObject(steiner)
)

Drawing and other size shape then delete shape.

What other way can I use to minimize the cellview for the correct zoom fit

 Thanks

Parents
  • Andrew Beckett

    I did think about writing something a bit more dedicated, but one approach would be to use the code example given in this post.

    For example, you could do:

    cv=geGetEditCellView()
    abTreeExample(cv~>shapes)

    you could also then use:

    abTreeExample(cv~>instances)
    abTreeExample(cv~>vias)
    abTreeExample(cv~>mosaics)
    abTreeExample(cv~>areaBoundaries)

    and so on - other interesting attributes to look at might be figGroups, blockages, rows, markers, guides, routes, steiners.

    The code allows you to sort the objects on the lower left x or y, or upper right x or y - so you can find the extent of each type of object. 

    If I had more time I'd write something which just showed the bBox for each layer (say) and the bBox for each other kind of object, to give you more of a starting clue without necessarily showing every single object. But I don't, so I'll leave that as an exercise for the reader - or maybe the code above is sufficient for your needs.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    I did think about writing something a bit more dedicated, but one approach would be to use the code example given in this post.

    For example, you could do:

    cv=geGetEditCellView()
    abTreeExample(cv~>shapes)

    you could also then use:

    abTreeExample(cv~>instances)
    abTreeExample(cv~>vias)
    abTreeExample(cv~>mosaics)
    abTreeExample(cv~>areaBoundaries)

    and so on - other interesting attributes to look at might be figGroups, blockages, rows, markers, guides, routes, steiners.

    The code allows you to sort the objects on the lower left x or y, or upper right x or y - so you can find the extent of each type of object. 

    If I had more time I'd write something which just showed the bBox for each layer (say) and the bBox for each other kind of object, to give you more of a starting clue without necessarily showing every single object. But I don't, so I'll leave that as an exercise for the reader - or maybe the code above is sufficient for your needs.

    Regards,

    Andrew.

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.