| *** tpb has joined #vtr-dev | 00:00 | |
| *** q3k has quit IRC | 00:45 | |
| *** q3k1 has joined #vtr-dev | 00:46 | |
| *** q3k1 is now known as q3k | 00:47 | |
| *** digshadow has quit IRC | 19:25 | |
| mithro | kem_: Once you have gotten the titan benchmarks, how do you actually run them? | 21:10 |
|---|---|---|
| kem_ | mithro: You've run 'make get_titan_benchmarks'? | 21:11 |
| mithro | kem_: Yes | 21:11 |
| mithro | It tells me how to run them manually with | 21:12 |
| mithro | vpr $VTR_ROOT/vtr_flow/arch/titan/stratixiv_arch.timing.xml $VTR_ROOT/vtr_flow/benchmarks/titan_blif/neuron_stratixiv_arch_timing.blif --route_chan_width 300 | 21:12 |
| kem_ | mithro: Check out https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/master/README.developers.md#example-titan-benchmarks-qor-measurements | 21:12 |
| tpb | Title: vtr-verilog-to-routing/README.developers.md at master · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com) | 21:12 |
| mithro | But how to I do it automatically | 21:13 |
| mithro | kem_: Thanks! We knew we had seen it but apparently have become blind :-P | 21:13 |
| kem_ | mithro: The surrounding sections should also be useful, they try to document the methodology and motivations for QoR comparisons. | 21:14 |
| kem_ | mithro: Also, if you have the CPUs and Memory you'll likey want to provide -j N to run_vtr_task.pl to run up to N benchmarks in parrallel | 21:15 |
| mithro | kem_: Thanks! - https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/388 | 21:15 |
| kem_ | mithro: Otherwise they will take a really long time | 21:15 |
| tpb | Title: Create a link from readthedocs to the README.developers.md for titan benchmark running · Issue #388 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com) | 21:16 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!