You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.developers.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -579,13 +579,13 @@ k6_frac_N10_frac_chain_mem32K_40nm.xml ch_intrinsics.v common 9f591f6-
579
579
580
580
### Example: Titan Benchmarks QoR Measurements
581
581
582
-
The Titan benchmarks are a group of large benchmark circuits from a wide range of applications, which are compatible with the VTR project.
582
+
The [Titan benchmarks](https://docs.verilogtorouting.org/en/latest/vtr/benchmarks/#titan-benchmarks) are a group of large benchmark circuits from a wide range of applications, which are compatible with the VTR project.
583
583
The are typically used as post-technology mapped netlists which have been pre-synthesized with Quartus.
584
584
They are substantially larger and more realistic than the VTR benchmarks, but can only target specifically compatible architectures.
585
585
They are used primarily to evaluate the optimization quality and scalability of VTR's CAD algorithms while targeting a fixed architecture (e.g. at a fixed channel width).
586
586
587
587
A typical approach to evaluating an algorithm change would be to run `vtr_reg_titan` task from the weekly regression test:
588
-
588
+
#### [Running and Integrating the Titan Benchmarks with VTR](https://docs.verilogtorouting.org/en/latest/tutorials/titan_benchmarks/)
0 commit comments