Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 7577
  • 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

About encounter DB command & its hidden option?

archive

Dear All:

I am a new comer here, I got two questions to ask:

1. Is there any db commands that can manipulate polygons, which means that I can cut a rectangular region or fence into polygon shaped?
2. Can anyone tell me some encounter hidden variables like "set drouteUseMinSpacingForBlockage true"


Originally posted in cdnusers.org by eminemshow
Parents

  • 1. Really thanks, BobD!!! :-) But I really found that when I want to get the module constraint (such as region, guide , fence, etc) boudary box, if the really boundary is a L shaped (or any other polygon shaped) box, I use the 'dbConstraintBox' command, I get the rectangular box, not a polygon.......sigh! Is there a command through which I can get polygons!?

    2. For the hidden variables, when I use the 'ecoChangeCell' command, encounter just run 'refinePlace' everytime it finishes a 'ecoChangeCell' command ,is there a variable to control this. By which I can just run 'refinePlace' once after all 'ecoChangeCell' commands?


    Originally posted in cdnusers.org by eminemshow
Reply

  • 1. Really thanks, BobD!!! :-) But I really found that when I want to get the module constraint (such as region, guide , fence, etc) boudary box, if the really boundary is a L shaped (or any other polygon shaped) box, I use the 'dbConstraintBox' command, I get the rectangular box, not a polygon.......sigh! Is there a command through which I can get polygons!?

    2. For the hidden variables, when I use the 'ecoChangeCell' command, encounter just run 'refinePlace' everytime it finishes a 'ecoChangeCell' command ,is there a variable to control this. By which I can just run 'refinePlace' once after all 'ecoChangeCell' commands?


    Originally posted in cdnusers.org by eminemshow
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.