Bots and Simulations > Evolution and Internet Sharing Sims
Infinite Loops
PurpleYouko:
--- Quote ---Keeping it as an option would be good. Personally I don't see it as that much of a problem but other people seem to.
--- End quote ---
As an option, no problem but as a default it would mess up almost all of the complex functions that go into making a streamlined (low energy consumption) combat bot. (See the simplebot tutorial for an example)
Pretty much every one of my top bots in the league use a system where they store a value on the stack based on some conditions. The value isn't used until a later gene in the genome. Clearing the stack removes this behaviour option and hugely limits the potential complexities of robots and evolution.
How about an option that wipes the stack at the end of the cycle? (Did you already do this Num? I know early versions allowed carry over.) I haven't yet attempted to design a bot that carries values over to the next cycle so that is no big deal. Most often a carried over value just fills the stack up and screws up the robot.
Numsgil:
I believe I fixed the stack to not pass values into new cycles already, though in what version that was I have no idea. (Probably the new one).
The way PYs better bots work seems to be the way that evolved bots, well, evolve.
PurpleYouko:
--- Quote ---I believe I fixed the stack to not pass values into new cycles already
--- End quote ---
Thought you had.
--- Quote ---The way PYs better bots work seems to be the way that evolved bots, well, evolve.
--- End quote ---
Figures. A bot neither knows nor cares how a value gets onto the stack or even how long it has been there. He just uses it. That's the way evolution works.
Botsareus:
I think its good to keep that loop of the stack thingy. Keep stack erasure as an option but leave it with the stack cycle loop as defult. I think the stack cycle loop is more natural.
PurpleYouko:
We do have one difference from the old days.
At some time in the last few versions, Num changes the dynamic nature of the stack. I discovered this last week while working through a debugger for my "Snapshot" utility.
No longer do new values fall off the stack once it fills up, the way they used to.
Now they just push the whole stack down and displace the bottom value.
That was a bit sneaky Num. I kind of like it though. :P
Maybe it is listed in the readme file but I hadn't noticed it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version