The Cadence Academic Network helps build strong relationships between academia and industry, and promotes the proliferation of leading-edge technologies and methodologies at universities renowned for their engineering and design excellence.

A huge knowledge exchange platform for academia to network with industry. We are looking for academic speakers to talk about their research to the industry attendees at the Academic Track at CDNLive EMEA and Silicon Valley.

Share

Digital Implementation Forums

About encounter DB command & its hidden option?

Started by archive on 26 Apr 2007 10:24 PM. Topic has 4 replies and 10925 views.
Last post on 26 Apr 2007 10:24 PM by 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"

4 Replies

For item 1, you could use the "setObjFPlanBoxList" command to define a polygon shape for a fence. You can see this command echoed to your .cmd file if you define an object to have more than 4 sides with the "Cut Rectilinear" widget in the GUI. Here is some sample output:

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?

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.