- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents EvoPCB, an LLM-based framework for end-to-end PCB physical design that formulates placement and routing as script generation and optimization over domain-specific APIs. The framework comprises three main components. First, RePCB jointly encodes component connectivity, placement geometry, and routing images, with supervision derived from wirelength and via count. Second, Bayesian optimization constructs layout–script training pairs, which support SFT and a customized DAPO procedure for generating initial designs. Finally, MM-Evolve iteratively refines the designs through topology, thermal, and electromagnetic agents using simulation feedback.
Critical strengths
The problem is practically relevant, and the API-based formulation makes sense for the task PCB physical design involves discrete decisions, geometric constraints, and competing physical objectives. Having the LLM generate calls to existing placement and routing tools gives it a concrete role in the design process: selecting and configuring tools, while the tools carry out the geometric operations.
The data construction addresses a concrete limitation of the available supervision. Expert PCB layouts often lack the scripts that produced them. Searching over a constrained API space to recover executable scripts is a practical way to turn these layouts into training examples. RePCB’s use of connectivity graphs and routing images is also a reasonable choice for representing the different aspects of a PCB layout.
Critical weaknesses
RePCB’s supervision remains largely determined by conventional metrics. I am not yet convinced that its similarity score captures expert design preferences beyond wirelength and via count. In Equation (4), both the regression targets and the pairwise similarity targets are derived from these two quantities. Two layouts with identical wirelength and via count therefore receive a target similarity of one, even if their routing structures differ substantially. The EM and thermal prediction results in Table 7 are useful, but downstream prediction accuracy does not directly establish that the similarity score reflects expert preferences.
The benefit of the DAPO customization has not been established. There is no controlled comparison with standard DAPO using the same PCB reward components and training budget. In particular, the contributions of the LBI filter and the modified advantage remain unclear. LBI checks whether a layout is legal and differs from the reference; this condition alone does not ensure variation in rewards within a group. The paper should clarify the actual filtering procedure and provide evidence that these changes improve training efficiency or final design quality.
Questions for authors
How does performance change if RePCB similarity is replaced by a similarity score computed directly from the normalized wirelength and via-count features used in Equation (4), while keeping the rest of the pipeline unchanged?
Can RePCB distinguish layouts with similar wirelength and via count but different topology or expert-assessed quality? A controlled comparison of such layouts would help clarify what the representation captures beyond its supervised metrics.
How does the customized DAPO compare with standard DAPO when using the same initial checkpoint, training data, PCB reward components, and rollout budget? It would also be helpful to separate the effects of LBI and the modified advantage.
10 comments
3. Effectiveness of Customized DAPO
All configurations use the same initial checkpoint, training data, PCB reward components, and evaluation protocol. “Naive DAPO” is the standard DAPO comparison; “Customized DAPO w/o LBI” changes the advantage; and the final row adds LBI. This sequential comparison evaluates the advantage change followed by LBI.
| RL Configuration | WL(mm) | Via | Legal script(%) | ||
|---|---|---|---|---|---|
| w/o DAPO | 1389.6 | 61.4 | 6.21 | 2.247 | 88.7 |
| Naive DAPO | 1357.9 | 58.8 | 5.65 | 2.086 | 89.8 |
| Customized DAPO w/o LBI | 1291.3 | 51.0 | 3.41 | 1.864 | 89.2 |
| Customized DAPO (Ours) | 1208.5 | 47.1 | 2.78 | 1.736 | 99.1 |
Here, a legal script is one that executes successfully and produces a DRC/LVS-valid layout. The final model's 99.1% rate corresponds to 991 legal outputs among 1,000 held-out PCB design tasks, with one generated initial script per task. LBI retains a rollout in the loss only when it is legal and differs from the reference under the implementation's coarse metric-level WL/via criterion, thereby focusing the finite update budget on non-equivalent outcomes under the two primary scalar routing objectives. Metric matching does not imply script, layout, or topology equality, and matched rollouts may still contain structural information; we therefore regard this filter as an empirical design choice supported by the ablation rather than a theoretically necessary criterion. LBI also does not itself guarantee reward variation. The comparison from Naive DAPO to Customized DAPO w/o LBI measures the modified advantage, and the final comparison isolates LBI. LBI raises the empirical legal-script rate from 89.2% to 99.1%, although illegal scripts are filtered rather than assigned an explicit negative advantage.
Conclusion
Thank you again for your valuable and constructive feedback. Your comments have substantially improved the clarity of our paper. We would be grateful if you could reevaluate our work and reconsider the score in light of these clarifications and additional results.
Dear Reviewer,
We hope our clarification has addressed your concerns. We have added further experiments to the anonymous repository: https://anonymous.4open.science/r/EvoPCB-ICLR-2027-8E0E/Rebuttal_EvoPCB.md. We welcome any feedback you may have, and we would be very grateful if you could reconsider your score in light of our clarification.
Best regards,
All authors
We would like to express our gratitude for your thoughtful review and recognition of our work. Your comments have guided us in clarifying our methodology. We have added more detailed evidence to the anonymous repo: https://anonymous.4open.science/r/EvoPCB-ICLR-2027-8E0E/Rebuttal_EvoPCB.md to address the reviewers' concerns. Key additional content will be added to the paper.
1. RePCB Similarity Analysis
In the reward ablation below, we keep the group-normalized WL/via reward riWV=α(wˉ−wi)/(σw+δ)+β(vˉ−vi)/(σv+δ) fixed and change only the similarity term. The four configurations use: (i) no similarity term; (ii) the analytic WL/via similarity target pi from Eq. (4); (iii) centered RePCB similarity si−sˉ; and (iv) uncentered RePCB similarity si. Their complete rewards are therefore riWV, riWV+γpi, riWV+γ(si−sˉ), and riWV+γsi, respectively. The last two configurations have the same within-group similarity ordering and differ by the group-wide offset γsˉ, which can affect finite-sample, filtered, and clipped policy updates. The remainder of the pipeline is unchanged.
Direct metric rewards produce slightly shorter WL, but all three similarity-based configurations improve EM/thermal costs over WL+Via only. Centered RePCB further improves RePCB similarity and EM cost over analytic metric similarity, while the uncentered variant gives the best via count, EM/thermal costs, and RePCB similarity. These results support the empirical utility of the learned RePCB signal and of the uncentered design in the reported pipeline; they do not establish that RePCB directly optimizes EM/thermal objectives. The RePCB-similarity column measures agreement under the learned representation and is not an independent quality measure.
2. Discrimination Ability of RePCB
The topology-sensitivity study below evaluates 30 layout pairs per category: one group with clearly different WL/via counts but similar PnR topology, and another group with similar WL/via counts but different PnR topology. Using the same fixed 0-1 rubric for all shuffled pairs, topology similarity was rated independently by three senior PCB engineers (scores averaged) and by GPT-6 Astra, from route geometry, relative component placement, and layer-transition patterns. RePCB similarity is the normalized cosine similarity between the corresponding embeddings.
RePCB similarity remains high when topology is similar despite large WL/via differences, and decreases when topology differs despite similar WL/via values, in agreement with the independent engineers' ratings. These results provide evidence that RePCB is sensitive to topology beyond its two scalar supervision targets on the evaluated pairs.