Darwinbots Forum
Bots and Simulations => Evolution and Internet Sharing Sims => Topic started by: Tilthanseco on July 06, 2012, 08:08:32 PM
-
This bot will stop moving when it wants to repro, this curiously leads to many big berthas in the sim who sit in front of veggies they were eating but can't reach now. (other bots keep pushing veggies in front of them)
The problem I have is that I don't know how the bot is stopping. It has a .up and .shoot command that are always active, but when it wants to .repro, the .up command gets canceled somehow?
Here is the Original:
cond
start
100 .up store
-1 .shoot store
stop
cond
*.nrg 20000 >
start
30 .repro store
15 .aimdx store
stop
end
Evolved: 535 Generations, 42 Mutations
' Gene: 1
cond
start
77 .up store
-1 .shoot dec
stop
' Gene: 2
start
*.nrg 19819 >
' Gene: 3
start
42 .repro store
store
5 15
' Gene: 4
cond
*498 overbool
Is this behavior attributed to storing 0 in -1? "... -1 .shoot dec ... 42 .repro store store"
-
Yes, I think store takes the absolute value of the store location. Possibly mods it by 1000 as well. So 0 -1 store is the same as 0 1 store.
-
Cool, Thanks
Now half the poor population mutated to not move at all. They're taking advantage of the stagnant veggies and being bumped by movers.
It does let them use half as much nrg/cycle, -3 instead of -6. The population has even doubled. (260 vs 140s)
"77 < store"
-
It'll be interesting to see how stable that sort of mutation is. It sort of relies on there being some movers somewhere
-
looks like a mutation that cannot go into fixation
-
Yep, that population slowly died out as the veggies were pushed away.
The stop when giving birth mutation is still going very strong; because of it, the population swings from 100 to 600. (average 200)
I just went on vacation and forgot to stop it, so we'll see if it survives and what happens in a week. (dynamic costs are off)