Difference between revisions of "Wave Suffering"

From Robowiki
Jump to navigation Jump to search
m
Line 9: Line 9:
 
* Incorrect/inaccurate precise prediction. For this there are a number of [[Precise Prediction|open source precise predictors]].
 
* 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.
 
* 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.
+
* Bad set back as front or goto implementation.
 
* Problematic [[Wall Smoothing]] that either is too harsh or not harsh enough.
 
* Problematic [[Wall Smoothing]] that either is too harsh or not harsh enough.
 
* Poor distancing that either causes it to go too close or too far in some situations.
 
* Poor distancing that either causes it to go too close or too far in some situations.

Revision as of 15:46, 27 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 back as front or goto implementation.
  • Problematic Wall Smoothing that either is too harsh or not harsh enough.
  • Poor distancing that either causes it to go too close or too far in some situations.