I’m sure I must be missing something that makes this “suggested_clock_period” untrustworthy, but if not — if this CLOCK_PERIOD approach actually does cause OpenLane to use a different strategy (and with still a low number of routing iterations, I might add) — then is there a reason it doesn’t just try this hard from the start when given a value like 20ns?