- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes OFLBe, a semantic-anchor-guided framework for one-shot federated learning (OFL) under non-IID data distributions. The method constructs shared class-level semantic anchors using a pretrained CLIP text encoder to provide a common reference for independently trained clients. During local training, an anchor-guided feature alignment loss and a learnable-prototype classification loss are jointly optimized. After a single upload of local models and class prototypes, the server performs similarity-weighted prototype aggregation and feature-level ensemble inference. The paper also derives conditional bounds relating anchor discrepancies to intra-client and inter-client representation inconsistency. Experiments on CIFAR-10, CIFAR-100, and Tiny-ImageNet report improvements over existing OFL baselines under different degrees of label heterogeneity.
Critical strengths
1. Well-motivated semantic alignment for one-shot federated learning. The paper addresses an important challenge in OFL: independently trained clients may learn inconsistent representations under heterogeneous data distributions, without subsequent communication rounds to correct them. Constructing shared semantic anchors before local training provides a reasonable and coherent approach to this problem.
2. Promising empirical performance across heterogeneous settings. Table 1 reports consistent accuracy improvements across CIFAR-10, CIFAR-100, and Tiny-ImageNet under different Dirichlet concentrations, with particularly large gains under severe label skew. The additional experiments on client scalability, heterogeneous architectures, and training costs further support the potential applicability of the framework.
Critical weaknesses
1. Insufficiently established novelty and confounded contribution of pretrained semantics. FAFI (ICML 2025) already combines local feature alignment, learnable class prototypes, server-side prototype aggregation, and feature-level ensemble inference. OFLBe follows a closely related framework, mainly introducing fixed CLIP-derived semantic anchors and similarity-based weighting. However, the paper does not sufficiently isolate the benefits of these algorithmic changes from those of the additional pretrained semantic knowledge. A comparison with FAFI equipped with equivalent CLIP anchors is needed to establish the independent contribution of the proposed approach.
2. Experimental inconsistencies and insufficient validation of the proposed mechanism. Tables 1 and 3 report inconsistent baseline results under the apparently identical CIFAR-10 setting with five clients and α = 0.5. In particular, Co-Boosting changes from 70.24% to 55.34%. FAFI also has different values in Tables 1 and 6 under the corresponding Tiny-ImageNet setting. These discrepancies require clarification, especially because many baseline results are imported from previous papers. Moreover, the paper does not directly quantify the proposed representation-inconsistency measures, and the independent benefit of anchor-aware server integration over simpler aggregation strategies remains insufficiently established.
Questions for authors
-
Could the authors explain the discrepancies across Tables 1, 3, and 6, particularly the 14.90-percentage-point difference for Co-Boosting? Since many baseline results are taken from previous publications, how are the data partitions, training budgets, model initialization, and evaluation protocols verified to be comparable?
-
How does OFLBe compare against FAFI when both methods have access to the same frozen CLIP semantic anchors? Can the authors distinguish the contribution of pretrained semantic knowledge from that of the proposed training and server-side integration mechanisms?
-
Could the authors report the actual intra-client and inter-client inconsistency metrics defined in Appendix C? How much improvement is independently provided by anchor-aware prototype aggregation and feature fusion compared with uniform alternatives? Additionally, how do the fusion weights behave when client class supports have little overlap?
-
How is the cumulative communication cost in Figure 3 calculated? Does it include the uploads of all client models and prototypes, and how does the server-side inference cost scale with the number of participating clients?