- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces LoopLUT, a real-time image-enhancement method that overcomes the iteratively predicts regional gates and residual LUTs from a fixed-resolution representation, then combines multiple LUT outputs through per-pixel weights to provide spatially adaptive correction. The authors evaluate LoopLUT on LCDP, MIT-Adobe FiveK, Mobile-Spec, and the LSUI underwater enhancement benchmark. The method achieves strong quantitative performance, including PSNR improvements of 1 dB+ on FiveK and almost 3 dB on Mobile-Spec over the respective SOTA baselines.
Critical strengths
-
Interesting and well-motivated architecture design. The partition-of-unity formulation provides a principled way to combine region-specific LUTs without repeatedly applying LUTs to intermediate full-resolution images. Moreover, the loop for decision reuse previous steps and leads to a constant constrained burden.
-
Strong empirical results on both performance and efficiency. LoopLUT reports the best PSNR and SSIM on LCDP, the best values across all four reported metrics on MIT-Adobe FiveK and Mobile-Spec, and competitive results on LSUI. It process 4K images at 16.23 ms on the reported RTX 4050 Laptop GPU (Table 3). The authors also report Thoughput and device memory.
Critical weaknesses
- More direct and intuitive ablation study. While the round-count ablation (Table 2) measures the combined effects of additional LUTs, spatial gates, and recurrent refinement. A controlled comparison against a non-recurrent multi-LUT architecture would be better to establish whether conditioning each round on the previous enhancement state provides a substantial advantage over one-shot spatial LUT prediction.
Questions for authors
- I also wonder how the resolution size for decision affect the accuracy and latency, especially for different target processing resolutions.
4 comments
Dear Reviewer,
Thank you again for your valuable feedback and time. We have carefully addressed your comments and questions in our rebuttal.
We would greatly appreciate it if you could take a moment to review our responses and let us know whether any concerns remain. We would be more than happy to provide further clarifications or additional evidence during the discussion period.
Thank you very much for your time and consideration!
Thank you again for your time and constructive feedback.
As only a few hours remain in the author–reviewer discussion period, we would greatly appreciate it if you could spare some time to review our rebuttal and revised manuscript. We have addressed your concerns through additional analyses, experiments, and clarifications.
We would be happy to clarify any remaining questions and sincerely welcome any further feedback.
Thank you for your time and consideration.
Thanks to the authors for their rebuttal. With added additional experiments on the multiple non-recurrent LUT, my concerns are mostly addressed. Thus, I will maintain my positive position on this submission. I hope the authors could add this experiment in their future versions to enhance the completeness of the work.
Response to Reviewer v9Uj: Feedback Ablation and Decision Resolution
Thank you for the encouraging assessment of our design, results, and efficiency. We agree that the two points you raised needed further experiments. We have added both to the revised manuscript, with the additions marked in purple. All table and figure references below refer to the revised version.
W1. A controlled comparison with a non-recurrent multi-LUT model
We agree that the round-count ablation alone does not isolate the contribution of feedback, since increasing the number of rounds also adds LUTs and spatial gates.
We therefore trained a non-recurrent three-LUT control. It retains the same backbone, basis LUTs, cascaded spatial gates, partition-of-unity structure, losses, training procedure, and 2.89 M parameters. The only change is that the gates and region statistics use the original low-resolution input instead of the previous round's low-resolution enhancement result. This keeps the LUT count and model capacity fixed while removing feedback from the updated image.
The results on the 218 LCDP test images at native resolution, averaged over seeds 42, 43, and 44, are:
The average PSNR gain over the non-recurrent control is 1.13 dB, with gains of +1.14, +1.03, and +1.23 dB for the three seeds. These results support the contribution of feedback within this architecture: later rounds benefit from observing the updated enhancement result, with the number of LUTs and parameters held fixed.
We have added this comparison to Section 4.4, “Effectiveness of feedback,” and Table 3. Appendix D.4, Table 8, and Figure 12 provide the per-seed and per-image results.
Q1. How decision resolution affects accuracy and latency at different output resolutions
We retrained LoopLUT at decision resolutions r = 128, 192, and 384 and compared them with the main model at r = 256. We fixed the seed at 42 and used the same decision resolution for training and inference. Accuracy is evaluated on LCDP; total latency is reported for outputs at 1620 × 1080 and 4K.
Latencies were measured on the same GPU in fp16, using the median of 60 consecutive runs after warm-up, and normalized to the r = 256 values in Table 4. For r = 512, we report latency only: training with batch size 16 requires about 7.1 GB of GPU memory, exceeding the 6 GB available on our GPU.
Increasing r from 128 to 384 improves PSNR by 0.78 dB. In particular, moving from the default r = 256 to r = 384 adds 0.38 dB, while total latency rises from 5.10 to 5.70 ms at 1620 × 1080 and from 16.23 to 17.55 ms at 4K.
For a fixed r, the decision stage operates at the same resolution regardless of the output size; the full-resolution execution stage accounts for the increase in cost with output size. The results therefore show how decision resolution can be used to trade additional latency for better accuracy, while the decision-stage latency remains a small part of the total at 4K.
We have added these results to Section 4.4, “Effectiveness of the decision resolution,” and Appendix D.5, Table 9.
Thank you again for these suggestions. They helped us test the role of feedback more directly and clarify the accuracy–latency trade-off.