Skip to Content

Wiki source code of Ball Physics

Version 10.1 by stu104225 on 2020/03/07 13:20
Hide last authors
stu104225 7.1 1 The **ball physics model**'s main objective is to provide a point in time to the controller, when the ball is predicted to be hittable, in order to not let the ball fall into the drain.
stu104225 5.1 2
stu104225 1.1 3 \\
4
stu104225 7.1 5 \\
stu104225 1.1 6
7
stu104225 7.1 8
stu104225 5.1 9 {{toc/}}
10
stu104225 4.1 11 == Ball trajectory ==
stu104225 1.1 12
stu104225 5.1 13 ----
14
stu104225 8.1 15 The trajectory of a ball can be modeled to be parabolic. From two point //p// and //p_old// with corresponding timestamps, the velocity //v// is computed.
stu104225 9.1 16 For a future point in time //t//, with //t=0 //being the timestamp of// p//, we can then approximately approximately predict the corresponding ball position using the following formulas.
stu104225 4.1 17
stu104225 8.1 18 [[image:attach:Bildschirmfoto von 2020-03-07 12-21-22.png]]
stu104225 7.1 19
stu104225 9.1 20 The incline of the playfield causes a vertical acceleration, which is modeled via a graviatational pull with the factor //g = sin(6°) * 9.81 m/s²//.
21 The value of 6° is the incline of the playfield  measured on the physical device.
22
stu104225 10.1 23 == Prediction ==
24
25 ----
26
27 TODO
28
stu104225 1.1 29 == Configuration ==
30
stu104225 5.1 31 ----
stu104225 1.1 32
stu104225 5.1 33 === Prediction parameters ===
34
stu104225 6.1 35 (% class="wrapped" %)
stu104225 5.1 36 |=(((
37 Parameter
38 )))|=(((
39 Description
40 )))|=(((
41 Default value
42 )))
43 |(((
44 PREDICTION_FRAME
45 )))|(((
46 window size for prediction - How far
47
48 into the future are predctions calculated at most.
49 )))|(((
50 70ms
51 )))
52 |(((
53 PREDICTION_STEP_SIZE
54 )))|(((
55 size of the steps for the forward search
56 )))|(((
57 10ms
58 )))
59 |(((
60 REFINEMENT_FACTOR
61 )))|(((
62 The prediction step size for the reverse search is
63 PREDICTION_STEP_SIZE divided by REFINEMENT_FACTOR.
64 )))|(((
65 10
66 )))
67
stu104225 6.1 68 When setting the PREDICTION_FRAME keep in mind, that predictions, that reach multiple frames into the future, are likely to be overwritten, when new frames arrive and new predictions are calculated.
69 Nevertheless it is reasonable to calculate predictions beyond the next frame in case a ball is not recognized on the next frame.
stu104225 5.1 70
stu104225 6.1 71 With the default values up to 7 predictions are calculated if the ball is not predicted to be in flipper range roughly within the next two frames.
stu104225 5.1 72
stu104225 6.1 73 The REFINEMENT_FACTOR is also the worst case number of predictions calculated during the reverse search part of the prediction process.
stu104225 5.1 74
75 \\
76
77 === Flipper range ===
78
stu104225 4.1 79 The model of the area, where the the flippers can hit a ball is computed from a set of five points. These points are set to real world coordinates in meter
stu104225 1.1 80
stu104225 4.1 81 and should not need further adjustment after the camera is correctly calibrated (see [[doc:World Coordinate System]]).
82
stu104225 5.1 83 The values for the left flipper are set to be symmetrical.
84
stu104225 1.1 85 [[image:attach:physics_points.png]]
86
stu104225 5.1 87 (% class="wrapped" %)
stu104225 4.1 88 |=(((
89 Point#
90 )))|=(((
91 Description
92 )))
93 |(((
94 1
95 )))|(((
96 center point of the circle that the flippers tip moves o
97 )))
98 |(((
99 2
100 )))|(((
101 highest point a ball can be at when it hits the resting flipper
102 )))
103 |(((
104 3
105 )))|(((
106 lowest point a ball can be at when it hits the resting flipper
107 )))
108 |(((
109 4
110 )))|(((
111 lowest point a ball can be at when it hits the fully triggered flipper
112 )))
113 |(((
114 5
115 )))|(((
116 highest point a ball can be at when it hits the fully triggered flipper
117 )))
stu104225 1.1 118
119 \\
120
stu104225 5.1 121 From these points an area, where the ball is deemed to be hittable, is computed.
stu104225 4.1 122
stu104225 1.1 123 [[image:attach:physics2.png]]
124
125 \\
126
127 === Inlane Area ===
128
stu104225 5.1 129 Since the trajectory prediction does not consider collisions in general, we need a different kind of predictions for the inlanes,
130 i.e. the path feeding a falling ball from the playfield to the flippers, behind the slingshot.
131 A ball is considered to be in an inlane, when it is in a rectangualar area, with one edge given by the begin of the flipper
132 and the other by a point at highest, outermost position of the angled part of the inlane.
stu104225 4.1 133
stu104225 6.1 134 In this area the vertical accelleration is deactivated in the prediction, since it would cause the prediction to assume the would slide into the wall.
135 Though in reality the still is some accelleration, a simple linear prediction has shown to be practical in this less critical area.
136
stu104225 1.1 137 [[image:attach:physics_inlane.png]]