Soheil Shahrouz

| branch | Place time | Place WL | Place CPD | |----------|----------|----------|----------| | this PR | 0.992 | 1.00 | 1.00 | | master | 1.000 | 1.00 |...

@vaughnbetz CI failures are gone now. The issue was that move generators needed to be crated after initial placement, where movable block are determined, but merging master into this branch...

Titan benchmarks | | vtr_flow_elapsed_time | pack_time | placed_wl | total_swap | place_time | placed_cpd | routed_wl | heap_pop | route_cpd | |-------------|-----------------------|-----------|-------------|-------------|------------|-------------|-------------|-------------|-------------| | master | 2858.225484 | 398.634554| 2572680.235...

vtr_reg_nightly_test1 and vtr_reg_nightly_test1_odin failures are fixed. vtr_reg_nightly_test3_odin hits the 7 hours executin time limit, which is a little strange because vtr_reg_nightly_test3 finishes in ~1 hour.

I ran nightly3_odin tasks on wintermute. There is no significant execution time difference between this branch and the master branch on wintermute.

> Maybe the odin II run is at the edge of 6 hours and we need to split it? I am running tasks in nightly3_odin as different CI tests to...

The mcml circuit in vtr_reg_qor_chain_predictor_off has an execution time about 5 times longer than the master branch. Finding the minimum channel width takes 38 times longer than on the master...

[vpr.txt](https://github.com/user-attachments/files/15518700/vpr.txt) It seems that the router tries to route the design at a channel width much lower than the minimum channel width. Since routing_failure_predictor is off, it does not terminate...

@vaughnbetz I updated the golden results for CI tests that were failing for out of bound QoR values. Now, all CI tests pass.