Bots and Simulations > The Gene depository

Help with something else

<< < (2/3) > >>

Moonfisher:
If you want to avoid the issue of birth ties breaking before all data is transfered, you can just cram more information into each of the first 5 that are transfered immediatly.
Vars go up to 32000 as far as I know, leaving 15 bits of space. So if you have values that take up half that space you can pack the values into the same var using the | and & operators.
Ofcourse values up to 1000 will use op 10 bits I think, so you may have to break up data into smaller fragments to fit them... gets harder to keep track of.
But, looks like the "first" var (972) is never used... so...

Panda:
That is the one I moved it for but the bot still isnt working, I am away from my pc so when I get bac home I will show the code again just in case something isnt right for it, I will alos wexpain what each of the genes have to do

Moonfisher:
Well, the value from bot should get transfered to parentbot at age 31, so that may not be whats causing the problem.
Maybe if you explain what the overall problem is with the bots behavior...
One thing I noticed is that "type" is set to 6 at age 0, then to 5 at age 1... and never changed since...
So basicaly instead of checking the type you could just check robage. But I'm thinking maybe this wasn't how it was suposed to work...

Panda:
.type is passed down the generations, it is so the bot knows how much energy to share at, ect, ect...
I dont think that is a problem in the code. I have also just realised I can use "dec" instead of "*.type 1 sub .type store" The idea is that it gets decreased by 1 when the bot has just been born  . I find going throught he code with somebody helps me debug the code but I dont have anybody to do it with at the mo

Moonfisher:
Yeah, forgot you deleted the first gene, so type should work. And yes dec is another way of decrementing, and with F1 settings it costs the same as a condition rather than a store (So it's cheaper).
But the other line should work too... bot should get moved to parentbot as the line says. I can't see any reason why that line wouldn't work once you fixed the mem location...
What exactly is the problem with the behavior of the bot ?
You could try to cycle through it while observing memmory or using the console to check the values being handeled. It's hard to come up with any other advice without knowing what the issue is since the gene you're mentioning looks like it should work as intended.

Navigation

[0] Message Index

[#] Next page

[*] Previous page