- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
CodePaint combines a layout-trained VQ-VAE with absorbing discrete diffusion for IC layout completion. TokenProbe enables geometric conditioning by retaining tokens selected through encoder sensitivity to spacing perturbations. The paper also investigates few-shot adaptation to a commercial PDK.
Critical strengths
The work addresses a practically relevant problem and reports a substantial improvement in direct DRC compliance, from 12.00% for PatternPaint to 75.69%. Calibre-based verification and the commercial-PDK evaluation provide meaningful evidence of practical utility.
Critical weaknesses
-
The methodological novelty is moderate. The representation and diffusion components are established techniques. The contribution therefore rests primarily on their application to layout generation and on the effectiveness of TokenProbe.
-
TokenProbe’s selection criterion needs stronger validation. Encoder sensitivity to a geometric perturbation does not establish that retaining the selected tokens is sufficient or necessary to preserve that geometry. It may also constrain unrelated features. A direct geometric-retention baseline would help establish the benefit of operating through token sensitivity.
-
The control evaluation does not fully establish precise, site-specific preservation. Metrics are computed after target-template cleanup, and successful realization need not occur at the original site. Furthermore, unchanged per-rule violation counts do not guarantee the absence of newly introduced violations.
-
The ablations contain confounding factors. The appendix describes different noise schedules and loss formulations across transition variants, while the cross-PDK comparison uses different adaptation procedures. These settings limit attribution of the improvements to the proposed mechanisms.
Questions for authors
- Can the authors clarify the implemented transition schedules and provide appropriately controlled comparisons?
- How does TokenProbe perform at the original target site before cleanup, compared with directly retaining the target geometry?
3 comments
W2 W3 and Q2: Site preservation before and after cleanup
We thank the reviewer for raising these points. That a successful realization need not occur at the original site is a deliberate choice rooted in the requirement of our task. Rule-targeted generation needs layouts that contain a requested spacing (e.g., 18 nm tip-to-side) for DTCO rule probing. A pattern serves this purpose wherever the spacing occurs, so the property to preserve is the spacing itself, not its absolute position in the clip. Problem 2 (Sec. 2.4) defines target consistency this way, and Kept follows it.
Before and after cleanup. To separate token retention from cleanup, we report Kept and Kept + clean before and after cleanup for every Table 2 variant.
| Method | Kept, before cleanup (%) | Kept + clean, before cleanup (%) | Kept, after cleanup (%) | Kept + clean, after cleanup (%) |
|---|---|---|---|---|
| Unconditional | 17.8 | 1.4 | 10.0 | 3.7 |
| Random | 20.7 | 1.7 | 13.1 | 5.7 |
| BoxKeep | 44.1 | 2.2 | 38.9 | 14.7 |
| TokenProbe | 53.0 | 4.0 | 55.2 | 22.5 |
The advantage of TokenProbe is already present before any cleanup. TokenProbe keeps the target in 53.0% of draws, against 44.1% for BoxKeep and 17.8% unconditionally, and the ranking TokenProbe > BoxKeep > Random > Unconditional holds in all four columns. Raw rasters contain isolated noise pixels that the deck flags as violations, so Kept + clean is low for every method before cleanup and rises after it. Token retention therefore realizes the dimension, and cleanup mainly supplies legality.
New violations. Our check already works at the level of individual violations, not counts. A draw is clean only if every Calibre violation it contains also appears in the reference, with the same rule at the same location. Any newly introduced violation fails the draw. The wording "no rule has more violations" in Appendix D.3 understates this, and we will clarify it in the revised PDF.
Dear Reviewer 6ydi,
Thank you again for your thoughtful feedback and careful consideration of our work. As the discussion period draws to a close, we would appreciate knowing whether our responses have sufficiently addressed your concerns. For convenience, we summarize our main responses below:
For W1 (Methodological novelty & task alignment): We clarified that our contribution goes beyond adapting existing components: (1) our layout-learned VQ vocabulary and monotonic absorbing kernel eliminate substitution defects and reduce boundary speckle by 25× (driving direct DRC compliance from 15.08% to 75.69%), and (2) TokenProbe introduces the first training-free, label-free mechanism to steer continuous critical dimensions numerically in discrete layout generation.
For W4 / Q1 (Noise-schedule confounds): We conducted controlled experiments training the absorbing diffusion model under the exact same constant noise schedule () used by all alternative kernels. Absorbing diffusion maintains a high direct DRC pass rate (72.00%), confirming its advantage is robust and independent of schedule differences.
For W2, W3 / Q2 (Site preservation & new violations): We provided detailed before-and-after cleanup metrics demonstrating that TokenProbe's target realization advantage over direct geometric retention (BoxKeep) already holds prior to post-processing ( vs. ), and clarified that our DRC evaluation strictly inspects individual violations rather than net counts to rule out any newly introduced errors.
We would greatly appreciate any further comments or questions. Thank you again for your time and positive recognition of our substantial DRC compliance gains and industry-aligned practical utility!
Thank you for recognizing the practical relevance of the problem and the substantial improvement in direct DRC compliance, and for noting that the Calibre-based verification and commercial-PDK evaluation provide meaningful evidence of practical utility. We greatly appreciate your constructive comments. Below, we provide our detailed responses to each point.
W1: Methodological novelty
We acknowledge that vector quantization and absorbing-state diffusion are established concepts. Our contribution lies in how we adapt and integrate them for layout generation, guided by the properties that layouts require.
First, the representation is not a generic image tokenizer. Prior diffusion-based layout generation works in a continuous latent space pretrained on natural images, and its decoder adds edge noise that only template cleanup can remove. CodePaint learns its vocabulary directly from layouts. Each code is a learned prototype of a local layout feature, so every decoded token is geometry observed in real designs.
Second, our use of absorbing diffusion is also not a generic transfer of D3PM. We select the absorbing kernel for two properties (Sec. 3.2, Fig. 2b). Its corruption removes information and never substitutes one layout code for another. Its completion is monotonic and never revisits a revealed token. Both properties matter for layouts. A single pixel-scale defect can invalidate an otherwise clean layout. With the tokenizer fixed, the kernel alone moves the direct DRC-clean rate from 15.08% (uniform) to 45.62% (codebook-similarity) to 75.69% (absorbing). It also reduces boundary speckle from 5,121 to 206 pixels (Table 1, Fig. 2c).
Third, prior controllable layout generators steer only coarse attributes, such as pattern category or a text description of the rule (Sec. 2.2). To our knowledge, CodePaint is the first to control a requested critical dimension numerically, and TokenProbe is the mechanism that makes it possible. It retains the tokens whose encoder features respond to a perturbation of the target dimension. It needs no labels, no retraining, and no rule-specific code.
Together, these choices address a specific gap in prior layout generation: continuous latent diffusion yields noisy geometry and offers no handle on a requested dimension. CodePaint raises direct DRC compliance from 12.00% to 75.69%, realizes a requested dimension within a designated region, and adapts the same prior to a commercial PDK from 20 clips without retraining.
W4 and Q1: Confounds in the ablations
We thank the reviewer for identifying the noise-schedule confound in the original comparison. We conducted additional experiments to assess whether the absorbing model’s advantage depends on its cosine-squared schedule. The original settings and new results are summarized below. Direct DRC pass rates are measured before geometric cleanup.
The codebook-similarity variant did not converge under the tested cosine-squared configuration. We therefore only trained the absorbing model with the constant schedule used by both alternative kernels. Under this shared schedule, absorbing diffusion achieves a 72.00% direct DRC pass rate, only 3.69 percentage points below its original result, and substantially above the uniform and codebook-similarity variants.
These results show that absorbing diffusion maintains strong performance under the constant schedule and that its observed advantage cannot be explained solely by the original noise-schedule difference.