Matt Liberty
Matt Liberty
I take that back - you do have clock propagation on. I don't understand the question though. In `484.724+41.142=525.866` where id 41.142 come from? Did you mean 42.713?
In the text report I see: ``` >>> report_checks -fields {slew cap input nets fanout} -format full -through ces_0_0/io_lsbOuts_7 Startpoint: ces_0_0 (rising edge-triggered flip-flop clocked by clock) Endpoint: ces_0_4 (rising...
If you expand the clock tree it is clearer:  The 42.713 is the last delay in producing the 331.162. You need to ad the delay of the next line...
I don't see a bug here, perhaps a misunderstanding?
Its a packaging error - it should be ./home not /home in var*sh
how many iterations?
In my run I see ``` [NesterovSolve] Iter: 1370 overflow: 0.235532 HPWL: 19759299769 [NesterovSolve] Iter: 1380 overflow: 0.209551 HPWL: 19286141404 [INFO GPL-0075] Routability numCall: 8 inflationIterCnt: 3 bloatIterCnt: 1 ```...
I suspect the extra time comes from these ``` [NesterovSolve] Revert back to snapshot coordi ```
@gudeh do you know where the congestion is that routability isn't able to resolve? It seems we are stuck in loop that becomes mostly futile after the first few iterations.
@gudeh I see on both this design and ariane/gf12 thin bands of congestion right after the routability iteration, eg  They seem solvable as the surrounding area is not congested....