feat: add VLSI Global Placement benchmark (Frontier-Eng) - #98
Open
y-ji24 wants to merge 1 commit into
Open
Conversation
🤖 AI Code Review (gemini-3-flash-preview)🇬🇧 English Analysis1. Executive Summary
2. AI Content Analysis
3. Engineering & Economic Assessment
4. Quality Assurance
5. Security & Privacy Check
🇨🇳 中文分析1. 摘要
2. AI 成分分析
3. 工程与经济评估
4. 质量保证
5. 安全与隐私检查
|
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
This PR adds a new Frontier-Eng benchmark for VLSI Global Placement, based on the ISPD 2005 placement benchmark suite.
The task requires an agent to generate legal placements for movable components while minimizing Half-Perimeter Wirelength (HPWL) under placement constraints.
The benchmark includes two representative datasets with different difficulty levels:
Highlights
Benchmark
Agent Interface
The agent can modify only the
place_components()function inscripts/init.py, which is enclosed by an EVOLVE-BLOCK. All evaluation logic, data loading, and output interfaces remain read-only.Evaluation
The evaluator independently verifies:
A candidate is considered valid only if all legality constraints are satisfied.
Baseline
A deterministic row-based placement baseline is provided.
The baseline:
Repository Structure
This benchmark follows the standard Frontier-Eng layout, including:
scripts/verification/baseline/references/frontier_eval/with
scripts/init.pyas the only editable source file.Verification
Verified on both benchmarks.
Runtime:
Docker Support
Containerized evaluation is supported through
verification/docker/Dockerfile.Notes
To reduce repository size, the benchmark stores netlists in a compact index-based representation. During loading, the representation is deterministically expanded into the original in-memory format. This compression is lossless and does not affect placement, legality checking, or HPWL computation.
Only two datasets (adaptec1 and adaptec3) are included in this benchmark. Frontier-Eng benchmarks are not required to include every instance from the original ISPD 2005 benchmark suite; representative instances covering different difficulty levels are sufficient.