Changes for page Ball Physics

Last modified by Soeren Domroes on 2025/01/30 12:18

From version 10.1
edited by stu104225
on 2020/03/07 13:20
Change comment: There is no comment for this version
To version 5.1
edited by stu104225
on 2020/03/04 17:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,9 @@
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.
1 +The **ball physics model** is meant to do things ... [TODO]
2 2  
3 3  \\
4 4  
5 -\\
6 6  
7 7  
8 -
9 9  {{toc/}}
10 10  
11 11  == Ball trajectory ==
... ... @@ -12,20 +12,9 @@
12 12  
13 13  ----
14 14  
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.
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.
13 +The trajectory of a ball can be modeled to be parabolic.
14 +\\\\\\like so: .... [TODO]
17 17  
18 -[[image:attach:Bildschirmfoto von 2020-03-07 12-21-22.png]]
19 -
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 -
23 -== Prediction ==
24 -
25 -----
26 -
27 -TODO
28 -
29 29  == Configuration ==
30 30  
31 31  ----
... ... @@ -32,7 +32,6 @@
32 32  
33 33  === Prediction parameters ===
34 34  
35 -(% class="wrapped" %)
36 36  |=(((
37 37  Parameter
38 38  )))|=(((
... ... @@ -65,12 +65,11 @@
65 65  10
66 66  )))
67 67  
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.
54 +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.
70 70  
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.
56 +\\
72 72  
73 -The REFINEMENT_FACTOR is also the worst case number of predictions calculated during the reverse search part of the prediction process.
58 +So this number is also the worst case number of predictions calculated during the reverse search part of the prediction process.
74 74  
75 75  \\
76 76  
... ... @@ -131,7 +131,4 @@
131 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 132  and the other by a point at highest, outermost position of the angled part of the inlane.
133 133  
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 -
137 137  [[image:attach:physics_inlane.png]]
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -71401663
1 +71401643
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/PP18/pages/71401663/Ball Physics
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/PP18/pages/71401643/Ball Physics