← Back to tutorial library

6G RESEARCH STUDIO · Examples & Tutorials

ISAC Range-Doppler Research Pipeline

Walk through the ISAC workflow from setup to the final range-Doppler result.

Learn how to use 6G Research Studio for ISAC Range-Doppler Research Pipeline with real, manually matched screenshots. This tutorial covers setup, execution, result interpretation and practical checks.

What this tutorial covers

Walk through the ISAC workflow from setup to the final range-Doppler result.

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.
ISAC Range-Doppler Research Pipeline - Open the relevant module and confirm the starting state.
Open the relevant module and confirm the starting state.
ISAC Range-Doppler Research Pipeline - Configure the key inputs that match the topic.
Configure the key inputs that match the topic.
ISAC Range-Doppler Research Pipeline - Run the workflow and inspect the result/status.
Run the workflow and inspect the result/status.

Step-by-step workflow

1Open the module

Open ISAC Research from Radio & Sensing. Confirm that the visible page really matches the tutorial topic before changing any settings.

2Configure the input

Prepare and check the imported data, waveform/physical-axis parameters and processing options such as CFAR/MUSIC.

3Run and watch the status

Configure the ISAC pipeline and run the range-Doppler analysis. Watch the visible status, plot or log area while the workflow is running.

4Inspect the result

Pay special attention to the range-Doppler map together with key range/velocity metrics.

5Verify and iterate

This page was manually corrected so the final screenshot stays inside the ISAC workflow. 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 range-Doppler map together with key range/velocity metrics.
  • Read the result together with the exact inputs used for the run; a screenshot alone rarely tells the whole story.
  • This page was manually corrected so the final screenshot stays inside the ISAC workflow.

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.