Deep learning phase recovery: data-driven, physics-driven, or combining both?

Kaiqiang Wang, Edmund Y. Lam
4/1/2024
eess.IVcs.LGphysics.optics

Official code: kqwang/DLPR (53 stars, MIT, last commit 2025-08-28).

Abstract

Phase recovery, calculating the phase of a light wave from its intensity measurements, is essential for various applications, such as coherent diffraction imaging, adaptive optics, and biomedical imaging. It enables the reconstruction of an object's refractive index distribution or topography as well as the correction of imaging system aberrations. In recent years, deep learning has been proven to be highly effective in addressing phase recovery problems. Two most direct deep learning phase recovery strategies are data-driven (DD) with supervised learning mode and physics-driven (PD) with self-supervised learning mode. DD and PD achieve the same goal in different ways and lack the necessary study to reveal similarities and differences. Therefore, in this paper, we comprehensively compare these two deep learning phase recovery strategies in terms of time consumption, accuracy, generalization ability, ill-posedness adaptability, and prior capacity. What's more, we propose a co-driven (CD) strategy of combining datasets and physics for the balance of high- and low-frequency information. The codes for DD, PD, and CD are publicly available at https://github.com/kqwang/DLPR.

View on arXivView PDF

Code Implementations(1)

kqwang/DLPROfficial100%
MIT

Example code for data-driven and physics-driven deep learning phase recovery

534PythonMar 21, 20241 years agoMIT
deep-learningphase-recovery

Similar Papers

Cite this paper

@article{wang2024deep,
  title  = {Deep learning phase recovery: data-driven, physics-driven, or combining both?},
  author = {Kaiqiang Wang and Edmund Y. Lam},
  year   = {2024},
  eprint = {2404.01360},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2404.01360v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2404.01360.svg)](https://codeofpaper.com/paper/2404.01360)

Discussion