How to Improve a Pattern Matcher

Jump to navigation Jump to search

How to Improve a Pattern Matcher

Hi, what are some easy ways to improve the standard nano-sized pattern matcher? I've tried everything (that I can think of!) but each change just seems to make the gun worse. Thanks!

Slugzilla (talk)17:25, 21 July 2019

Think this way: if there are easy ways to improve, it should be already within every nano-sized pattern matcher.

And, most changes are making things worse simply means you may be already at some local minimum, which is discovered by the predecessors. The "improvements" you easily think of may be already tried by predecessors as well, and the ones that work are already applied.

So, to push the bar further, just go the "hard" way. Record some data of every opponent you need to face, encode some behavior of your gun into genes, and use genetic algorithms to find a way out!

Xor (talk)02:29, 22 July 2019

Ah, I was hoping there were some simple ways that took a bit more codesize. Since the nano-sized pattern matcher I am using is not in a NanoBot, I can afford better performance for more code. I have quite a few bytes to spare in Basilite and I was hoping for changes that were easy to put in and gave small gains, like energy management for example.

Slugzilla (talk)03:35, 23 July 2019

Then don't look at pattern matchers in nanobots, look at those in microbots, minibots and even megabots. And energy management is mostly independent of gun type I think, as long as they are learning. So learn from gf targeting bots' energy management as well.

Xor (talk)18:05, 23 July 2019

OK. I'll check it out ;)

Slugzilla (talk)23:59, 23 July 2019

Multiple choice is the obvious improvement if you have more codesize. Otherwise adding distance buckets can also be helpful. Cotillion does both of these.

Skilgannon (talk)09:32, 24 July 2019

Awesome! I'll try one of those later =)

Slugzilla (talk)06:15, 25 July 2019