- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
SizingAgent is a training-free framework for analog sizing. It combines LLM-derived initialization with device lookup tables, a structured reasoning prompt supplied with finite-difference sensitivities, and a pre-simulation filter that checks proposed action directions. Multiple initializations and sensitivity-guided numerical exploration complete the workflow. The paper evaluates 27 SKY130 circuits and several proprietary and open-weight backbones. It reports 74.8% Pass@1 with Gemini 2.5 Flash, compared with 42.0% for the strongest evaluated same-backbone baseline.
Critical strengths
-
The approach addresses a concrete failure mode with a deployable mechanism. Supplying measured sensitivities to an LLM and checking proposed directions before spending another simulation is sensible. The shared-backbone comparison, 27-circuit benchmark, and tests across multiple model families provide substantially more evidence than isolated examples. Table 7 is internally consistent: its counts sum to 303/405, yielding 74.8% Pass@1; all 27 circuits succeed at least once.
-
The ablations already establish useful incremental effects. Within the separate ablation experiment, removing SV changes successes from 322 to 288, an 8.4-point reduction, and removing PGR yields 262, a 14.8-point reduction. Thus, there is evidence for these modules with the other components retained. The paper also explicitly acknowledges stale sensitivities, independently checked actions that are executed jointly, and equation/diagnosis fields that are not machine-verified. Those qualifications appropriately limit what “verification” means.
Critical weaknesses
-
The baseline protocol and the largest ablation effect cannot currently be reconstructed unambiguously. Section 4.3, Table 2, and Appendix A specify 15 runs per cell. Yet several LLM-baseline entries, including 7.1/35.7 and 42.9/97.2 for Pass@1/Pass@5, match the estimator at 14 trials rather than 15. Separately, the 27 printed “w/o PI” counts in Table 6 sum to 171, not its reported 161. If the individual cells are correct, this implies 42.2% success and a 37.3-point decrease from 322/405, rather than the reported 39.8-point decrease. The other five ablation column totals are correct. These could be reporting errors, and the corrected PI effect would still be large; nevertheless, run denominators, excluded attempts, and the authoritative counts must be reconciled.
-
The stronger attribution to LLM physics reasoning exceeds the controls. The no-PI ablation simultaneously removes LLM guidance and the gm/Id lookup mechanism, replacing the initialization with random sampling. It measures the value of that bundle, not an isolated LLM contribution as claimed in §4.5. This does not negate the separate SV/PGR gains. The novelty discussion should also distinguish the directional filter from earlier equation-based feedback systems, including White-Op (arXiv:2601.21321), Bujana and Karsilayan (arXiv:2604.07387v1), and NEMESIS (arXiv:2607.05657). Table 1's negative entry for AutoSizer's simulation-grounded loop is difficult to reconcile with that work's explicit feedback-to-LLM mechanism (§§3.6, 4.6, arXiv:2602.02849v2). A more precise positioning would strengthen the actual contribution without requiring a new model architecture.
Questions for authors
-
What are the successful/attempted counts behind the affected Table 2 cells, and how are infrastructure errors and non-converging circuit simulations handled? Table 8 discloses one excluded GA run, but the corresponding LLM-baseline rules are unclear.
-
Which “w/o PI” entries or aggregate are incorrect? Please reconcile them from existing records, and explain Appendix B's 20.45 simulations/run versus Table 7's 19.4. The main and ablation experiments are explicitly separate; their different aggregate rates are not, by themselves, contradictory.
-
Is there existing evidence separating LLM initialization guidance from access to the same device tables and initialization procedure? For SV, can the recorded traces quantify useful proposals rejected or unhelpful proposals admitted as sensitivities become stale, beyond the illustrative checked steps?
5 comments
Response to Reviewer w8vm (Part 2/3)
(Continued from Part 1/3 above.)
Q (W2). Does the w/o PI ablation isolate the LLM contribution, how does SizingAgent differ from prior equation-based feedback methods, and how should AutoSizer be classified in Table 1?
Ans. Thank you for these precise points. We agree on both: the w/o PI ablation measures the initialization module as a whole rather than the LLM alone, and SizingAgent should be positioned more precisely against the four works cited. We have added controls that isolate the LLM and revised the positioning as follows.
-
Attribution of the w/o PI drop. Removing PI replaces both the targets of the LLM and the gm/Id lookup with random sampling, so its drop measures the module as a whole, and we have revised §4.5 accordingly. The controls in General Response 2 isolate the LLM: with the same gm/Id tables and downstream modules, LLM targets succeed in 55/85 runs, compared with 48/85 for fixed targets, and removing LLM guidance from both PI and PGR lowers success from 199/270 to 127/270. Our response to Q3 gives further detail.
-
Positioning against earlier equation-based feedback systems. As shown in the table below, the four works differ from SizingAgent in what they produce and in what simulation feedback controls.
| Work | Output | What simulation feedback controls | Screens each proposed update by measured sensitivity before simulation |
|---|---|---|---|
| White-Op [2] | Behavioral op-amp design from a symbolic optimization problem | Refines the design using theory–simulation discrepancies | Not described |
| Bujana and Karsilayan [3] | Executable analytical sizing function | Calibrates device parameters with operating-point simulations; feeds prediction errors into later rounds | Not described |
| NEMESIS [4] | Performance equations (models) from netlists and schematics | Repairs the equation predictions with SPICE | Not applicable (builds models, no sizing loop) |
| AutoSizer [5] | Circuit sizing with optimizers selected and configured in a two-loop framework | Selects optimizers; adapts ranges and active variables | Not described |
| SizingAgent | Transistor dimensions and bias parameters within a fixed simulation budget | Individual parameter updates, proposed by PGR and screened by SV | Yes (SV) |
SizingAgent's distinct element is the action-level filter: PGR proposes individual parameter updates, and SV screens the direction of each against the local response needed to close a specification gap, before the joint candidate is simulated.
-
Table 1(d): AutoSizer. We agree that AutoSizer has a simulation-grounded loop with explicit feedback to the LLM (§§3.6 and 4.6 of [5]). We have changed its entry in Table 1(d) to Partial (marked in blue), with a note that its feedback adapts optimizer selection, ranges, and active variables rather than individual parameter updates.
-
Evidence for the directional filter. In the repeated ablation, removing SV lowers success by 5.9 percentage points and removing PGR by 7.7 points. SV flags a directional conflict in 615 of 3,323 recorded checks (18.5%) before the candidate is simulated. In the telescopic OTA case (General Response 3), SV rejects an L5 update whose measured gain sensitivity (−0.200) contradicts the equation-based proposal. PGR revises it to W7 × 1.05, SPICE confirms that all four specifications are met, and a same-state offline replay confirms that the rejected update would have failed.
Overall, the PI ablation supports the initialization module as a whole, and General Response 2 isolates the contribution of the LLM. Relative to the four works, SizingAgent's distinct contribution is to screen individual sizing actions by their measured direction before simulation, within a fixed budget. The revised manuscript updates Table 1(d), discusses the four works in §2, and adds the telescopic OTA case to Appendix B.2 and the same-state comparison as Figure 4.
References
[2] Chen et al., White-Op, arXiv:2601.21321 (2026).
[3] Bujana & Karsilayan, Self-Calibrating LLM-Based Analog Sizing, arXiv:2604.07387 (2026).
[4] Ghosh et al., NEMESIS, arXiv:2607.05657 (2026).
[5] Yu et al., AutoSizer, arXiv:2602.02849 (2026).
Our response is continued in Part 3/3 below.
Response to Reviewer w8vm (Part 3/3)
(Continued from Part 2/3 above.)
Q (Q1). What are the successful/attempted counts behind Table 2, and how are infrastructure errors and non-converging simulations counted?
Ans. Thank you for this question. Every LLM-baseline cell now has 15 attempted runs (Table R8). A simulation that does not converge counts as a used, unsuccessful evaluation, and an infrastructure interruption is resumed, so each run yields exactly one outcome.
Table R8. LLM baselines with Gemini 2.5 Flash; successful runs out of 405 attempted (27 circuits × 15 runs), Pass@1, and Pass@5 averaged over circuits.
| Method | Successful / attempted ↑ | Pass@1 ↑ | Pass@5 ↑ |
|---|---|---|---|
| ADO-LLM | 131/405 | 32.3% | 57.9% |
| AutoSizer | 87/405 | 21.5% | 38.2% |
| EEsizer | 170/405 | 42.0% | 70.0% |
| LEDRO | 94/405 | 23.2% | 42.2% |
These counts determine the Pass@1 entries of the revised Table 2. Pass@5 is computed for each circuit from its 15 runs and then averaged over the 27 circuits.
Infrastructure error handling.
-
Current protocol (stated in the supplement). A submitted candidate uses one SPICE evaluation even if ngspice does not converge or a required measurement is missing, and it cannot count as a success. Infrastructure interruptions are logged separately, and each resumed run contributes one completed outcome to the denominator.
-
Historical batch. The earlier runner treated a propagated exception as an unfinished run and a completed run without a feasible design as a failure; its logs cannot fully separate internally caught API errors from SPICE non-convergence. The GA run excluded in the earlier Table 8 came from this batch.
-
Refreshed GA and BO records. Each has 405 completed runs, with 70 and 95 successes, and the revised Table 8 lists 15 GA runs per circuit.
Overall, every baseline entry now traces to 15 attempted runs per circuit, and the supplement states how failed simulations and interruptions are counted.
Q (Q3). Can the effect of LLM-guided initialization be isolated from device-table access, and what do recorded SV traces reveal about false rejections, false acceptances, and stale sensitivities?
Ans. We thank the Reviewer for these valuable questions. Yes to both: a matched control separates the targets of the LLM from the device tables and the initialization procedure, and the recorded traces quantify the errors of SV in both directions.
-
LLM initialization versus the same device tables. Holding the gm/Id tables and the downstream PGR and SV fixed, and changing only the source of the targets, LLM-generated targets succeed in 55/85 runs, compared with 48/85 for fixed targets (General Response 2). This isolated difference is modest. The combined control, which removes LLM guidance from both PI and PGR across all 27 circuits, is large and statistically clear: 199/270 (73.7%) versus 127/270 (47.0%), Fisher's exact p < 10−9. The gm/Id conversion is deterministic given the numerical targets: removing the equation text from 26 archived PI outputs while keeping the targets fixed yields identical initial dimensions. The archived lookup check is also reported in Appendix I.2.
-
SV errors in both directions. Across 3,323 action-level checks, SV finds 2,253 directions consistent with the stored sensitivities (67.8%), flags 615 as conflicts (18.5%), and marks 455 as weak (13.7%). Because one LLM proposal can contain several actions, we also audited proposals against their SPICE outcomes: among 1,415 archived proposals, the directional rule would reject 440 (45 later retained by SPICE) and admit 975 (92 later rolled back by SPICE). The two errors have different costs. An admitted ineffective proposal costs one SPICE evaluation, which then exposes it; a rejected action returns to PGR for revision, as in the telescopic OTA case. SV is therefore a screen, and SPICE remains the final judge of every candidate. (Section 4.7, Figure 4; Appendix B.2)
-
Stale sensitivities. These counts cover all recorded checks; we have not yet broken them down by the age of the sensitivities.
Overall, the matched control shows that the LLM's targets add value beyond the device tables, and the audit shows that SV errs in both directions while its net effect is positive: removing it lowers success by 5.9 percentage points.
We thank the Reviewer again for the careful audit, which has made our reported results more accurate and our contribution more precisely stated.
Response to Reviewer w8vm (Part 1/3)
We thank the Reviewer for the exceptionally careful audit of our records and the constructive comments. Below, we reconcile each flagged count with the archived records, add controls that isolate the contribution of the LLM, position SizingAgent precisely against the four works cited, and audit the recorded SV checks. All changes are highlighted in blue in the revised manuscript.
Q (W1). Why do some Table 2 cells appear to use 14 rather than 15 trials, and why do the 27 w/o PI entries in Table 6 sum to 171 rather than the reported 161?
Ans. We are grateful for this careful reconstruction. Both observations are correct, and we have reconciled them with the archived records. We have updated and re-checked every other cell of Tables 2 and 6 against the archived records and found no further discrepancy.
Baseline denominators. The affected LLM-baseline cells were computed from 14 recorded outcomes, exactly as the Reviewer inferred from the estimator: an interrupted batch had left one outcome unrecorded in each of them. We reran each missing trial with its original seed, so every cell now has 15 completed runs. The revised Table 2 reports the updated values, and Table R8 (response to Q1) gives the successful/attempted counts.
The w/o PI total: one cell was misprinted, not the total. The Reviewer's column sum is correct. The archived record for the PMOS-input OTA cell is 2/15, which the original Table 6 printed as 12/15. With 2/15, the 27 cells sum to the reported 161/405, and the decrease from the original full result (322/405) is 39.8 percentage points, as reported.
The revised Table 6 reports the repeated batch. The revised Table 6 reports the repeated ablation with the main experiment's seeds (Table R3 in General Response 3). Without PI, initialization is random sampling, so this cell depends on the random initial designs that each seed draws, and the two batches use different seeds. We report these updated results in the updated manuscript so that each set of numbers matches its own records.
Overall, every baseline cell now rests on 15 runs, and the original w/o PI total and its 39.8-point decrease stand, with the PMOS-input OTA cell corrected to 2/15. The revised Table 2 reports 15 runs per cell, and the revised Table 6 reports the repeated ablation with the main experiment's seeds.
Q (Q2). Which w/o PI counts are correct, and why does Appendix B report 20.45 simulations per run while Table 7 reports 19.4?
Ans.
w/o PI counts. With the corrected cell, the 27 cells sum to 161/405, and the decrease from the original full result (322/405) is 39.8 percentage points, as reported (see response to W1).
Mean simulation cost. Appendix B's 20.45 simulations per run come from the ablation experiments, whereas Table 7's 19.4 comes from the main experiment. As the Reviewer notes, the two experiments are separate batches with the same benchmark and settings, so their means need not coincide. We have clarified this distinction in Appendix B of the revised manuscript.
Consistency check. Repeating the ablation with the main experiment's seeds gives a full-pipeline success rate of 74.6%, compared with 74.8% in the main experiment (see Table R10 below).
Table R10. Repeated full-pipeline and component ablation using main-experiment seeds (27 circuits × 15 runs; 50 SPICE evaluations per run).
Overall, the original w/o PI total and its 39.8-point decrease stand after the one-cell correction, and the two simulation-cost figures come from separate batches rather than inconsistent settings. The revised manuscript and Appendix B distinguish these experimental batches.
Our response is continued in Part 2/3 below.