← Back to tutorial library

WAVERAY · Examples & Tutorials

Richardson-Lucy Deconvolution

Run a Richardson-Lucy deconvolution workflow and inspect the restored output.

Learn how to use WaveRay for Richardson-Lucy Deconvolution with real, manually matched screenshots. This tutorial covers setup, execution, result interpretation and practical checks.

What this tutorial covers

Run a Richardson-Lucy deconvolution workflow and inspect the restored output.

Before you start:You need access to the product and should ideally follow the tutorial using your own real parameters or data. The screenshots below were manually rematched to avoid the image/topic mismatches seen in the previous version.
Richardson-Lucy Deconvolution - Open the relevant module and confirm the starting state.
Open the relevant module and confirm the starting state.
Richardson-Lucy Deconvolution - Configure the key inputs that match the topic.
Configure the key inputs that match the topic.
Richardson-Lucy Deconvolution - Run the workflow and inspect the result/status.
Run the workflow and inspect the result/status.

Step-by-step workflow

1Open the module

Open Richardson-Lucy Deconvolution. Confirm that the visible page really matches the tutorial topic before changing any settings.

2Configure the input

Prepare and check the input image, PSF/deconvolution settings and iteration controls.

3Run and watch the status

Load the data, execute the deconvolution and examine the restored image. Watch the visible status, plot or log area while the workflow is running.

4Inspect the result

Pay special attention to the restored output and the settings used to produce it.

5Verify and iterate

Too many iterations can amplify noise, so start with a small iteration count. Change one meaningful parameter and rerun so you can verify whether the output changes in the expected direction.

How to read the result

  • The main output of this workflow is the restored output and the settings used to produce it.
  • Read the result together with the exact inputs used for the run; a screenshot alone rarely tells the whole story.
  • Too many iterations can amplify noise, so start with a small iteration count.

Troubleshooting & practical tips

  • If nothing changes, first confirm that the correct module is open.
  • If the output looks unrealistic, check units, field mapping and input scale first.
  • For comparisons, change one key parameter at a time whenever possible.