- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
CapVector extracts parameter differences between auxiliary-trained and standard-SFT VLA models, then adds these differences to the pretrained model before downstream adaptation. A regularizer is introduced to preserve the injected benefits. The goal is to reuse auxiliary-training gains across tasks with lower downstream training costs.
Critical strengths
- The paper addresses a practical problem: reducing repeated auxiliary-training overhead when adapting VLA models.
- Experiments span multiple backbones, auxiliary objectives, simulation benchmarks, and real-world platforms, with promising cross-environment transfer results.
Critical weaknesses
-
The practical scope of checkpoint reuse is unclear. The main experiments inject vectors into the pretrained checkpoint used as their extraction origin. Their usefulness for domain-adapted or intermediate checkpoints remains untested. If extraction must be repeated for each starting checkpoint, the practical reuse benefit could be substantially reduced.
-
The paper describes it as enforcing orthogonal updates, but the formula appears to keep certain weights close to their starting values. The authors should clarify what it actually does and whether an ordinary penalty on weight changes would work similarly.
-
The authors already have an auxiliary-trained model. Why not directly fine-tune that model on the downstream task? Without this comparison, it is unclear why subtracting the standard-SFT model and adding the difference back to the pretrained model is necessary.
-
Downstream training may be cheaper, but extracting the vector requires two source-training runs. The cost assumptions used to estimate when this investment pays off do not match the appendix measurements. The paper should show the total cost at comparable success rates.
Questions for authors
- Can the same vector be reused on an already adapted or intermediate checkpoint without re-extraction or harming its existing capabilities?
- Does the regularizer enforce orthogonality, or mainly limit changes to certain weights? Would ordinary weight-update regularization work similarly?
- Does CapVector outperform directly fine-tuning the auxiliary-trained model on the downstream task?
- Including extraction costs, how many downstream tasks are needed before CapVector saves total computation at comparable performance?
Dear Reviewer 6XLL,
I hope this message finds you well. As the discussion period is nearing its end with less than three days remaining, I wanted to ensure we have addressed all your concerns satisfactorily. If there are any additional points or feedback you'd like us to consider, please let us know. Your insights are invaluable to us, and we are eager to address any remaining issues to improve our work.
Thank you for your time and effort in reviewing our paper.
Best regards, Authors