Skip to content

Configuration#

The RadarImager provides many configuration parameters. For best results, adapt them step by step to your installation and use case.

Configuration is not persistent

After a restart or power outage, the RadarImager does not retain previously configured parameters.

Configuration structure#

The configuration is organized as a hierarchical tree structure, with each parameter represented as a node. The tree is split into four main sections: taskMeasurement, taskImaging, taskVision and taskOutput.

To modify a parameter, navigate to the corresponding node in the tree. Parameter values are transmitted as strings.

When using parameters in code, build the full dotted path from the hierarchy shown in this documentation. For example, layerSelection.indexes under taskImaging becomes taskImaging.layerSelection.indexes. Depending on the writable feature exposed by the API, the exact component name may include a final field such as .Values. If you need the precise writable component name, copy it from Impact Control Center (ICC) as described in Python GEV Client.

Where to start

If you want to get a first working image quickly, follow the Generate First Image guide.

Below is an overview of the tree structure with direct links to parameter descriptions:

taskMeasurement#

taskMeasurement.measurement.radarSystem

taskImaging#

taskImaging

taskVision#

taskVision

taskOutput#

taskOutput

Update of the RadarImager configuration#

When parameters are updated, the RadarImager instantly recalculates the image using the most recent measurement data. However, a subset of measurement parameters deviates from this behavior and only takes effect after a new measurement.

If one of these parameters is changed, the RadarImager temporarily pauses image recalculation for any other parameter changes until a new measurement is performed. The changes are not discarded and are applied automatically to the next measurement.

Configuration limitations#

In some scenarios, the RadarImager's computational limits can be exceeded (typically when multiple high-impact parameters are set too high). This usually manifests as frame drops.

To resolve this, reduce the most performance-critical parameters:

For help assessing and optimizing performance, refer to the Performance Estimation Usage Guide and the Performance Estimation Tool.