Biases pre-sets
Prophesee Event-Based sensors can be tuned for optimal functioning in a specific applications and in a particular environment condition by adjusting the sensor settings so-called biases.
On this page we provide several biases pre-sets for different applications. These pre-sets should be seen as a starting point for bias tuning for a particular application and not as a final solution. The final solution will depend on many factors and here we provide only a generic idea.
Biases pre-sets for GenX320 MP sensor
| Application | Speed | bias_diff | bias_diff_off | bias_diff_on | bias_fo | bias_hpf | bias_refr | What is seen |
| Min recommended* | Low | 41 | 19 | 24 | 19 | 0 | 0 | |
| Max recommended* | High | 51 | 50 | 60 | 39 | 127 | 127 | |
| Default* | Medium | 51 | 28 | 25 | 34 | 40 | 10 | Moving / changing objects |
| Low-light detection | Low | 51 | 19 | 24 | 19 | 0 | 10 | Moving / changing objects |
Drone tracking | Medium | 51 | 40 | 40 | 29 | 0 | 82 | Moving / changing objects |
| High-speed motion, Object counting, PSM (Particle Size Measurement) | High | 51 | 26 | 37 | 38 | 74 | 25 | Fast moving objects |
| LED tracking** | High | 51 | 45 | 55 | 50** | 127 | 0 | High-frequency LED only |
| Active marker detection** | High | 51 | 127** | 78** | 50** | 127 | 0 | Active marker only |
* Based on Metavision SDK v5.x
** Outside of the recommended range
Biases pre-sets for IMX636 sensor
Please note that all IMX636 sensors are individually trimmed during the manufacturing process, resulting in sensor-specific factory biases settings. In Metavision SDK, all relative biases are set to 0 by default, but these values correspond to different absolute biases settings depending on the sensor.
Factory biases settings can be found in the log when the log level is set to TRACE. As factory settings can vary between sensors, the amount of background activity observed in a static dark scene may also vary.
The biases pre-sets below should therefore be considered as examples of relative biases settings. Their effect depends on the sensor's factory settings, and additional adjustments may be required for optimal results.
| Application | Speed | bias_diff | bias_diff_off | bias_diff_on | bias_fo | bias_hpf | bias_refr | What is seen |
| Min recommended* | Low | -25 | -35 | -85 | -35 | 0 | -20 | |
| Max recommended* | High | 23 | 190 | 140 | 55 | 120 | 235 | |
| Default* | Medium | 0 | 0 | 0 | 0 | 0 | 0 | Moving/changing objects |
| High-speed motion, Object counting, PSM (Particle Size Measurement) | High | 0 | 16 | 50 | 55 | 110 | 0 | Fast moving objects |
| Active marker detection** | High | 0 | 180 | 60 | 30 | 140** | 0 | Active marker only |
* Based on Metavision SDK v5.x
** Outside of the recommended range
Applying the biases pre-sets
Each biases pre-set can be downloaded as a *.bias or *.json file from the attachments to this page.
Each biases pre-set can be applied in one of the following ways:
- via a command line option "-j" followed by a *.json configuration file:
- metavision_viewer -j genx320_lowlight.json
- via a command line option "-b" followed by a *.bias file:
- metavision_viewer -b genx320_lowlight.bias
- in the code using Metavision API (in C++ or Python)
As a Prophesee customer, get access to your personal ticketing tool, application notes, product manuals, SDK Download Center and more resources.