Difference between revisions of "Wave Suffering"
Jump to navigation
Jump to search
(Created page with '{{stub}} In developing a wave surfing robot, many people go through that which is called Wave Suffering. This is usually caused by all the minuscule details that need to be gott…') |
(a few things I could think of, please add more) |
||
| Line 2: | Line 2: | ||
In developing a wave surfing robot, many people go through that which is called Wave Suffering. This is usually caused by all the minuscule details that need to be gotten right for it to score well. This term was coined by [[User:Axe|Axe]]. | In developing a wave surfing robot, many people go through that which is called Wave Suffering. This is usually caused by all the minuscule details that need to be gotten right for it to score well. This term was coined by [[User:Axe|Axe]]. | ||
| + | |||
| + | Common mistakes include: | ||
| + | * Incorrect wave information. | ||
| + | ** Waves should have the enemy position from last turn, and the fire time should be last turn. | ||
| + | ** Waves should use the absolute bearing and direction from 2 turns ago. That is the turn before last. | ||
| + | * Incorrect/inaccurate precise prediction. For this there are a number of [[Precise Prediction|open source precise predictors]]. | ||
| + | * Not including the distancer or other heading/velocity information in the precise prediction. That is to say the robot does things differently in actuality then what it does in the precise prediction. | ||
| + | * Bad set front as back or goto implementation. | ||
Revision as of 21:44, 26 July 2010
| This article is a stub. You can help RoboWiki by expanding it. |
In developing a wave surfing robot, many people go through that which is called Wave Suffering. This is usually caused by all the minuscule details that need to be gotten right for it to score well. This term was coined by Axe.
Common mistakes include:
- Incorrect wave information.
- Waves should have the enemy position from last turn, and the fire time should be last turn.
- Waves should use the absolute bearing and direction from 2 turns ago. That is the turn before last.
- Incorrect/inaccurate precise prediction. For this there are a number of open source precise predictors.
- Not including the distancer or other heading/velocity information in the precise prediction. That is to say the robot does things differently in actuality then what it does in the precise prediction.
- Bad set front as back or goto implementation.
