- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Fuzzy-MoE proposes a channel-level forecasting ensemble with local convolutional and global segmented features, learned Gaussian memberships, product aggregation, and a dual-view router over linear experts. Its MLP-gate comparison keeps the backbone fixed and supports the routing design. Two questions remain: whether the latent rules have the claimed physical or regime semantics, and whether input-dependent routing adds value beyond strongly smoothed or input-independent mixing.
Critical strengths
-
The dual-view router combines local and global temporal features. Its Gaussian and product calculations make the routing computation inspectable in the learned latent space. Section 3.4 describes the linear expert design.
-
Table 1 reports competitive results on six benchmarks. Appendix D.3 and Table 5 compare fuzzy and MLP gates with the same forecasting backbone. All twelve reported MSE comparisons favor the fuzzy gate. For example, ETTh2/96 has MSE 0.271 versus 0.303. These results support the complete fuzzy-gate design.
Critical weaknesses
-
The claims about physical semantics and regime identification need independent support. The fuzzy antecedents use coordinates produced by a learned nonlinear projection. Their explicit formulas make routing traceable, but the connection to meaningful temporal states remains unvalidated. Appendix D.4 uses the same gate's argmax to label the t-SNE visualization. Separation under these labels does not independently validate recovered regimes. The rule-deletion experiment also has a narrower interpretation. Suppressing Gaussian firing strengths changes routing while leaving the associated expert with positive Softmax weight. The ablation measures sensitivity to that perturbation. It does not measure complete removal of the expert's predictive contribution or independently validate regime semantics.
-
The experiments do not separate the benefit of input-dependent fuzzy routing from the benefit of bounded, strongly smoothed mixing. For the tau=5 implementation in Model.py, firing strengths in [0,1] bound the ratio between any pair of expert weights by exp(0.2), approximately 1.2214. With five experts in this implementation, the per-view weights lie at approximately 0.1699–0.2339. Averaging the two views preserves these bounds, apart from the negligible normalization epsilon. These conditional bounds should not be applied to runs using another temperature or to configurations with another expert count. Small weight changes may still matter when expert predictions differ. Uniform and learned input-independent gates would help resolve this attribution question. Table 5 supports the combined design but does not separate input dependence from smoothing or regularization.
The experimental entrypoint and effective temperatures also need clarification. Pipeline/OneMulEdit.py imports the absent model.CMoS. Model.py fixes tau=5 and does not read configs.tau. The ETTm2 configuration files specify tau=0.3, while the weather files specify tau=5. The package also includes initModel.py, which uses a different temperature-dependent gating calculation. Please identify the actual training/evaluation entrypoint, source version, and effective temperature for the main results. One or two representative saved prediction, metric, and configuration records should connect those results to the program used. A source update or textual explanation alone cannot document the existing runs retrospectively. This concern remains until matching records are provided.
Questions for authors
-
What temperature and expert count were used for each main result? Can the authors provide uniform-gate and learned input-independent-gate comparisons with the same expert backbone and training protocol? Capacity- or entropy-matched MLP controls would further distinguish the fuzzy structure from smoothing.
-
Is there independent regime annotation, a controlled temporal-feature intervention, or other externally grounded evidence connecting the learned antecedents to the claimed states? If this evidence is unavailable, can the claims be narrowed to latent-space routing traceability? The remaining structured-routing contribution would then need to be evaluated on that basis.
-
Which actual entrypoint and model/source version produced the main results? How were the temperature sweeps implemented when Model.py fixes tau=5? Please clarify whether the configured tau=0.3 and tau=5 values took effect. Please provide one or two representative saved predictions, metric records, and effective configurations with an explicit mapping to the reported results. They should identify whether the results used Model.py, initModel.py, or another version. Please also connect Figure 5 to its original unrounded gate tensor, plotting script, source/configuration, checkpoint, and selected evaluation batch.
Additional presentation feedback Figure 2 labels the Prediction shape as B×L×C, whereas Section 3.4.2 and Eq. (11) define the final output as B×P×C. It labels the first local convolution as Conv 1×1, although that layer uses kernel_size=configs.kernel_size; the second convolution is 1×1. The architecture diagram can be prepared as an AI-assisted editable SVG, with every label and connection checked manually, or correctly redrawn. Figure 5 displays channel-0 weights of 0.198, 0.200, 0.196, 0.198, and 0.200, which sum to 0.992. The combined rounding allowance for five three-decimal values is 0.0025. Rounding alone therefore does not explain the discrepancy. Please provide the unrounded gate tensor, actual plotting script, and corresponding source/configuration, checkpoint, and evaluation batch. The numerical figure should be regenerated from those recorded values and its annotations corrected.
Comment: Dear reviewer Yv99,
Comment: Dear reviewer Yv99,
We greatly appreciate your constructive comments which substantially help us to improve the manuscript. We are hopeful that our responses help address your concerns and provide a clearer understanding of our contributions.
We sincerely apologize for our late reply and would be grateful if you could review our responses. If you find that our clarifications have adequately addressed your concerns, we would greatly appreciate your consideration of increasing the score.
Once again, we sincerely thank you for your time and efforts and wish you all the best.
Best regards,
All authors