doc update

This commit is contained in:
Jan Petykiewicz 2026-04-02 22:30:22 -07:00
commit 316eda090d
3 changed files with 6 additions and 3 deletions

View file

@ -186,7 +186,7 @@ The frontier trace is observational only. It reruns only the final reached-but-c
Use `scripts/record_frontier_trace.py` to capture JSON and Markdown frontier-prune artifacts for the built-in trace scenarios. The default target is `example_07_large_scale_routing_no_warm_start`.
Separately from the observational trace tooling, the router may run a bounded post-loop pair-local scratch reroute before refinement when the restored best snapshot ends with final two-net reached-target dynamic conflicts. That repair phase is part of normal routing behavior and is reported through the `pair_local_search_*` counters below.
Separately from the observational trace tooling, the router may run a bounded post-loop pair-local scratch reroute before refinement when the restored best snapshot ends with final two-net reached-target dynamic conflicts. In the late all-reached low-edge regime, the negotiated-congestion loop also narrows reroutes to the current conflict set and may carry capped heavy nets forward by immediately restoring their incumbent reached-target paths instead of spending more search work on pathological late reroutes. That behavior is part of normal routing and is reported through the `pair_local_search_*` and `late_phase_capped_*` counters below.
## 9. Pre-Pair Frontier Trace
@ -321,8 +321,8 @@ Use `scripts/record_iteration_trace.py` to capture JSON and Markdown iteration-a
- `pair_local_search_attempts`: Number of pair-local-search reroute attempts executed across all considered pairs.
- `pair_local_search_accepts`: Number of pair-local-search attempts accepted into the whole routed result set.
- `pair_local_search_nodes_expanded`: Total A* node expansions spent inside pair-local-search attempts.
- `late_phase_capped_nets`: Number of late all-reached heavy-net reroutes run under the bounded node-limit cap before pair-local handoff.
- `late_phase_capped_fallbacks`: Number of those capped late-phase reroutes that fell back to the incumbent reached-target path instead of replacing it.
- `late_phase_capped_nets`: Number of heavy nets identified in the final all-reached late phase and handled by the capped carry-forward path before pair-local handoff.
- `late_phase_capped_fallbacks`: Number of those capped late-phase nets that kept their incumbent reached-target paths instead of accepting a newly searched replacement.
## 10. Internal Modules