User talk:J Litewski - Revision history

RednaxelaBot: Using .

2010-07-01T08:42:16Z

Using <syntaxhighlight>.

J Litewski: /* 2D Segmentation Smoother */ Leveled 2D Segmented Array

2009-06-12T04:29:33Z

2D Segmentation Smoother: Leveled 2D Segmented Array

Rednaxela: Random thoughts

2009-06-12T04:13:59Z

Random thoughts

J Litewski: /* 2D Segmentation Smoother */ new section

2009-06-12T03:56:01Z

2D Segmentation Smoother: new section

Nat: /* Wiki issues */ be bold =)

2009-06-09T03:50:23Z

Wiki issues: be bold =)

J Litewski: /* Wiki issues */ I'll be good :)

2009-06-09T03:12:54Z

Wiki issues: I'll be good :)

Nat: /* Wiki issues */

2009-06-09T03:01:21Z

Wiki issues

Nat: /* Wiki issues*/

2009-06-09T03:00:39Z

Wiki issues

J Litewski: /* Talk about GravityWave */ Sucessful gunHeat class!! yay!

2009-06-06T00:54:41Z

Talk about GravityWave: Sucessful gunHeat class!! yay!

J Litewski: /* Talk about GravityWave */

2009-06-05T15:55:56Z

Talk about GravityWave

@@ Line 45: / Line 45: @@
 Gunheat code (rapid-cooked now, hasn't test yet)
-<pre>
+<syntaxhighlight>
 class GunheatTracker {
 	private double gunHeat;
@@ Line 70: / Line 70: @@
+	}
+}
-</pre>
+</syntaxhighlight>
 You must detect energy drop yourself. I will write more when I come home.   &raquo; <span style="font-size:0.9em;color:darkgreen;">[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]</span> &raquo; 09:37, 5 June 2009 (UTC)
@@ Line 119: / Line 119: @@
 </pre>
 Note that it will not be this dramatic of a spike. But if this works the way I think it will, it will be a 2D BIN Smoother, or 2D Segmentation Smoother as I call it, since it does smooth the BINS biased on where the hit took placed on the Segment. This should make it easier to go from one segment to the next without to much fuss (like I have been having) and optimize the danger checker. Here is the code:
-<pre>
+<syntaxhighlight>
 public void logHit(EnemyWave ew, Point2D.Double targetLocation, int segment) {
      int index = getFactorIndex(ew, targetLocation);
@@ Line 131: / Line 131: @@
+}
-</pre>
+</syntaxhighlight>
 Tell me what you think please :) --[[User:J Litewski|Jacob Litewski]] 03:56, 12 June 2009 (UTC)

← Older revision		Revision as of 04:29, 12 June 2009
Line 153:		Line 153:
	</pre>		</pre>
	Which is a technique that massively boosts score in [[Rednaxela/SaphireEdge]]... though... nobody other than me has implemented it to my knowledge... as it does get a little complicated when you get into a large number of segment dimensions... :) --[[User:Rednaxela\|Rednaxela]] 04:13, 12 June 2009 (UTC)		Which is a technique that massively boosts score in [[Rednaxela/SaphireEdge]]... though... nobody other than me has implemented it to my knowledge... as it does get a little complicated when you get into a large number of segment dimensions... :) --[[User:Rednaxela\|Rednaxela]] 04:13, 12 June 2009 (UTC)
		+
		+	I haven't even thought of shooting yet... heh
		+	Anyways, after testing it, I noticed my score drop massively. so I looked into the fight and saw my problem: I didn't have 'levels' of arrays for bullet power. So, I'm testing my new(er) Leveled 2D Segmentation Smoothing, Leveled with 4 levels biased off of bullet power and segmented with a 2D array biased off of distance and BINS respectively ( or [power][distance][BINS]). Hopefully this will work better and learn faster. --[[User:J Litewski\|Jacob Litewski]] 04:29, 12 June 2009 (UTC)

← Older revision		Revision as of 04:13, 12 June 2009
Line 133:		Line 133:
	</pre>		</pre>
	Tell me what you think please :) --[[User:J Litewski\|Jacob Litewski]] 03:56, 12 June 2009 (UTC)		Tell me what you think please :) --[[User:J Litewski\|Jacob Litewski]] 03:56, 12 June 2009 (UTC)
		+
		+	It's been done by a few people before and isn't a bad idea. However, the two things that should be kept in mind: '''1)''' You generally want less smoothing across segments than across bits but doesn't hurt to experiment, and '''2)''' This will get SLOW when/if you start having upwards of 5 different segmention axis like many/most high ranking bots have. Additionally, here's another thing you can try:
		+
		+	if you're writing and you're halfway between segments, write half in each like this:
		+	<pre>
		+	0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
		+	0.0 0.5 1.0 1.5 2.0 1.5 1.0 0.5 0.0
		+	0.0 0.5 1.0 1.5 2.0 1.5 1.0 0.5 0.0
		+	0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
		+	</pre>
		+	and if you're closer to one side than another, weight your insertion towards that side. Then when reading, you do a similar thing, like if you're halfway between segments looking like
		+	<pre>
		+	0.0 0.0 0.0 0.5 1.0 1.5 2.0 1.5 1.0
		+	1.0 1.5 2.0 1.5 1.0 0.5 0.0 0.5 0.0
		+	</pre>
		+	you will shoot by taking the highest point of
		+	<pre>
		+	1.0 1.5 2.0 2.0 2.0 2.0 2.0 1.5 1.0
		+	</pre>
		+	Which is a technique that massively boosts score in [[Rednaxela/SaphireEdge]]... though... nobody other than me has implemented it to my knowledge... as it does get a little complicated when you get into a large number of segment dimensions... :) --[[User:Rednaxela\|Rednaxela]] 04:13, 12 June 2009 (UTC)

← Older revision		Revision as of 03:56, 12 June 2009
Line 79:		Line 79:

	I built an Utilities class that uses a very simplistic method to track of stuff. Currently, with the help of some quick hacks, it helps weed out non-bullet waves. I'm running a 500 round test now to see if it improved anything. --[[User:J Litewski\|Jacob Litewski]] 00:54, 6 June 2009 (UTC)		I built an Utilities class that uses a very simplistic method to track of stuff. Currently, with the help of some quick hacks, it helps weed out non-bullet waves. I'm running a 500 round test now to see if it improved anything. --[[User:J Litewski\|Jacob Litewski]] 00:54, 6 June 2009 (UTC)
		+
		+	== 2D Segmentation Smoother ==
		+
		+	Ok, this woke me up out of the deepest sleep I had in years. I was trying to figure out the best way to log hits with [[GravityWave]]'s new segmented array. I thought the original logHit function was doing it's job. Well, it hit me, it saw storing the data like a 1D array, not like a 2D segmented array. For instance, data on <code>test[8][8]</code> (which is a 9x9 array) is laid out like this:
		+	<pre>
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	</pre>
		+	When it was storing the data, it would store it like this (if hit on the 2D GuessFactor of 0 (5x5)):
		+	<pre>
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 1 2 3 4 3 2 1 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	</pre>
		+	Instead, it should be storing it like this:
		+	<pre>
		+	0 0 0 0 0 0 0 0 0
		+	0 0 0 0 1 0 0 0 0
		+	0 0 0 1 2 1 0 0 0
		+	0 0 1 2 3 2 1 0 0
		+	0 1 2 3 4 3 2 1 0
		+	0 0 1 2 3 2 1 0 0
		+	0 0 0 1 2 1 0 0 0
		+	0 0 0 0 1 0 0 0 0
		+	0 0 0 0 0 0 0 0 0
		+	</pre>
		+	Note that it will not be this dramatic of a spike. But if this works the way I think it will, it will be a 2D BIN Smoother, or 2D Segmentation Smoother as I call it, since it does smooth the BINS biased on where the hit took placed on the Segment. This should make it easier to go from one segment to the next without to much fuss (like I have been having) and optimize the danger checker. Here is the code:
		+	<pre>
		+	public void logHit(EnemyWave ew, Point2D.Double targetLocation, int segment) {
		+	int index = getFactorIndex(ew, targetLocation);
		+
		+	//New 2D Segmentation smoother
		+	for (int x = 0; x < 13; x++) {
		+	for(int y = 0; y < BINS; y++) {
		+	_surfStats2[x][y] += (Math.pow(segment - x, 2) + 1) / (Math.pow(index - y, 2) + 1);
		+	}
		+	}
		+
		+	}
		+	</pre>
		+	Tell me what you think please :) --[[User:J Litewski\|Jacob Litewski]] 03:56, 12 June 2009 (UTC)

@@ Line 21: / Line 21: @@
 Hi! Please mark an edit as minor edit when you just correct grammar or adding links. And please write edit summary when edit, it help other robocoder to know what is changed briefly. Mroe information about this can be found on Wikipedia. Thanks! &raquo; <span style="font-size:0.9em;color:darkgreen;">[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]</span> &raquo; 06:35, 18 May 2009 (UTC)
-Hi Litewski. In your recent contributions to [[Bin Smoothing]] page and some other pagse, you use [[:Category:CamelCase redirect|CamelCase]] words in some links text, such as [[GuessFactorTargeting]], which is, by the standard of this new wiki, deprecated. The correct name with proper spaces is defined. The old CamelCase page still work as a redirect page, but it is better to link to the exact page instead of redirect page.
+Hi Litewski. In your recent contributions to [[Bin Smoothing]] page and some other pages, you use [[:Category:CamelCase redirect|CamelCase]] words in some links text, such as [[GuessFactorTargeting]], which is, by the standard of this new wiki, deprecated. The correct name with proper spaces is defined. The old CamelCase page still work as a redirect page, but it is better to link to the exact page instead of redirect page.
 Another issue: Standard heading level of the wiki is start at 2, threfore you should use level 2 heading <nowiki>(== Heading ==)</nowiki> instead of level 1 heading, which is use by page title itself. In some od your contributions to the page [[GITS]] and its subpages, you have the level 1 heading which have the same text as page title, which is not needed and make the table of content look funny. Thank you! &raquo; <span style="font-size:0.9em;color:darkgreen;">[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]</span> &raquo; 03:00, 9 June 2009 (UTC)
 :sorry for the problems, still kinda new to this. --[[User:J Litewski|Jacob Litewski]] 03:12, 9 June 2009 (UTC)
 == Handle ==

← Older revision		Revision as of 03:12, 9 June 2009
Line 24:		Line 24:

	Another issue: Standard heading level of the wiki is start at 2, threfore you should use level 2 heading <nowiki>(== Heading ==)</nowiki> instead of level 1 heading, which is use by page title itself. In some od your contributions to the page [[GITS]] and its subpages, you have the level 1 heading which have the same text as page title, which is not needed and make the table of content look funny. Thank you! » <span style="font-size:0.9em;color:darkgreen;">[[User:Nat\|Nat]] \| [[User_talk:Nat\|Talk]]</span> » 03:00, 9 June 2009 (UTC)		Another issue: Standard heading level of the wiki is start at 2, threfore you should use level 2 heading <nowiki>(== Heading ==)</nowiki> instead of level 1 heading, which is use by page title itself. In some od your contributions to the page [[GITS]] and its subpages, you have the level 1 heading which have the same text as page title, which is not needed and make the table of content look funny. Thank you! » <span style="font-size:0.9em;color:darkgreen;">[[User:Nat\|Nat]] \| [[User_talk:Nat\|Talk]]</span> » 03:00, 9 June 2009 (UTC)
		+	:sorry for the problems, still kinda new to this. --[[User:J Litewski\|Jacob Litewski]] 03:12, 9 June 2009 (UTC)

	== Handle ==		== Handle ==

@@ Line 17: / Line 17: @@
 Hi! Write more about yourself to your userpage, I'd be interested in it. And don't afraid of submitting your bots to RoboRumble. :) (it's very motivating and educational)--[[User:Robar|HUNRobar]] 18:02, 14 May 2009 (UTC)
-----
+== Wiki issues ==
 Hi! Please mark an edit as minor edit when you just correct grammar or adding links. And please write edit summary when edit, it help other robocoder to know what is changed briefly. Mroe information about this can be found on Wikipedia. Thanks! &raquo; <span style="font-size:0.9em;color:darkgreen;">[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]</span> &raquo; 06:35, 18 May 2009 (UTC)
 == Handle ==

@@ Line 32: / Line 32: @@
 * Segmentation (always a plus)
 * Better Algorithms
-* Enemy GunHeat Class (to weed out non-bullet waves)
+* Enemy GunHeat Class (to weed out non-bullet waves) (finished)
 * And more stuff I can't think of
 I did tweak the base a little bit (changed the radar, added in some more debug graphics, minor things), but other than that, nothing to drastic yet. So, go wild with your comments! --[[User:J Litewski|Jacob Litewski]] 03:05, 5 June 2009 (UTC)
@@ Line 69: / Line 69: @@
 Well, I just want a simplistic GunHeat class to weed out non-bullet waves that GravityWave seems to surf, mostly into bullets. It's more or less ''if enemy fired with x power, don't calculate waves for x ticks'' type thing. --[[User:J Litewski|Jacob Litewski]] 15:55, 5 June 2009 (UTC)

← Older revision		Revision as of 15:55, 5 June 2009
Line 67:		Line 67:

	OK, at home now. I don't think you need to detect enemy gunheat unless you are in melee (which need a lot of other components to make the class above work), or want the extra 2 ticks (as in [[DrussGT]] and [[RougeDC]]) to surf. Otherwise, it is much more easier to detect the thing by energy drop (you will need to do that if you want the class above work too) and adjusted the energy on the events (onHitRobot, onHitByBullet and onBulletHit). Anyway, this only work for one-on-one, in melee, you need to interpolate (a lot), do some statistical recording to predict the whole battle (two months work, don't seem to make much progress). » <span style="font-size:0.9em;color:darkgreen;">[[User:Nat\|Nat]] \| [[User_talk:Nat\|Talk]]</span> » 13:33, 5 June 2009 (UTC)		OK, at home now. I don't think you need to detect enemy gunheat unless you are in melee (which need a lot of other components to make the class above work), or want the extra 2 ticks (as in [[DrussGT]] and [[RougeDC]]) to surf. Otherwise, it is much more easier to detect the thing by energy drop (you will need to do that if you want the class above work too) and adjusted the energy on the events (onHitRobot, onHitByBullet and onBulletHit). Anyway, this only work for one-on-one, in melee, you need to interpolate (a lot), do some statistical recording to predict the whole battle (two months work, don't seem to make much progress). » <span style="font-size:0.9em;color:darkgreen;">[[User:Nat\|Nat]] \| [[User_talk:Nat\|Talk]]</span> » 13:33, 5 June 2009 (UTC)
		+
		+	Well, I just want a simplistic GunHeat class to weed out non-bullet waves that GravityWave seems to surf, mostly into bullets. It's more or less ''if enemy fired with x power, don't calculate waves for x ticks'' type thing. --[[User:J Litewski\|Jacob Litewski]] 15:55, 5 June 2009 (UTC)