detailRoute vs trialRoute

Hi Rajesh,

There's not a way to have reportRoute key off trialRoute differences instead of half-perimeter net wirelengths.  Would you explain a little more the scenario(s) you're seeing that this information would be particularly helpful?  It might give us reason to pursue an enhancement to the tool.

The net lengths are *not* stored as part of the net object in Encounter.  There are "dbNetLenX" and "dbNetLenY" but if you create a serpentine route you'll notice that it's more of a half-perimeter number that's reported.  Here's a code example I cooked up that leverages dbGet to capture wire coordinates and adds up the total wire length:

set totalLength 0
foreach pt [dbGet $net.wires.pts] {
  if {$pt != "0x0"} {
    set a [lindex $pt 0]
    set ax [lindex $a 0]
    set ay [lindex $a 1]
    set b [lindex $pt 1]
    set bx [lindex $b 0]
    set by [lindex $b 1]
    set xlen [expr $bx - $ax]
    set ylen [expr $by - $ay]
    set len [expr abs($xlen) + abs($ylen)]
    set totalLength [expr $totalLength + $len]
  }
}
puts "$totalLength"

Maybe you could use this on your design as a starting point for comparing whether trialRoute vs. detailRoute is more enlightening than half-perimeter vs. detailRoute.  Let us know what you find, and if I can be of further assistance on scripting especially.

Thanks,
Bob

Hi Rajesh,

There's not a way to have reportRoute key off trialRoute differences instead of half-perimeter net wirelengths.  Would you explain a little more the scenario(s) you're seeing that this information would be particularly helpful?  It might give us reason to pursue an enhancement to the tool.

The net lengths are *not* stored as part of the net object in Encounter.  There are "dbNetLenX" and "dbNetLenY" but if you create a serpentine route you'll notice that it's more of a half-perimeter number that's reported.  Here's a code example I cooked up that leverages dbGet to capture wire coordinates and adds up the total wire length:

set totalLength 0
foreach pt [dbGet $net.wires.pts] {
  if {$pt != "0x0"} {
    set a [lindex $pt 0]
    set ax [lindex $a 0]
    set ay [lindex $a 1]
    set b [lindex $pt 1]
    set bx [lindex $b 0]
    set by [lindex $b 1]
    set xlen [expr $bx - $ax]
    set ylen [expr $by - $ay]
    set len [expr abs($xlen) + abs($ylen)]
    set totalLength [expr $totalLength + $len]
  }
}
puts "$totalLength"

Maybe you could use this on your design as a starting point for comparing whether trialRoute vs. detailRoute is more enlightening than half-perimeter vs. detailRoute.  Let us know what you find, and if I can be of further assistance on scripting especially.

Thanks,
Bob