Wave Suffering - Revision history

MultiplyByZer0: Small fixes

2017-08-09T19:59:01Z

Small fixes

Sheldor: Minor edit.

2012-12-06T22:02:27Z

Minor edit.

Sheldor: Minor edit.

2012-12-06T22:01:14Z

Minor edit.

Chase-san: Trying to flesh this out as I tackle it myself (add code examples when possible, try and make them general)

2011-07-20T00:40:17Z

Trying to flesh this out as I tackle it myself (add code examples when possible, try and make them general)

Nat at 14:46, 27 July 2010

2010-07-27T14:46:18Z

Rednaxela at 04:47, 27 July 2010

2010-07-27T04:47:37Z

Chase-san: a few things I could think of, please add more

2010-07-26T20:44:59Z

a few things I could think of, please add more

Chase-san: 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…'

2010-07-26T11:21:41Z

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…'

New page

{{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 gotten right for it to score well. This term was coined by [[User:Axe|Axe]].

@@ Line 1: / Line 1: @@
 {{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 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 Pitfalls==
-=== [[Energy Drop]] ===
+=== [[Energy Drop]] Detection ===
-'''Wrong'''
+'''Wrong:'''
-<blockquote><syntaxhighlight>
+<syntaxhighlight>
 public void onBulletHit(BulletHitEvent e) {
-	lastEnemyEnergy = e.getEnergy();
+    lastEnemyEnergy = e.getEnergy();
+}
-</syntaxhighlight></blockquote>
+</syntaxhighlight>
-:*Caveat of this is if they fired a bullet at the same time ours hit them, it may not be detected, so even though it returns the energy after our bullet hits them, we should do the math.
-'''Correct'''
+The caveat of this is: if they fired a bullet at the same time ours hit them, it may not be detected. We should do the math.
-<blockquote><syntaxhighlight>
-//When our bullet hits them, they lose energy
+'''Correct:'''
 public void onBulletHit(BulletHitEvent e) {
-	double bulletPower = e.getBullet().getPower();
+    lastEnemyEnergy -= Rules.getBulletDamage(e.getBullet().getPower());
+}
 //When we get hit by the enemies bullet, they gain energy
 public void onHitByBullet(HitByBulletEvent e) {
-	lastEnemyEnergy += Rules.getBulletHitBonus(e.getPower());
+    lastEnemyEnergy += Rules.getBulletHitBonus(e.getPower());
+}
-</syntaxhighlight></blockquote>
+</syntaxhighlight>
 === [[Wave]] Creation ===

@@ Line 6: / Line 6: @@
 === [[Energy Drop]] ===
-[[Energy]] Adjustment due to robot hit and hit by robot
+Energy Adjustment due to robot hit and hit by robot
 '''Wrong'''

@@ Line 5: / Line 5: @@
 ==Common Pitfalls==
-=== Energy Drop ===
+=== [[Energy Drop]] ===
-Energy Adjustment due to robot hit and hit by robot
+[[Energy]] Adjustment due to robot hit and hit by robot
 '''Wrong'''
@@ Line 28: / Line 28: @@
 </syntaxhighlight></blockquote>
-=== Wave Creation ===
+=== [[Wave]] Creation ===
-* Waves should have the enemy position from last turn, and the fire time should be last turn.
+* [[Wave|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.

@@ Line 3: / Line 3: @@
 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:
+==Common Pitfalls==
-* Incorrect wave information.
-** Waves should have the enemy position from last turn, and the fire time should be last turn.
+=== Energy Drop ===
-** Waves should use the absolute bearing and direction from 2 turns ago. That is the turn before last.
+Energy Adjustment due to robot hit and hit by robot
 * 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 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.

@@ Line 9: / Line 9: @@
 * 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.
+* 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.

← Older revision		Revision as of 04:47, 27 July 2010
Line 10:		Line 10:
	* 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 front as back 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.

← Older revision		Revision as of 20:44, 26 July 2010
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.