Weaknesses
## "Foundation" model
The term foundation model feels very misplaced in this paper, and more like a term added as an afterthought because of the current trends in the deep learning community.
Generally, foundation models are models considered to be trained on a very large amount of data, and not for a particular task. The model is then being fine tuned on different down-stream tasks for particular applications. This is not the case here, as the model is not trained on multiple tasks, but rather trained to predict multiple granularities, which is one task. Additionally, the model is suited for this particular task, but could hardly be applied to something different, given the specificity of the application.
The paper reads as if, initially, the letter "F" in Sea Ice Foundation Model, was supposed to be "Fusion", but then changed last minute to follow a trend. The model is never argued as a foundation model, and save for the name, the term is never used. The concept of fusion on the other hand, is largely covered and mentioned multiple times throughout the paper.
I would strongly suggest changing Foundation to Fusion.
## Related Work
Line 137: "temporal information inherent in sea ice modeling can not be fully exploited". I would argue that LSTM combined with CNNs can actually extract the spatio-temporal information quite well. Maybe not particularly in Sea Ice modeling, but in other fields there is a slue of models making use of the spatio-temporal information, be it transformers or combined LSTM/CNN architectures (c.f. Yu et al. 2024, Giezendanner et al. 2023, Boulila et al. 2021, etc...).
## Temporality
### Terms
The temporalities are a bit all over the place. With a paper like this, where the temporal resolution is central to understanding the work, I feel like the wording is particularly important.
Line 186 explains the granularities relatively well: daily, weekly average, and monthly average. But after that, the terms get a bit muddy:
- Line 174: "7 days, 8 weeks’ averages and 6 months’ averages". My understanding is that these are the time steps. You take 7 days of daily data as input, 8 weeks of weekly average and 6 month of monthly average. Just reading the figure, this is not clear, and I had to piece this together from the text.
- Line 245: "We propose to jointly model three granularities that cover sub-seasonal to seasonal scale, i.e., 7 days, 8 weeks averages, and 6 months averages". Here the confusion is quite big. Area you taking 8 time steps of weekly average, or an average over 8 weeks? Same for month. I think I got the gist, but this is far from clear and I had to go over the paper multiple times to piece it together.
- Table 1 (line 358): Here it gets worse. Lead Times: 7 days (daily). Intuitively I read this as the 7 days lead time, temporal resolution of 1 day, i.e. the values of the 7th day. But I'm not sure this is right, since you mention you forecast at all time steps, so is the result the error of the 7th day, or the cumulative/average error over the 7 days? Same comment for 8 weeks and 6 month.
I think the paper would profit a lot from a figure describing the temporalities. Show exactly what the inputs and outputs are, and how you define the terms used in the rest of the paper.
### Number of Time steps per granularity
I might have missed it, but it is unclear to me if the number of time steps per granularity is justified anywhere.
Why take only the seven next days? Why not the 6 months of daily inputs as a whole? The multi-granularity approach probably makes the model lighter, but a model with 6 month of daily inputs could very well perform as well as the multi-granularity one.
Alternatively, one could also model the daily output, with a moving window, and average over the other other granularities.
## Dataset
It is not totally clear to me, from section 4.1, how big the dataset is. A rough estimation of the daily data from 1978 to 2013 for the training data yields ~13'000 training samples), but how were the different temporalities sampled? Is there a moving average? Does that mean the validation set has 365 points (assuming 6 months at the begining and the end have to be blocked for the monthly average)? And the test set 2,555?
## Results
Table 1: The results for the 7 days daily lead time are better, but almost seem marginal. The table is missing units, but assuming it's percentage, is a difference in RMSE of 0.0061 really significant?
The comparisons to 45 Days and 90 Days are hard without having the output of the model. Would it be possible to run the model with 45 and 90 days of daily inputs to compare?
Additionally, an ablation study on the number of time steps per granularity would be interesting.
The results on the 6 months seem more significant.
The ablation study "Effectiveness of multi-granularity representation" is interesting, but it would also be interesting to see the results for a single granularity aggregated on the other granularity. For example: daily forecast, aggregated over 6 months.
## Conclusions
The conclusion is very minimal, and would profit from a bit more of a discussion. What advancements do the results of this model bring?
## Minor comments
Line 44 and 131: "However, numerical and statistical models usually rely on high-performance computing on CPU clusters and often lead to complex debugging processes and uncertain parameterization" and "tend to result in complex debugging processes and uncertain parameterization". That might be true, nevertheless Deep learning methods can also have large debugging processes as well as uncertain parameterizations.
## Grammar comments
Line 144: move "while" to the beginning of the sentence.
Line 146: remove "in the vision community"
## Comments on figures
Line 063: "(a)" should be bold
Line 173: It would be helpful to have the numbers mentioned in the caption reflected in the figure (e.g. (1), shared spatial encoder, (2), ... (3), ...)
Figure 6: set the value of 0 to the middle, make sure it is on the white part, and set the limits of the color bar to be the same up and down.
Figure 7: use a shared x axis for each column, and a shared y axis for each line