Bots and Simulations > Bot Tavern

Evo Anyone?

<< < (3/5) > >>

Endy:
Know what you mean. I had to replace my laptop after the screen broke. :sad2:

On the plus side the old computer has been dedicated to storing most of the robot files ever made. :D

Modified the code for the semi-fixer to allow normal bots to spread themselves out better. I think it's helping to reduce the conditions that lead to rampant cannibotism(groups of bots sitting idly by with a predator next to them). I'm likeing how natural the ecosystem is looking, all the bots moving around when crowded.

I'll post the bot's code up a bit later, I want to try and do some work on allowing them access to the taste senses.

Got the idea from an article about the Darpa race winner, telling about how they added more "senses" to give the jeep a better grasp of the situation. Pretty cool. B)

Endy:
What was this segementation fault about? I was noticing some bizare stuff in sexrepro myself.

The bots seem to be formng waves now, very weird. I think feeding is causing a local area growth and the "move when hit" dna is causing them to spread out, one bot hits another and the cycle keeps going.

In the latest run they've managed to learn to spin while as a group, more or less, traveling in one direction. :)

Numsgil:
Most impressive.  I love to hear when bots learn new emergent behavior (wether programmed or evoluted).  Especially group behavior, like my fish school bot.  I just think it's the coolest thing bots can do.

I've rewritten most of the core routines (including reproduction) to be less chaotic and more centralized.  As a result, they're a dream to maintain, and also incredibly buggy (any new length of programming always is).  There's a bug I'm trying to isolate now that is driving me absolutely crazy.  I can't seem to isolate it.  As I step through the program it all seems just fine.  If I let it go it screws up.  I just can't find exactly where it's screwing up.  Most infuriating.

On a plus side, when the program does something naughty, it won't just exit anymore.  Or save your sim or anything like that.  The engine will simply stop running, but the GUI will remain responsive, and you'd be able to (theoretically, I'm not this far yet) save the sim, attempt to restart, load another sim, etc.

A wonderous unforeseen consequence I am simply enthralled with.

Endy:
That'd be nice. It does get annoying having to restart it the hard way. Could it maybe auto-restart when a bug occurs? That'd be pretty cool, especially when running long evosims. I get annoyed when I have a decent sim going and the program stops on me without giving me any idea what's been going on.

Numsgil:
I should be able to add some pretty advanced error handling routines, I just don't really understand them yet.

Theoretically, It'll be able to tell you exactly where in the code the problem is, what caused the problem, send a report back to some error database (like what XP does), save your sim, and attempt to continue automatically.

Theoretically anyway.  Like I said, I don't really understand it all yet.

Navigation

[0] Message Index

[#] Next page

[*] Previous page