Responses to Reviewer 8w66 (Part 2)
**About the value of experiments on SAM.**
The purpose of this experiment is to demonstrate the generality of our method across different domains, which we believe is an important aspect of the paper’s contribution.
While the primary focus of our work is on merging LLMs to acquire agentic skills, one of the key strengths of CycleQD lies in its domain-agnostic design (i.e., task metric is the only thing that is required and it serves as both Q and BC). By applying CycleQD to SAM, we aim to prove this point and highlight that the proposed method is not limited to language models but can be generalized to other foundation models in the future for more diverse agentic skills.
**About adding more tasks to support the generality of CycleQD.**
In addition to the three CS tasks, we have incorporated a VQA task into CycleQD in this revision (see A.1.5).
As a vision-language modeling task, VQA differs significantly from computer science tasks, making this incorporation particularly challenging. During the CycleQD process, we extract the LLAMA3-8B-INSTRUCT component from LLAMA3-LLAVA-NEXT-8B and fuse it with other expert models.
The results indicate that CycleQD achieves better VQA performance compared to its expert model, while maintaining higher performance on MBPP and OS than their respective experts. Although its DB performance is lower than the DB expert, CycleQD achieves the highest average performance overall.
**About combining CycleQD with SFT.**
We have further fine-tuned the model optimized by CycleQD with the entire datasets for Coding, DB, and OS (model 11 in the following table). However, the fine-tuned model exhibits lower performance compared to the original CycleQD model (model 10). This suggests that CycleQD enhances the model's capability to its limit. Additionally, the fine-tuned model's performance is lower than that of other expert models (models 3, 4, 5, 6), indicating that it may have fallen into overfitting.
| Method | MBPP | DB | OS | Avg |
|--------------------------------|------|------|------|------|
| 3. Fine-tuning (Coding expert) | 70.4 | 21.2 | 20.7 | 37.4 |
| 4. Fine-tuning (DB expert) | 65.8 | 42.4 | 28.5 | 45.6 |
| 5. Fine-tuning (OS expert) | 66.3 | 0 | 30.4 | 32.2 |
| 6. Fine-tuning (All) | 67.3 | 37.1 | 36.7 | 47.0 |
| 10. CycleQD (Ours) | 76.4 | 38.2 | 42.6 | 52.4 |
| 11. CycleQD + ALL | 68.8 | 30 | 26.3 | 41.7 |
**About computation comparison between CycleQD and gradient-based fine-tuning.**
We have added this comparison in A.1.7. As a summary, the gradient-based fine-tuning took ~200 GPU hours, and CycleQD took ~410 GPU hours (excluding the experts training time). We wish to point out that (1) the extra time spent on CycleQD is mostly due to agentic task evaluations rather than the optimization, (2) due to GPU memory constraints, the merging process was carried out on CPU, (3) CycleQD produces an archive of models whereas fine-tuning generates only one. Furthermore, it is important to note that fine-tuning is a mature and well-established approach with software implementations that are optimized for efficiency. By contrast, the proposed method was developed primarily to assess its performance, and as such, there is ample room for further efficiency improvements.
**About sensitivity to the number of generations.**
We have added a sensitivity study to reveal this. Specifically, we tested CycleQD performance every 100 generations and added the results in A.1.3. In Figure 5, the performance gradually increases over the generations. We don’t observe large oscillations in performance w.r.t the number of generations.