Open vijayank88 opened 1 year ago
We generally only write the .odb when a step succeeds. If we write it on failure then the next invocation of make will not try to re-run grt. We could write some other .odb just for debug purposes though that may be confusing to novices.
For debug purpose can be created if it's fails with congestion.
You are missing the point that doing so has a meaning to the flow that is incorrect
@oharboe you may need this option as per discussion https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/discussions/1338
We generally only write the .odb when a step succeeds. If we write it on failure then the next invocation of make will not try to re-run grt. We could write some other .odb just for debug purposes though that may be confusing to novices.
Indeed: the debug .odb would have to be written with a different name.
disk space&runtime vs. usability is an issue: if we write it out when the .rpt files are written that takes disk space and time in the case where the reports might not be used.
if we don't write out the .odb alongside the progress .rpt file, then the user has to go spelunking to get that .odb file written out.
In CTS, you can specify CTS_SNAPSHOTS=1, this writes out extra .odb snapshots with names that don't collide with make dependencies.
Much as I hate options, perhaps a ROUTE_SNAPSHOTS=1?
Or perhaps simply add a generic SNAPSHOTS=1?
There is nothing extra to see in the .odb even if we wrote it out. The markers can be loaded against the cts .odb and will be visually identical.
Subject
[Stage]: Global Router.
Describe the bug
If there is any global routing congestion, flow write
congestion.rpt
, but without writing5_1_grt.odb
. It makes hard to debug visually where congestion occurs in OpenROAD gui.Expected Behavior
If there is a congestion during global routing stage, write
.odb
along withcongestion.rpt
and exit the flow.Environment
To Reproduce
Hope description gives idea about requirement
Relevant log output
No response
Screenshots
No response
Additional Context
No response