Closed oharboe closed 2 days ago
Hi @oharboe, this message is not an error message actually. This is printing the worst slack after calling repair design with resizer. Maybe we should transform this into a debug message.
@gudeh Understood. However, it may be useful for the user to know that they can relax the optimization target to improve running times. If message can be rearticulated to communicate this, it would be helpful.
It seems that having some document or global options on fast analysis is better than sprinkling hints throughout the log
@rovinski Had an idea to collect data on running times vs quality of results and creating a tool that recommended options?
I am closing this issue. I am currently working on the timing driven mode in global placer, which is what generates the mentioned logs. We should have further modifications on timing driven in the near future.
Description
What is OpenROAD trying to tell me here?
Is OpenROAD trying to tell me that removing
-timing_driven
could speed things up?For architectural exploration, I initially want fast turnaround time with less accurate results.
Suggested Solution
Make the error message more actionable.
Additional Context
No response