We appreciate the careful framing of the teacher–probe distinction and the honest reporting of per-configuration results. The two points below are offered as tightening suggestions rather than fundamental concerns.
-
The Dao et al. (2021) citation is analogical and should be sharpened. In Section 4.2 (p. 4), you write that “the conditions used to write the teacher corpus must be honest out of sample” and cite Dao et al. for this claim. However, Dao et al. analyze in-sample bias of the teacher’s predictions, whereas your concern is that the probe’s conditions (the teacher corpus) are in-sample. This is a meaningful distinction: the cited work does not directly address the probe’s training conditions. I suggest tightening the citation, for example by writing “cf. the in-sample bias analysed by Dao et al.” and then explicitly stating that your concern is the probe’s conditions, not the teacher’s predictive bias. This will prevent a reader from inferring that Dao et al. support a claim they do not make.
-
The abstract’s GREEN claim is contradicted by your own Table 1 on two of three pairs. The abstract (p. 1) states: “It raises clinical efficacy F1 to 0.481 and the LLM-judged GREEN score to 0.510.” However, Table 1 (p. 5) shows that, relative to the Mcond baseline, SelfCue does not raise GREEN on two of the three configurations:
-
COLIPRI+Llama: 0.510=0.510 (no change, not a raise),
-
VISD+CT-CLIP: 0.504<0.512 (a drop),
-
MedGemma: 0.456<0.472 (a drop).
The body text in Section 6 (p. 9) says “SelfCue holds GREEN at the level of Mcond on all three pairs,” which is also inaccurate for the two pairs where GREEN decreases. We recommend qualifying the GREEN claim by configuration (e.g., “raises GREEN for COLIPRI+Llama and holds it within 0.008 for the other two”) or, more conservatively, reporting the GREEN result only relative to the M_base baseline, where the improvement is consistent. This will align the abstract and Section 6 with the tabulated evidence and avoid a reviewer or reader flagging the discrepancy.
- Literature & Related Work
Thank you for contributing a timely and well-scoped study on self-cueing for 3D CT report generation. The related-work section is clearly organized, and the probing-based framing in Section 2.2 is a useful lens. The following suggestions are intended to strengthen the transparency, completeness, and reproducibility of the literature positioning.
-
Enumerate the candidate set for the Table 1 eligibility screen and justify exclusions. At least four same-benchmark (CT-RATE) 2026 systems report clinical numbers at or above SelfCue’s headline figures ([email protected]$ = 0.481$, AUROC =0.775), yet none are cited or screened: NV-Reason-CT (report-derived macro-F1 0.592, macro-AUROC 0.871), Resolution Meets Reduction (clinical macro-F1 0.495), Sparse Concept Channels (F1=0.549), and Disease-Centric VLP (CT-RATE AUC 84.4%). The claim that “SelfCue is on par with the strongest eligible works on [email protected]” is therefore incomplete at best. Please add a paragraph (or a supplementary table) that lists every same-benchmark system you considered, states the inclusion/exclusion criteria (e.g., “we include systems that report [email protected] on CT-RATE test split and provide a public checkpoint”), and then explicitly explains why each of the four above is or is not included. If they are excluded because they report different metrics (e.g., macro-F1 or AUC), say so and consider adding a secondary comparison on those metrics.
-
Add Merlin (and ideally RadGenome-ChestCT) to the evaluation or justify the single-dataset scope. Merlin (Blankemeier et al., 2026, Nature) is the other major public 3D CT vision-language corpus, and the authors’ own ORCA paper evaluates on it (“We evaluate it across two datasets (CT-RATE and Merlin)”). The current manuscript never mentions Merlin, which weakens the generalizability claim. Please either (a) add Merlin (and RadGenome-ChestCT, if feasible) to the experimental setup, or (b) add an explicit justification for the single-dataset scope in Section 5.1, e.g., “we focus on CT-RATE because it is the only benchmark with a standardized [email protected] evaluation protocol; Merlin lacks this metric.” If the latter, also note that ORCA’s Merlin results do not transfer automatically to SelfCue.
-
Verify the RadAgent Table 1 row or remove it. The RadAgent row ([email protected] = 0.220) cannot be reconciled with its own abstract, which reports a 5.8-point (35.4% relative) macro-F1 improvement over CT-Chat: 0.184+0.058=0.242 (or 0.184×1.354=0.249), neither of which equals 0.220. Please check the full RadAgent paper (Roschewitz et al., 2026, arXiv:2604.15231) for the correct [email protected] value, or remove the row if the metric is not reported there. If you keep it, add a footnote explaining the derivation.
-
Expand Section 2.1 to cover the broader 3D CT report-generation literature. Section 2.1 currently cites only 8 works, while at least 15 same-domain systems exist and are uncited, including 3D-CT-GPT (Chen et al., 2024), CT-GLIP (Lin et al., 2024), M3 (Hosseini et al., 2025), MvKeTR (Deng et al., 2025), MedScribe (Orlando et al., 2026), CPR-RAG (Yang et al., 2026), MARCH (Lin et al., 2026), ALTER (Li et al., 2026), CORTEX (Malik et al., 2026), CTInstruct (Lei et al., 2026), Jolia/ConQuer (Khlaut et al., 2026), and Rad-JEPA 3D (Trinh et al., 2026). Please add the directly relevant ones to the related-work section, grouping them by approach (e.g., end-to-end generation, retrieval-augmented, agentic, and probing-based). Also consider citing R2Gen (Chen et al., 2020) as the foundational 2D radiology report-generation work, and Belinkov & Glass (2019) for the probing methodology in Section 2.2. This will position SelfCue more accurately within the rapidly growing field.
-
Positive note on reference integrity. We found no predatory or retracted venues among the verified references; all verified venues are legitimate (Nature Biomedical Engineering, Nature, ACL, EMNLP, AAAI, CVPR, ICLR, MICCAI, ISBI, Radiology: AI, JAMA Internal Medicine, PMLR). This is a strength of the manuscript and should be maintained as you add the new citations above.
We hope these suggestions help you sharpen the literature positioning and make the empirical claims more robust. The core idea of self-cueing is promising, and with a more complete and transparent related-work section, the paper will be a stronger contribution to the 3D CT report-generation community.
- Mathematical Correctness
The mathematical core of the paper is clear and the probing setup is thoughtfully designed. The suggestions below are about precision rather than correctness; addressing them will make the formal claims airtight.
-
Make the fold partition explicit in Eq. (2). The union notation ⋃kSk and the sentence “every training volume is paired with a report” imply that the folds cover the training set, but this covering property is never stated. Since Eq. (2) depends on the folds partitioning the training set, please state this explicitly, e.g., the folds form a partition of the training set Dtrain:
Si∩Sj=∅(i=j),⋃k=15Sk=Dtrain.
This removes any ambiguity about whether some training volumes could be excluded from all folds. (Section 4.2, p. 4)
-
Condition Eq. (3) on the prompt, or state that it is implicit. Eq. (3) writes pstudent(yi∣xi), but the text says the student “receives only the plain prompt.” Strictly, the probability should be pstudent(yi∣xi,promptplain). Since the prompt is fixed throughout, this is a reasonable notational simplification, but the equation as written is incomplete. Please either add the prompt explicitly in Eq. (3), or add a sentence such as “the prompt is fixed and suppressed in the notation.” (Section 4.2, p. 4; Eq. (3), p. 4)
-
State the zero-denominator convention for macro-F1max. In Section 5.1, when you define macro-F1max as the best F1 over all thresholds and introduce the threshold τ at which the readout becomes a condition, the case of an abnormality that is never mentioned and never present is not addressed. For such a class, precision is 0/0 and F1 is undefined. Please state the convention explicitly; the standard choice is to define F1=0 in this case. This will make the macro-average well-defined for all classes. (Section 5.1, p. 5–6)
-
Qualify the abstract’s “0.848 in the hidden states.” The abstract says “from 0.848 in the hidden states to 0.739 in the generated report,” but the evidence in Section 3.2 shows the hidden-state scores range from 0.839 to 0.848, and the 0.848 value is the pre-LM embedding score quoted from ORCA. Please adjust the abstract wording to match the evidence, e.g., “from up to 0.848 in the hidden states” or “from 0.839 to 0.848 in the hidden states.” This is a small change that will prevent overclaiming. (Abstract, p. 1; cf. Section 3.2, p. 3)
-
Add a control experiment for the “surfacing gap,” or soften the claim. The headline gap of 0.848→0.739 (a drop of 0.109) is measured with the trained CheapCT probe on hidden states and frozen RadBERT on reports. As written, the gap may partly reflect probe-versus-RadBERT differences rather than pure information loss at tokenization, because the paper never scores the same text with both rulers. I strongly recommend adding a control experiment in which the same generated reports are scored with both the CheapCT probe and RadBERT. If that is not feasible, please soften the claim “lost only when the hidden state becomes text” to something like “lost as measured by our two scoring instruments.” This is the most important point, because the paper’s central conclusion depends on comparing two different measurement tools. (Section 3.1, p. 3)
- Reproducibility
Thank you for releasing the code and for the detailed experimental description. The paper is largely reproducible in spirit, but several gaps currently prevent a competent peer from re-running the central result from the paper alone. The following suggestions are intended to close those gaps; none require new experiments, only additional reporting.
Data and comparability
-
Please clarify the relationship between the two evaluation sets. You report COLIPRI on n=1564 volumes and VISD+CT-CLIP on n=2987 (Section 5.1, p. 5). Are the 2987 volumes independent scans, or do they include multiple reconstructions of the same scan? If the latter, do multiple reconstructions enter the macro averages? The comparability claim is currently asserted rather than demonstrated; a sentence specifying the scan-to-volume mapping and the averaging unit would resolve this.
-
The claim that the effect is “not a quirk of one pipeline” (Section 1, p. 1) is supported by only three of the four possible encoder–backbone combinations (COLIPRI+Llama, VISD+CT-CLIP+Llama, COLIPRI+MedGemma), all within a single LLaVA-style architecture family and a single dataset (CT-RATE). Please either add the missing combination (VISD+CT-CLIP+MedGemma) or qualify the breadth claim, e.g., “not a quirk of one encoder–backbone pair within the LLaVA-style family on CT-RATE.” The generalization statement in Section 6 (p. 9) and the backbone-dependence discussion in Section 5.2 (p. 6) would also benefit from this qualification.
-
No reader study is reported; the paper explicitly defers this (“reader studies are the next step”, Section 6, p. 9). This is an acknowledged limitation, but please make sure the clinical-efficacy claims are read with this scope in mind—e.g., by adding a sentence in the abstract or conclusion that the reported metrics are automated, not clinician-validated.
-
The paper contains no ethics, informed-consent, IRB, or data-governance statement, despite using the clinical chest-CT dataset CT-RATE. Please add a statement on data usage and governance (e.g., in a dedicated Ethics Statement or in the Data Availability section). The only ethics-adjacent text is the AI Use Statement (p. 10); a data-governance sentence would complete the picture.
Training and hyperparameters
-
Student (SelfCue-KD) training details are incomplete. Please report epochs, learning rate, batch size, LoRA rank, and number of steps for the student. Section 5.3.4 (p. 8) states that the two students “start from the same checkpoint and train for the same number of steps” but gives neither value. The projector/LoRA training in Section 5.1 (p. 6) mentions a cosine schedule and effective batch size of 16, but the student-specific hyperparameters are missing. Please add a table or paragraph with the full student training configuration.
-
No cross-method hyperparameter-tuning protocol is described. The paper states its own tuning (e.g., the MedGemma baseline uses 5×10−6, “which a sweep selected for it”, Section 5.1, p. 6), but nothing is said about how the quoted baselines were tuned in their source papers, and no re-tuning under a common protocol is reported. Please state the tuning protocol for all compared systems, or explicitly note that no common protocol was applied.
-
The sentence “All three seeds land on that setting” (Section 5.4, p. 9) is ambiguous. If the recipe is unchanged across seeds, the setting is fixed, not re-selected; if the setting was re-selected per seed, that is a different experiment. Please clarify which procedure was used.
Evaluation and claims
-
Selection on the validation split is only partially mitigated. You state that α=1.0 and τ=0.75 were “chosen on the validation split” (Section 5.1, p. 6), Table 1 is scored on that same split, and the held-out experiment (Section 5.4, p. 9; Table 5, p. 9) covers only COLIPRI + Llama-3.1-8B. The headline numbers for VISD+CT-CLIP and MedGemma-27B therefore remain selection-on-validation. Please either extend the held-out experiment to those configurations or qualify the claims accordingly.
-
CLarGen’s Table 1 row ([email protected] = 0.486) lacks backbone annotation. Section 5.2 (p. 6) identifies 0.486 as the MedGemma-27B number and 0.472 as the Llama-3.1-8B number. Please annotate the row (e.g., “CLarGen (MedGemma-27B)”) so the reader can compare like-for-like.
-
The claim “SelfCue is on par with the strongest eligible works on [email protected] and GREEN and above them on F1max” (Section 5.2, p. 6) is only partially supported. The table’s eligible-works rows are not backbone-annotated, and CLarGen’s table value (0.486) exceeds SelfCue’s 0.481. Please qualify the claim (e.g., “on par with the strongest eligible works on [email protected] within the same backbone family”) or add the missing annotations.
-
Several metric values repeat suspiciously across conditions; please check them against unrounded numbers. Specifically: Table 1 (p. 5) shows GREEN = 0.510 for Mcond, SelfCue, and SelfCue-KD on COLIPRI+Llama (three identical in a row); SelfCue [email protected] = 0.481 on both COLIPRI+Llama and COLIPRI+MedGemma; Table 5 (p. 9) shows reported vs. held-out means identical for Mcond [email protected] (0.430/0.430), Mcond GREEN (0.510/0.510), and SelfCue-KD GREEN (0.510/0.510). Please report unrounded values or add a note explaining the coincidences.
-
The Table 4 mention-rate construction for condition-free systems is not stated. For Mbase and “Mcond, plain prompt” no condition is in the prompt, so the split must use the probe’s condition for all systems. Please state this explicitly in the caption or text.
-
Mcond under the plain prompt degrades substantially [email protected] 0.299 vs. Mbase 0.395, Table 4, p. 8), even though the plain branch is the reference in Eq. (1) and the 30% plain-prompt mixture was intended to “keep the plain branch in distribution.” This unexplained degradation deserves discussion; please add a paragraph interpreting this result.
-
The abstract’s claim that SelfCue “drops into any pipeline already serving the baseline” is broad: the student requires the same visual encoder/compressor and prompt format. Please qualify the drop-in claim (e.g., “drops into any pipeline already serving the baseline with the same visual encoder and prompt format”).
- Spelling, Grammar, Acronyms
Thank you for preparing the manuscript with careful attention to cross-referencing. I have two points to raise, one positive and one that will improve consistency for readers.
- Please expand all acronyms and symbols at first use. I noticed at least one instance of an abbreviation or symbol used without a definition at first use (e.g., Abstract, p. 1), and the same convention should be checked throughout the whole document rather than only at the listed locations. Specifically, the following acronyms are used before being defined or are never expanded:
- LLM (Abstract) — never defined.
- GREEN (Abstract) — first defined in Section 5.1 but never expanded there.
- AUROC (Abstract) — never expanded.
- KD (Abstract, in “SelfCue-KD”) — never defined.
- [email protected] (Contributions, p. 2) — defined only later in Section 5.1.
- F1max (Table 1) — defined only in Section 5.1.
- τ (Table 1 caption) — defined only in Section 5.1.
- LoRA (Section 5.1) — never expanded.
For each of these, please provide the full expansion at the first occurrence in the abstract, main text, and table/figure captions, and then use the abbreviation consistently thereafter. This will help readers who encounter the terms early on and will align the manuscript with standard scholarly practice.
Minor editorial findings (typos and wording)
1 minor points, listed here rather than in the sections above so they do not obscure the substantive feedback. None of these affects the scientific content.
- Typos and copy-editing artifacts: p. 4 'optimized' → 'optimised' (UK consistency); p. 6 'a report mentions 2.4 of the 3.4 abnormalities present' is ambiguous (average?); references: duplicated 'Shaun Lindsay, Shaun Lindsay' and 'Shuqiang Zhang, Shuqiang Zhang'; comma-mangled 'Guangyi, Zhang' and 'Yu, Wang'; 'Jean bastien Grill' → 'Jean-Bastien Grill';
Thank you for recognizing the controlled decoding gains and the practical value of distillation. We have added diagnostic evidence and clarified the mechanism and scope of the clinical results.
Q1. Why are the trajectories so similar, and could alignment explain this?
We added FlexiCT, ASAP and HLIP with Llama-3.1-8B to Table 1. Across six configurations, visual-probe AUROC ranges from 0.824 to 0.868 and report AUROC from 0.727 to 0.753. Higher visual-probe scores generally accompany higher hidden-state and report scores, while the surfacing gap remains 0.097–0.116. The scores therefore vary with the visual representation. All generators use SFT with frozen visual representations and trained projectors/LoRA adapters; Setup specifies the backbone-specific learning rates. A shared alignment bottleneck may still contribute. We clarify this interpretation in Section 3.2 and provide published configurations for context in Table 2 and Appendix C. Figure 1's caption also explains the rescaling of MedGemma's 62 layers to Llama's 32-layer axis.
Q2. Does probing show information in text positions or its active use by the LLM?
Appendix B.1 and Table 8 compare pooling visual positions, all prompt positions and the last prompt position, which can attend to the image. Their best-layer AUROCs differ by at most 0.010 across the three configurations. This shows that abnormality information is recoverable from text positions as well as visual positions. We agree that probing alone does not establish how each finding is used during generation. Replacing the hidden-state probe with a visual-embedding probe also changes downstream scores by at most 0.008 (Table 5). We now frame SelfCue as expressing information recoverable from the generator's internal representations.
Q3. Could the hidden-to-report gap reflect different measurement tools?
The probe and RadBERT are different readouts. To check reference-label sensitivity, we relabeled the same reference reports with gpt-oss-120b. Keeping all prediction scores fixed changes the COLIPRI–Llama AUROC gap only from 0.1093 to 0.1075. The gap therefore persists under alternative reference annotation. Section 3.2 and Appendix B.2 report this check. We revised the Introduction and Discussion to describe report expression as an important bottleneck.
Q4. How does SelfCue differ from putting probe predictions in the prompt?
The baseline uses predicted labels in the prompt, while SelfCue additionally contrasts conditioned and plain logits from the same model at the same generated prefix. With weights and labels fixed, [email protected] rises from 0.430 to 0.481. To make this distinction easier to follow, we renamed ordinary conditioned generation the “Probe-conditioned baseline.” We explain the distinction after Eq. (1) and in Table 2's caption. SelfCue provides one way to narrow the surfacing gap through decoding.
Q5. What happens when the condition contains errors?
SelfCue helps reports express more abnormality information recoverable from the model. In Table 6, mention rates for reference-positive cues rise from 0.697 to 0.901, and overall [email protected] increases from 0.430 to 0.481. Some incorrect predictions are expressed more often too. Our method promotes expression of the probe's predictions but has no dedicated mechanism to check their correctness against the CT image or filter errors. We added this limitation in “Limitation: error propagation” and identify cue verification and error filtering as future work.
Q6. Why do the F1 gains not consistently improve GREEN?
F1 measures expression of the 18 targeted abnormalities, while GREEN also assesses clinical details beyond these labels. Higher F1 therefore need not yield higher GREEN: NV-Reason-CT (Myronenko et al., 2026) reports F1 of 0.5923 and GREEN of 0.4072. Relative to the probe-conditioned baseline, our GREEN is unchanged on COLIPRI–Llama and falls by 0.008 on VISD–Llama and 0.016 on COLIPRI–MedGemma. Table 2 reports these results. We revised “GREEN” and Discussion's “Complementary metrics” to explain why both metrics are needed.
Q7. What is the scope of the clinical evidence?
Under automated evaluation, SelfCue improves expression of the 18 targeted categories in SFT-trained generators. The same-split template control in Table 3 also shows higher report F1 and GREEN for SelfCue than fixed label templates. Benefits for other findings and finer attributes, including location, size and laterality, remain future work, as stated in “Limitation: scope of the correction.”