- Rating
- 1
- Confidence
- 3(−1)
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
The manuscript considers all-in-one open world image restoration as a multi-phase synthesis and verification pipeline executed on a unified multimodal model. Built on multiple open source models, the framework integrates these models via a semantic understanding, constrained discrete denoising and critic-guided self-correction four stage close loop. Experiments part demonstrate advancement compared to other AiO methods in multiple no-reference metrics.
Critical strengths
- Consistently integrates multiple existing work into a unified pipeline for image restoration usage.
- Converting pixel-level error maps predicted by a critic into discrete token-space re-masking masks intuitively performs localized refinement.
Critical weaknesses
- Each module belongs to an off-the-shelf component. Show-O, MAGVIT-V2, MaskGIT and Swin-UNet these four part all come from existing methods which present the job simply as tool ensemble. Additional, the "restore-assess-refine" loop has been explored in recent image restoration work, such as RAR (CVPR 26). The overall approach just integrates existing methods and lacks novelty.
2.The method is trained on the GenDS dataset. However, the paper explicitly claims that all baselines are evaluated without fine-tuning on GenDS. Most critically, GenDeg, which proposed the GenDS benchmark is omitted as a baseline. In the GenDeg paper, baselines such as PromptIR, NAFNet and Swin are trained with GenDS which demonstrate drastically improved out-of-distribute performance. The experimental setup is unfair to the other baselines, making the results unmeasurable.
Questions for authors
- Since this work relies directly on the GenDS dataset proposed by GenDeg, why are GenDeg and other recent methods (2025/2026) not being compared?
- Is it fair to remove all the full-reference metrics in Tables 1 and 3, given that most of these datasets contain paired GT-LQ data?
- The inference stage relies on a loop. Could the wall-clock latency (seconds per image) or other efficacy metrics be compared to those of one-shot method on the same computation resource?