search

ckeh / vtr-verilog-to-routing

Automatically exported from code.google.com/p/vtr-verilog-to-routing
0 stars 0 forks source link

Convert xml file #104

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What version of the product are you using? On what operating system?
7.0 , ubuntu 14.0 LTE

Please provide any additional information below.

I've been tried to converted "k4-n4.xml" architecture from version 5.0 to 
version 7.0. However,the result of max channel widths are different (15 vs 18), 
When I executed cluster 4 "e64.blif" , both in v5.0 and v7.0. Am I missing 
something that I should notice ?

Original issue reported on code.google.com by rchu...@gms.tcu.edu.tw on 17 Apr 2015 at 5:53

Attachments:

GoogleCodeExporter commented 9 years ago 
A few things.  You probably mean min channel instead of max channel width.  You 
are using a unidirectional architecture so your channel widths cannot be odd 
(15 should not happen unless there is a bug in the code).  And finally, the 
algorithms are pseudorandom so min channel width in the same build can change 
with something as simple as a different starting seed.

I just realized that we do not have links to background papers, which are 
important for understanding the use of the tool.  Redirecting to Kevin to add 
some background papers to wiki.

Original comment by JasonKai...@gmail.com on 17 Apr 2015 at 12:49

GoogleCodeExporter commented 9 years ago 
I agree we should add more background papers and guides on tool usage.

However, since Google code is shutting down this year, this will probably be 
deferred until we've transitioned to new code hosting (likely Github).

Original comment by kevinemu...@gmail.com on 17 Apr 2015 at 1:35

GoogleCodeExporter commented 9 years ago 
Thanks for your help. As I know, version 5.0 improved "xilinx x4000" series 
architecture.Does version 7.0 using same way?

Original comment by rchu...@gms.tcu.edu.tw on 18 Apr 2015 at 3:33