Talk:WaveSim - Revision history

Voidious: moved User talk:Voidious/WaveSim to Talk:WaveSim: I guess this deserves to be in the main namespace

2011-09-08T18:25:12Z

moved User talk:Voidious/WaveSim to Talk:WaveSim: I guess this deserves to be in the main namespace

Voidious: /* General */ PM support basically ready

2011-04-17T03:32:26Z

General: PM support basically ready

Voidious: comment

2011-04-17T00:34:14Z

comment

Miked0801 at 13:58, 16 April 2011

2011-04-16T13:58:46Z

Rednaxela: /* Play-It-Forward */ oops

2011-01-28T00:25:48Z

Play-It-Forward: oops

Voidious: /* Play-It-Forward */ it's not like that

2011-01-27T14:28:06Z

Play-It-Forward: it's not like that

Rednaxela: /* Play-It-Forward */ feeding of unfinished waves

2011-01-27T14:21:19Z

Play-It-Forward: feeding of unfinished waves

Voidious: /* Play-It-Forward */ sounds neat

2011-01-27T13:24:46Z

Play-It-Forward: sounds neat

Rednaxela: /* Play-It-Forward */ new section

2011-01-27T04:48:57Z

Play-It-Forward: new section

Voidious: /* Compression? */ off-topic: stop RoboResearch stealing focus on Mac

2011-01-26T18:11:49Z

Compression?: off-topic: stop RoboResearch stealing focus on Mac

← Older revision		Revision as of 03:32, 17 April 2011
Line 16:		Line 16:

	: Cool - would of course welcome any feedback you have on usability. Btw it would require some updates to support PM "correctly". Right now, data is only fed to classifiers when a wave is collected. For PM you'd probably just want each TickRecord fed to the classifier as soon as it happens, and the wave collection could be ignored altogether. And you'd want abs heading instead of relative heading, but that could be deduced from relative heading + orbit direction + sign(velocity). Those would all be pretty simple changes so maybe I'll hack that together shortly for 2.0.1. --[[User:Voidious\|Voidious]] 00:34, 17 April 2011 (UTC)		: Cool - would of course welcome any feedback you have on usability. Btw it would require some updates to support PM "correctly". Right now, data is only fed to classifiers when a wave is collected. For PM you'd probably just want each TickRecord fed to the classifier as soon as it happens, and the wave collection could be ignored altogether. And you'd want abs heading instead of relative heading, but that could be deduced from relative heading + orbit direction + sign(velocity). Those would all be pretty simple changes so maybe I'll hack that together shortly for 2.0.1. --[[User:Voidious\|Voidious]] 00:34, 17 April 2011 (UTC)
		+
		+	: I've added the TickClassifier and also the raw heading to the file format. Probably won't rush it out yet so I can gather a new batch of sample data and write an example PM using TickClassifier, but if you want the dev version (you'd need to collect some data yourself), let me know and I'll gladly post it before the official release. --[[User:Voidious\|Voidious]] 03:32, 17 April 2011 (UTC)

	== Compression? ==		== Compression? ==

@@ Line 1: / Line 1: @@
 Still ironing out some issues here and there, but damn this is cool. =) Time to run normal battles, 20 seasons x 48 bots: 4.75 hours (on 2 threads). Time to run the same gun against the raw data: ~10 minutes. :-D Plus you don't have to hope randomness averages out over the battles - it's the same data every time. --[[User:Voidious|Voidious]] 23:37, 13 March 2010 (UTC)
@@ Line 12: / Line 14: @@
 Interesting idea here.  Might convince me to dust off my bots and give things another go.  --[[User:Miked0801|Miked0801]] 13:58, 16 April 2011 (UTC)
 == Compression? ==

← Older revision		Revision as of 13:58, 16 April 2011
Line 10:		Line 10:

	My recent gun tests have been against a field of 47 mid-range bots I had in an old [[RoboResearch]] test bed. Last night before bed, I took 5 minutes and used [[User:Voidious/BedMaker\|BedMaker]] to create a test bed of 250 bots that [[Diamond]] scores between 70% and 90% against, then started collecting 6 seasons of gun data (1500 battles) against them with [[User:Voidious/WaveSim#TripHammer_RES\|TripHammer RES]]. I felt so cool! =) --[[User:Voidious\|Voidious]] 16:15, 25 January 2011 (UTC)		My recent gun tests have been against a field of 47 mid-range bots I had in an old [[RoboResearch]] test bed. Last night before bed, I took 5 minutes and used [[User:Voidious/BedMaker\|BedMaker]] to create a test bed of 250 bots that [[Diamond]] scores between 70% and 90% against, then started collecting 6 seasons of gun data (1500 battles) against them with [[User:Voidious/WaveSim#TripHammer_RES\|TripHammer RES]]. I felt so cool! =) --[[User:Voidious\|Voidious]] 16:15, 25 January 2011 (UTC)
		+
		+	Interesting idea here. Might convince me to dust off my bots and give things another go. --[[User:Miked0801\|Miked0801]] 13:58, 16 April 2011 (UTC)

	== Compression? ==		== Compression? ==

← Older revision		Revision as of 00:25, 28 January 2011
Line 42:		Line 42:

	Hmm? It's not like that. Each wave also includes the ID of the last wave collected before it was aimed. So it only feeds the classifier the waves it had seen before trying to classify that wave. WaveReader stores two positions - the firing wave position and the reading/feeding position. --[[User:Voidious\|Voidious]] 14:28, 27 January 2011 (UTC)		Hmm? It's not like that. Each wave also includes the ID of the last wave collected before it was aimed. So it only feeds the classifier the waves it had seen before trying to classify that wave. WaveReader stores two positions - the firing wave position and the reading/feeding position. --[[User:Voidious\|Voidious]] 14:28, 27 January 2011 (UTC)
		+
		+	Oh, well... that's what I get for skimming over the code in the early morning I suppose. Let's see how this goes... --[[User:Rednaxela\|Rednaxela]] 00:25, 28 January 2011 (UTC)

← Older revision		Revision as of 14:28, 27 January 2011
Line 40:		Line 40:

	It strikes me that _classifier.feed(wave); and _classifier.classify(wave); currently aren't set up an accurate way. It looks to me like the classifier is being fed every wave before the one it's classifying, but I'd say this is notably inaccurate, because not all of those waves have finished yet. This could affect the results noticeably I think. It'll take a little more refactoring than I expected to correct for factors like this. --[[User:Rednaxela\|Rednaxela]] 14:21, 27 January 2011 (UTC)		It strikes me that _classifier.feed(wave); and _classifier.classify(wave); currently aren't set up an accurate way. It looks to me like the classifier is being fed every wave before the one it's classifying, but I'd say this is notably inaccurate, because not all of those waves have finished yet. This could affect the results noticeably I think. It'll take a little more refactoring than I expected to correct for factors like this. --[[User:Rednaxela\|Rednaxela]] 14:21, 27 January 2011 (UTC)
		+
		+	Hmm? It's not like that. Each wave also includes the ID of the last wave collected before it was aimed. So it only feeds the classifier the waves it had seen before trying to classify that wave. WaveReader stores two positions - the firing wave position and the reading/feeding position. --[[User:Voidious\|Voidious]] 14:28, 27 January 2011 (UTC)

← Older revision	Revision as of 18:25, 8 September 2011
(No difference)

← Older revision		Revision as of 14:21, 27 January 2011
Line 38:		Line 38:

	Sure! I might even try it out myself if you do. =) --[[User:Voidious\|Voidious]] 13:24, 27 January 2011 (UTC)		Sure! I might even try it out myself if you do. =) --[[User:Voidious\|Voidious]] 13:24, 27 January 2011 (UTC)
		+
		+	It strikes me that _classifier.feed(wave); and _classifier.classify(wave); currently aren't set up an accurate way. It looks to me like the classifier is being fed every wave before the one it's classifying, but I'd say this is notably inaccurate, because not all of those waves have finished yet. This could affect the results noticeably I think. It'll take a little more refactoring than I expected to correct for factors like this. --[[User:Rednaxela\|Rednaxela]] 14:21, 27 January 2011 (UTC)

← Older revision		Revision as of 13:24, 27 January 2011
Line 36:		Line 36:

	Hmm... I think I might just want to use this framework to test some new targeting ideas... Though I will need to update it to support PIF also. Perhaps the best way to do it would be a single row at the top of the CSV file, listing self/enemy positions/velocities. When I modify it do support this, want me to send the code? :) --[[User:Rednaxela\|Rednaxela]] 04:48, 27 January 2011 (UTC)		Hmm... I think I might just want to use this framework to test some new targeting ideas... Though I will need to update it to support PIF also. Perhaps the best way to do it would be a single row at the top of the CSV file, listing self/enemy positions/velocities. When I modify it do support this, want me to send the code? :) --[[User:Rednaxela\|Rednaxela]] 04:48, 27 January 2011 (UTC)
		+
		+	Sure! I might even try it out myself if you do. =) --[[User:Voidious\|Voidious]] 13:24, 27 January 2011 (UTC)

← Older revision		Revision as of 04:48, 27 January 2011
Line 32:		Line 32:

	: Figured if out, if anyone cares: add "-Dapple.awt.UIElement=true" argument in BattleRunner.java. --[[User:Voidious\|Voidious]] 18:11, 26 January 2011 (UTC)		: Figured if out, if anyone cares: add "-Dapple.awt.UIElement=true" argument in BattleRunner.java. --[[User:Voidious\|Voidious]] 18:11, 26 January 2011 (UTC)
		+
		+	== Play-It-Forward ==
		+
		+	Hmm... I think I might just want to use this framework to test some new targeting ideas... Though I will need to update it to support PIF also. Perhaps the best way to do it would be a single row at the top of the CSV file, listing self/enemy positions/velocities. When I modify it do support this, want me to send the code? :) --[[User:Rednaxela\|Rednaxela]] 04:48, 27 January 2011 (UTC)

← Older revision		Revision as of 18:11, 26 January 2011
Line 30:		Line 30:

	Figured it out - my little "go back to Apple JVM" stuff in my RoboResearch shell script wasn't really working, since RoboResearch doesn't use the Robocode control API, it actually launches Java itself. And now I remember why I hate the Apple JVM for RoboResearch - it launches a new "Java app" thing in the dock every battle and steals the focus from your current app. Time to figure out how to tweak that... I hope... Good news is I think this is almost good to go. =) --[[User:Voidious\|Voidious]] 16:49, 26 January 2011 (UTC)		Figured it out - my little "go back to Apple JVM" stuff in my RoboResearch shell script wasn't really working, since RoboResearch doesn't use the Robocode control API, it actually launches Java itself. And now I remember why I hate the Apple JVM for RoboResearch - it launches a new "Java app" thing in the dock every battle and steals the focus from your current app. Time to figure out how to tweak that... I hope... Good news is I think this is almost good to go. =) --[[User:Voidious\|Voidious]] 16:49, 26 January 2011 (UTC)
		+
		+	: Figured if out, if anyone cares: add "-Dapple.awt.UIElement=true" argument in BattleRunner.java. --[[User:Voidious\|Voidious]] 18:11, 26 January 2011 (UTC)