← Back to tutorial library

WAVERAY · Examples & Tutorials

Android Gaussian Beam ABCD

Enter q-parameter and system values on Android to inspect Gaussian Beam ABCD results.

Learn how to use WaveRay for Android Gaussian Beam ABCD with real, manually matched screenshots. This tutorial covers setup, execution, result interpretation and practical checks.

What this tutorial covers

Enter q-parameter and system values on Android to inspect Gaussian Beam ABCD results.

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.
Android Gaussian Beam ABCD - Open the relevant module and confirm the starting state.
Open the relevant module and confirm the starting state.
Android Gaussian Beam ABCD - Configure the key inputs that match the topic.
Configure the key inputs that match the topic.
Android Gaussian Beam ABCD - Run the workflow and inspect the result/status.
Run the workflow and inspect the result/status.

Step-by-step workflow

1Open the module

Open Gaussian Beam ABCD. Confirm that the visible page really matches the tutorial topic before changing any settings.

2Configure the input

Prepare and check the input-beam values and the system-matrix/propagation parameters.

3Run and watch the status

Adjust the parameters and inspect output beam waist, radius and related results. Watch the visible status, plot or log area while the workflow is running.

4Inspect the result

Pay special attention to Gaussian Beam ABCD results and the plotted response.

5Verify and iterate

If the result changes unexpectedly, first make sure all beam and system parameters use consistent units. 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 Gaussian Beam ABCD results and the plotted response.
  • Read the result together with the exact inputs used for the run; a screenshot alone rarely tells the whole story.
  • If the result changes unexpectedly, first make sure all beam and system parameters use consistent units.

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.