Tuesday, January 06, 2009     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Digital IC > Floorplanning, Place and route

Subject: About encounter DB command & its hidden option?
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
eminemshow
Posts: 75
Online: User is Offline
4/27/2007 1:24 AM  

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"
BobD
Posts: 80
Online: User is Offline
4/27/2007 6:38 AM  
Hello eminem,

Welcome to the forum! Hope you find it useful.

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:

setObjFPlanBoxList Module {DTMF_INST/RESULTS_CONV_INST} 922.0200 673.6800 1151.7000 840.0000 922.0200 840.0000 1042.1400 905.5200

For additional information, type:

encounter> help setObjFPlanBoxList
or
encounter> man setObjFPlanBoxList

Regarding hidden variables- maybe you could provide some additional information on what you're trying to achieve that isn't happening by default?

Hope this helps,
Bob
eminemshow
Posts: 75
Online: User is Offline
4/28/2007 3:37 AM  
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?
BobD
Posts: 80
Online: User is Offline
4/30/2007 7:54 AM  
For 1, there's a couple of different ways to get this. First, there's a corresponding "getObjFPlanBoxList" that goes with setObjFPlanBoxList. It works like this:

encounter 34> getObjFPlanBoxList Module DTMF_INST/RESULTS_CONV_INST
942.48 598.08 1172.16 749.28 942.48 749.28 1100.88 829.92

You could also query the db similarly to how you have with "dbConstraintBox" to get a list of the boxes that make up the polygon. Here's an example of how you could do that with FE-TCL:

proc userConstraintBoxList {hinstName} {
set constraintBoxList {}
set constraint [dbHInstConstraint [dbGetHInstByName $hinstName]]
set constraintBox [dbConstraintBox $constraint]
dbForEachConstraintBox $constraint box {
set ptrBox [dbBoxPtrBox $box]
lappend constraintBoxList $ptrBox
}
if {[llength $constraintBoxList] > 0} {
return $constraintBoxList
} else {
return $constraintBox
}
}

encounter 28> userConstraintBoxList DTMF_INST/RESULTS_CONV_INST
{1884960 1498560 2201760 1659840} {1884960 1196160 2344320 1498560}

This scripted method is probably easier to do if you're writing a script because you can control the formatting of what is returned to suit your needs.

For item 2, using 6.2 you can use "setECOMode -noRefinePlace" to suppress refinePlace during eco commands. In 6.1 and earlier, you can use "setOptMode -noRPlace" to achieve same.

-Bob
eminemshow
Posts: 75
Online: User is Offline
5/06/2007 12:38 AM  
Really thanks!! BObD, hope we can be friends!! My MSN is eminem198123@hotmail.com
Posting to forums is available to community members only.
Login or Register
Forums > Digital IC > Floorplanning, Place and route > About encounter DB command & its hidden option?


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.