Description
To determine whether we can get away with a low performance ADCS module, we need to gauge the strength of post-processing algorithms to correct for extreme jitter and motion blur in the acquired datacube.
TODO
- [ ] Find papers that describe algorithms for pushbroom pointing jitter and motion blur compensation.
- [ ] Add papers to ‣.
- [ ] Gauge the feasibility of developing such an algorithm in-house in terms of development time/practicality.
Artifacts
Some information on the XACT - From of the Papers Yongda shared: https://arxiv.org/pdf/1706.06967.pdf

Notes
- have not really come across the
Goals
- How well can we correct for jitter in 1 scan line
- How well can we correct for misaligned Scan Lines
Findings
- Goal 1, is movement while scanning 1 line. It leads to blur (motion blur)
- Often defined as Jitter in papers
- Is a result of the Pointing Stability of the ADCS system
- Goal 2, is for misaligned scan lines, leads to weird discontinuities in the images
- Is a result of the Point Accuracy of the ADCS system
Conclusions So Far - Oct 22 2022
- COTS or In House system → Data Processing must implement a jitter correction algorithm (motion -blur) and might need to correct for scan line
- Need more than 2 weeks (Maybe 1 month or 2) to look into misaligned scan line and jitter papers and figure out what is feasible
- lot’s of papers uses technique that are not feasible for us (high temporal resolution or stacked CCD)
- they usually correct for very small jitter → < 1 pixel