fix(pyplacedb): union fixed placement obstacles - #153
Merged
Conversation
Emin017
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
total_space_areafrom the exact terminal-geometry union clipped to the core, avoiding double-counted overlapping halos and blockagesVerification
test/tools/ecc/test_pyplacedb_macro_status.py:2 passed in 0.44scell_padding_x=400,iteration=3000, and routability optimization disabled stopped at iteration 1296 with overflow0.09878085, belowstop_overflow=0.1; the previous representation plateaued around0.1131Scope Note
The Kunminghu ECC process later exited during the separate post-placement
feature_placement_map()iRT EarlyRouter evaluation after very high memory growth. DreamPlace placement had already completed, but ECC currently runs that optional evaluation beforesave_data(), so the final DEF was not written. That orchestration and memory issue is outside this ecc-tools geometry change.