Difference between revisions of "Thread:User talk:Wompi/Skipped Turns ... what to know about?/reply (9)"
Jump to navigation
Jump to search
(new data and some thoughts) |
|||
Line 1: | Line 1: | ||
Hmm this is the stripped output of the skipped turn: | Hmm this is the stripped output of the skipped turn: | ||
− | + | Finally i got a skipped turn (288) and it works like we thought it must work. The whole turn got no events and even the loop got no turn, so no print out. On the other hand i think i found your bug. If you look at the table below you can see that the robot is advanced in his skipped turn and the next turn has the 15.98 distance difference. this should be 8 or less because of the skipped turn. | |
− | |||
− | |||
− | |||
− | + | To me it looks right now there are three bugs | |
− | + | *skipped robots advance just like in a normal turn but they get no events | |
− | + | *skipped robots get events and advance just normal (so it is just a message with no consequences) | |
− | + | *robots get no skipped events at all even if they are way out of time | |
− | + | ||
− | x | + | [285] 121000 0 [285][285] 49000 [270.78095:748.65046] - [1.41372] // ([x:y] - [heading]) |
− | + | [286] 130000 0 [286][286] 54000 [262.87944:747.39899] - [1.41372] | |
− | + | SYSTEM: TassieDevil* (1) skipped turn 287 | |
− | + | [287] 16716000 16 [287][287] 16582000 [254.97794:746.14751] - [1.41372] | |
− | + | [289] 131000 0 [289][289] 55000 [239.28147:743.09643] - [1.34390] | |
− | + | ||
− | + | {| border=1 width=100% | |
− | + | |- | |
− | + | | turn || 286 || 287 || 288 || 289 | |
− | + | |- | |
− | + | | energy || 160.07883925169597 || 160.07883925169597 || 160.07883925169597 || 157.07883925169597 | |
− | + | |- | |
− | + | | x || 262.8794433297025 || 254.9779366049414 || 247.07642988018029 || 239.28146936189842 | |
− | + | |- | |
− | + | | y || 747.3989879466453 || 746.1475122263234 || 744.8960365060016 || 743.0964280712507 | |
− | + | |- | |
− | + | | bodyHeading || 1.4137166941154065 || 1.4137166941154067 || 1.4137166941154067 || 1.3439035240356334 | |
− | + | |- | |
− | + | | gunHeading || 1.1884119094971828 || 1.161216370645719 || 1.161216370645719 || 1.135682848864048 | |
− | + | |- | |
− | + | | radarHeading || 1.7448331266273467 || 0.9322394243784347 || 0.5360878333247008 || 1.295952474940478 | |
− | + | |- | |
− | + | | gunHeat || .09999999999999981 || 0.0 || 0.0 || 1.5 | |
− | + | |- | |
− | + | | veocity || -8.0 || -8.0 || -8.0 || -8.0 | |
− | + | |- | |
− | + | | getX() || 262.87944 || 254.97794 || skipped || 239.28147 | |
− | + | |- | |
− | + | | getY() || 747.39899 || 746.14751 || skipped || 743.09643 | |
− | + | |- | |
− | + | | getHeadingRadians() || 1.41372 || [1.41372 || skipped || 1.34390 | |
− | + | |- | |
+ | | delta dist || ... || 8.0 || '''should be skipped''' || '''15.98''' | ||
+ | |} | ||
+ | |||
+ | Sorry i just edited my former post .. to save space. | ||
Yep onStatus(..) is always the first event and holds every state of your robot. | Yep onStatus(..) is always the first event and holds every state of your robot. |
Latest revision as of 20:23, 11 June 2012
Hmm this is the stripped output of the skipped turn:
Finally i got a skipped turn (288) and it works like we thought it must work. The whole turn got no events and even the loop got no turn, so no print out. On the other hand i think i found your bug. If you look at the table below you can see that the robot is advanced in his skipped turn and the next turn has the 15.98 distance difference. this should be 8 or less because of the skipped turn.
To me it looks right now there are three bugs
- skipped robots advance just like in a normal turn but they get no events
- skipped robots get events and advance just normal (so it is just a message with no consequences)
- robots get no skipped events at all even if they are way out of time
[285] 121000 0 [285][285] 49000 [270.78095:748.65046] - [1.41372] // ([x:y] - [heading]) [286] 130000 0 [286][286] 54000 [262.87944:747.39899] - [1.41372] SYSTEM: TassieDevil* (1) skipped turn 287 [287] 16716000 16 [287][287] 16582000 [254.97794:746.14751] - [1.41372] [289] 131000 0 [289][289] 55000 [239.28147:743.09643] - [1.34390]
turn | 286 | 287 | 288 | 289 |
energy | 160.07883925169597 | 160.07883925169597 | 160.07883925169597 | 157.07883925169597 |
x | 262.8794433297025 | 254.9779366049414 | 247.07642988018029 | 239.28146936189842 |
y | 747.3989879466453 | 746.1475122263234 | 744.8960365060016 | 743.0964280712507 |
bodyHeading | 1.4137166941154065 | 1.4137166941154067 | 1.4137166941154067 | 1.3439035240356334 |
gunHeading | 1.1884119094971828 | 1.161216370645719 | 1.161216370645719 | 1.135682848864048 |
radarHeading | 1.7448331266273467 | 0.9322394243784347 | 0.5360878333247008 | 1.295952474940478 |
gunHeat | .09999999999999981 | 0.0 | 0.0 | 1.5 |
veocity | -8.0 | -8.0 | -8.0 | -8.0 |
getX() | 262.87944 | 254.97794 | skipped | 239.28147 |
getY() | 747.39899 | 746.14751 | skipped | 743.09643 |
getHeadingRadians() | 1.41372 | [1.41372 | skipped | 1.34390 |
delta dist | ... | 8.0 | should be skipped | 15.98 |
Sorry i just edited my former post .. to save space.
Yep onStatus(..) is always the first event and holds every state of your robot.