“布局成本表”会影响路由器吗？

假设我有一个设计，其中每个最后的BEL都定位到固定位置，因此放置器基本上没有自由度。
问题：改变成本表会影响路由器的行为吗？
为了记录，我正在使用大约95％固定位置的设计，因此更改成本表肯定会影响我的设计。
最后5％的位置很好，但是我从路由器得到了一些不理想的结果 - 它在LOC'd单元之间做了一些愚蠢的事情路由路径。
我想知道是否值得花时间在Amazon EC2上购买所有100个成本表的详尽探索。
不幸的是，现在我无法判断更改成本表是否会影响路由器，因为它正在改变最后5％的位置（对LOC'd区域的拥塞产生“连锁反应”）或是否更改成本表
实际上导致路由器行为明显不同。
在后一种情况下，尝试所有100个表格对我来说可能是值得的。
PS：设备是Spartan-6，它放置在地图阶段，所以我在这里添加了成本表标志。
我假设成本表选择被隐藏在ncd的某处，以便路由器可以检索它...
PPS：这是一个疯狂密集的设计;
如果没有放置限制，它甚至不会以10mhz路由。
因此，我可能在par工具的预期使用模型之外运行。



以下为原文

Suppose I have a design in which every last BEL is LOC'd to a fixed location, so that the placer has essentially zero freedom.

Question: will changing the cost table influence the behavior of the router?

For the record, I am working with a design that is about 95% fixed-placement, so changing the cost table definitely affects my design.  The placement of the last 5% is just fine, but I'm getting some suboptimal results from the router -- it's doing some kind of dumb things routing paths between LOC'd cells.  I'd like to know if it's worth buying time on Amazon EC2 for an exhaustive exploration of all 100 cost tables.  Unfortunately right now I can't tell if changing the cost table is affecting the router because it's changing the placement of that last 5% (which has a "ripple effect" on congestion in the LOC'd areas) or whether changing the cost table actually results in significantly different router behavior.  In the latter case it's probably worth it for me to try all 100 tables.

PS: the device is Spartan-6, which does placement in the map stage, so that's where I'm adding the cost-table flag.  I assume the cost table choice gets stashed somewhere in the ncd so that the router can retrieve it...

PPS: this is an insanely dense design; it won't even route at 10mhz without the placement constraints.  So it might be that I'm operating outside the intended usage model for the par tools.