Get desktop application:
View/edit binary Protocol Buffers messages
Realism configuration for ER-Force simulator this message is stored in human readable form for saved ui settings therefore do NOT modify field names without changing them in the config files
Used in:
Standard deviation of the gaussian noise applied to the ball position [m]
Standard deviation of the gaussian noise applied to the robot position [m]
Standard deviation of the gaussian noise applied to the robot angle [rad]
Standard deviation of the gaussian noise applied to reported ball area [pixel]
Whether or not to simulate the ball being invisible when the view from the camera to it is blocked by a robot. It also simulates the slight perceived motion of the ball when it is partially overshadowed by a robot as the visible center of the ball shifts
The occlusion threshold at which the ball will no longer be visible [0-1] A value of 0 would make the ball always visible
The overlap of the visible range of the different cameras [m] For example: if there are two cameras and the overlap value is 0.5m then the ball is visible in both cameras between -0.5 and 0.5 meters from the centerline
With this probability, additional erroneous ball detections are added at the edge of a robots dribbler (to emulate the red break beam lights sometimes being visible from the camera). [detections/s/robot]
How much the reported camera positions should deviate from the actual camera positions used for ball projection etc. [m]
The percentage of robot control commands that are "lost in transit" [0-1]
The percentage of robot reply messages that are "lost in transit" [0-1]
The percentage of times the ball is erroneously not "seen" by the camera [0-1]
Sending out the vision data is delayed by this time after capturing the positions [ns]
The difference between the reported t_capture and t_sent of the vision frame [ns]
If false, 'glue' the ball during dribbling
Simulates an offset of all reported object positions (robots, ball) at this magnitude [m]
Fixed-Loss model for chipped balls. Uses fixed damping factors for xy and z direction per hop.
Used in:
Chip kick velocity damping factor in XY direction for the first hop
Chip kick velocity damping factor in XY direction for all following hops
Chip kick velocity damping factor in Z direction for all hops
Two-Phase model for straight-kicked balls. There are two phases with different accelerations during the ball kicks: 1. Sliding 2. Rolling The full model is described in the TDP of ER-Force from 2016, which can be found here: https://ssl.robocup.org/wp-content/uploads/2019/01/2016_ETDP_ER-Force.pdf
Used in:
Ball sliding acceleration [m/s^2] (should be negative)
Ball rolling acceleration [m/s^2] (should be negative)
Fraction of the initial velocity where the ball starts to roll
Represents a field marking as a circular arc segment represented by center point, a start angle, an end angle, and an arc thickness.
Used in:
Name of this field marking.
Center point of the circular arc.
Radius of the arc.
Start angle in counter-clockwise order.
End angle in counter-clockwise order.
Thickness of the arc.
The type of this shape
Represents a field marking as a line segment represented by a start point p1, and end point p2, and a line thickness. The start and end points are along the center of the line, so the thickness of the line extends by thickness / 2 on either side of the line.
Used in:
Name of this field marking.
Start point of the line segment.
End point of the line segment.
Thickness of the line segment.
The type of this shape
Used in: ,
Used in:
Used in:
Used in:
Used in:
this is only used for replay at the moment
A 2D float vector.
Used in: ,