- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper introduces a residual corrector algorithm for thermosphere density forecasting of satellite trajectories. The paper introduces an architecture which acts as a corrector on top of a DTM model (classical). The paper also implements a curated dataset including 5 satellites.
My main reason for rejecting the paper is venue fit. I think a domain journal/conference would be a much better fit. Also, I think the paper needs more work. For instance, I am not convinced the architecture does much beyond the DTM. An ablation study would quickly identify where most of the gain comes from.
Critical strengths
- it introduces a new problem and dataset for time series forecasting.
Critical weaknesses
Major
- I find the paper hard to follow even though I am familiar with time series forecasting.
- Neither the problem setting nor the method are carefully explained. For instance, how does the drag temperature model
- this problem is largely new and the ML community needs some context - what kind of time series is this, is it chaotic, why is this hard, what are the inputs, etc.
- Given that this problem is also very specific to an application domain, I would suggest the authors submit it to a domain journal, where there would be more interest for such a paper.
- I suspect that the heavy lifting is done by the DTM and that if the other baselines were to predict the residual as well, they might obtain a better performance. In this regard, I would like to see an ablation to conclusively prove that the architectural additions really did contribute to skill.
More:
- what is RSE? the acronym isn't introduced.
- also I see acronyms being used before being introduced.
- Acronyms that aren't parsable by a large portion of the ML community shouldn't be in the title
Questions for authors
- why the patch encoding? given that this is sequence data why not model it directly?
- is autoregressive prediction possible in this setting? I would hardly call this time series forecasting if only a few discrete time points are predicted.
- how much of the performance comes from your architecture and how much comes from effectively substracting the large-scale motion with the DTM? (I guess that is what it does). How do the metrics look like only on the residual? I suspect that the metrics are dominated by the DTM prediction.