Radar/camera advanced detection and tracking

Developing radar/camera-based advanced detection and tracking algorithms in the context of applications for smart urban mobility - generating inputs for simulators; covering potentially problematic situations; testing accuracy and reliability of detectors; testing perception robustness under uncertainty; integrating simulation-based testing in continuous integration contexts

Id Each requirement and test-case has a unique ID with running numbers based on the corresponding use case. In order to avoid name clashing between identifiers of requirements and test-cases, which can potentially lead to confusion, the letter ‘R’ is used to denote a requirement ID and the letters ‘TC’ are used to denote a test-case ID. For example, UC2_R_1 is the ID of the first requirement of use case 2, and UC3_TC_2 is the ID of the second test-case of use case 3.

Evaluation Scenario Textual Description Each evaluation scenario has a concise description, which is limited to one sentence to keep it as concise as possible.

Evaluation Scenario Rationale Risk he rationale / risk contains an explanation of what needs to be evaluated, referring to the “What” stated in the work plan.

Evaluation Scenario Owner The owner is the partner acting as the main contributor to this evaluation scenario

Evaluation Scenario Requirements

Evaluation Scenario Requirements List

V&V Methods

V&V Methods List of the methods used in this evaluation scenario

VALU3S Framework

Evaluation Environment Type Type of environment where the method is applied. It can be more than one type of environment.(Dimension 1)

Evaluation Type Type of evaluation performed with that method. If a method is hybrid, more than one type can be selected.(Dimension 2)

Type of Component Under Evaluation Type of components that can be evaluated with that method. It can be more than one type.(Dimension 3)

Evaluation Stage The evaluation stage where the method is used.(Dimension 5)

Purpose of the Component Under Evaluation The type of purpose that can be evaluated by a method. It can be more than one type.(Dimension 6)

Type of Requirement Under Evaluation The type of requirements that a method is able to evaluate. It can be more than one type.(Dimension 7)

Evaluation Performance Indicator The type of evaluation criteria or KPI that a method is able to improve. It can be more than one type.(Dimension 8)

Contents

UC1_R_1

Road users counting accuracy should be at least 99%

UC1_R_2

Speed measurement error shall be within 2kph for speed up to 100kph and 2% for speed over 100kph.

UC1_R_3

System should keep its qualities even in bad/tricky lighting and weather conditions.

UC1_R_4

Radar sensor automatic configuration/calibration should provide good estimation of installation parameters (azimuth, elevation, rotation - within 1 degree accuracy, mounting height - within 10cm accuracy) including detection of manipulation with the sensor.

UC1_R_5

Robustness under sensor faults

UC1_R_6

System shall properly detect and track two vehicles going side by side at the very similar relative speed.

UC1_R_7

Radar sensor shall detect and track weak objects (in terms of radar signal power reflection) such as cyclists in the presence of strong reflectors such as vehicles including being able to classify them.

UC1_R_8

System shall detect and track slowing down traffic including detection of presence of static/stopped vehicles (even crashes which are definitely safety issue).

UC1_R_9

System shall detect and track vehicle going at very high speed including less than 2% speed error.

UC1_R_10

System shall detect and track driving in opposite direction (wrong way - safety issue).