Difference between revisions of "Talk:Watermelon/Development"
J Litewski (talk | contribs) (→WaveSurfing adaptation: So it's not only me...) |
(→WaveSurfing adaptation: Clarifying miscommunication) |
||
| Line 6: | Line 6: | ||
When my wavesurfing was segmented only on velocity, it adapted almost immediately to velocity-based targeting, specifically linear targeting. It only had to get hit perhaps once for each velocity segment before it "got the picture". Now that I've added all these segments, it's adapting *much* more slowly (and getting hit a lot more in the process!). Any thoughts as to what could cause this sort of behavior? Are my segments too narrow? -- [[User:Synapse|<font style="font-size:0.8em;font-variant:small-caps;">Synapse</font>]] 00:54, 14 June 2009 (UTC) | When my wavesurfing was segmented only on velocity, it adapted almost immediately to velocity-based targeting, specifically linear targeting. It only had to get hit perhaps once for each velocity segment before it "got the picture". Now that I've added all these segments, it's adapting *much* more slowly (and getting hit a lot more in the process!). Any thoughts as to what could cause this sort of behavior? Are my segments too narrow? -- [[User:Synapse|<font style="font-size:0.8em;font-variant:small-caps;">Synapse</font>]] 00:54, 14 June 2009 (UTC) | ||
| + | |||
:I have kinda the same problem. [[GravityWave]] is segmented on distance currently, since adding even one more segment drops his score by 50%. I just thought it was because my computer is old and my code really basic. I know this didn't help you much, but still :P --[[User:J Litewski|Jacob Litewski]] 01:01, 14 June 2009 (UTC) | :I have kinda the same problem. [[GravityWave]] is segmented on distance currently, since adding even one more segment drops his score by 50%. I just thought it was because my computer is old and my code really basic. I know this didn't help you much, but still :P --[[User:J Litewski|Jacob Litewski]] 01:01, 14 June 2009 (UTC) | ||
| + | |||
| + | It's not just that I increased the segmentation - I have a mechanism for choosing the most useful segmentation based on how "spiky" it is that ensures that I never have to deal with an empty segment. My trouble is that it's not choosing the clearly best segmentation - velocity. It chooses things like ''time since last reversed'' or ''lateral walldistance'' even though the enemy bot isn't firing based on those variables. Even if I remove the other segmentations so we're down to just velocity and nothing, the velocity segmentation isn't as specific with this framework as it was without the automatic segmentation. -- [[User:Synapse|<font style="font-size:0.8em;font-variant:small-caps;">Synapse</font>]] 02:16, 14 June 2009 (UTC) | ||
Revision as of 03:16, 14 June 2009
Hooray!
Glad to see you consider your bot worthy of version tracking now! It's fun to watch people's progress. --Simonton 16:11, 25 September 2008 (UTC)
WaveSurfing adaptation
When my wavesurfing was segmented only on velocity, it adapted almost immediately to velocity-based targeting, specifically linear targeting. It only had to get hit perhaps once for each velocity segment before it "got the picture". Now that I've added all these segments, it's adapting *much* more slowly (and getting hit a lot more in the process!). Any thoughts as to what could cause this sort of behavior? Are my segments too narrow? -- Synapse 00:54, 14 June 2009 (UTC)
- I have kinda the same problem. GravityWave is segmented on distance currently, since adding even one more segment drops his score by 50%. I just thought it was because my computer is old and my code really basic. I know this didn't help you much, but still :P --Jacob Litewski 01:01, 14 June 2009 (UTC)
It's not just that I increased the segmentation - I have a mechanism for choosing the most useful segmentation based on how "spiky" it is that ensures that I never have to deal with an empty segment. My trouble is that it's not choosing the clearly best segmentation - velocity. It chooses things like time since last reversed or lateral walldistance even though the enemy bot isn't firing based on those variables. Even if I remove the other segmentations so we're down to just velocity and nothing, the velocity segmentation isn't as specific with this framework as it was without the automatic segmentation. -- Synapse 02:16, 14 June 2009 (UTC)
