how to generate DRC report during DRT

[gkamendje]

DRT is not converging on my design and the DRT phase iterates over and over with hundreds of violations. The log file 5_2_TritonRoute.log contains information like

[INFO DRT-0195] Start 9th optimization iteration.
    Completing 10% with 101 violations.
    elapsed time = 00:00:00, memory = 650.74 (MB).
    Completing 20% with 101 violations.
    elapsed time = 00:00:00, memory = 650.74 (MB).
    Completing 30% with 101 violations.
    elapsed time = 00:00:49, memory = 654.01 (MB).
    Completing 40% with 101 violations.
    elapsed time = 00:00:49, memory = 654.01 (MB).
    Completing 50% with 101 violations.
    elapsed time = 00:00:51, memory = 654.01 (MB).
    Completing 60% with 101 violations.
    elapsed time = 00:01:15, memory = 654.01 (MB).
    Completing 70% with 101 violations.
    elapsed time = 00:01:18, memory = 654.01 (MB).
    Completing 80% with 101 violations.
    elapsed time = 00:01:28, memory = 654.01 (MB).
    Completing 90% with 101 violations.
    elapsed time = 00:01:32, memory = 657.29 (MB).
    Completing 100% with 101 violations.
    elapsed time = 00:01:46, memory = 657.29 (MB).
[INFO DRT-0199]   Number of violations = 101.
Viol/Layer      METAL1 METAL2
Metal Spacing      100      0
SpacingTableTw       0      1
[INFO DRT-0267] cpu time = 00:03:11, elapsed time = 00:01:47, memory = 672.04 (MB), peak = 672.95 (MB)
Total wire length = 17502 um.
Total wire length on LAYER METAL1 = 603 um.
Total wire length on LAYER METAL2 = 6624 um.
Total wire length on LAYER METAL3 = 9546 um.
Total wire length on LAYER METAL4 = 590 um.
Total wire length on LAYER METAL5 = 138 um.
Total number of vias = 3022.
Up-via summary (total 3022):.

But nothing really related to the nature of the violations. Since the DRT step never completes, no DRC report is generated and I can't have a clear picture of the violations. Is there a way to generate DRC reports during the DRT phase?

[vijayank88]

@gkamendje
You've to wait till 64th iterations to get drt.drc report.

[gkamendje]

Ok Thanks

[rovinski]

@vijayank88 @gkamendje you can use the -droute_end_iter flag to stop DR early. In ORFS this can be added with DETAILED_ROUTE_ARGS

For example:
make DETAILED_ROUTE_ARGS=' -droute_end_iter 9'
To stop after the 9th iteration.