Bots and Simulations > Bot Tavern
Advanced Multibot Project
ashton15:
--- Quote from: Tj3 ---Let's come up with cell types we know we'll need, so we know what to work on.
I think some important ones are
Body cells: Store nrg, transfer information
Brain cells: Process information, send instructions
Eye cells: "See." Send brain information on what's happening
Tentacle cells: Branches out. Kill enemies, tie to veggies.
Movement cells: Move the robot, by either swimming or just moving.(We could use tentacle cells for this too.)
If we need more, we can add them, but we should work on these main ones to start.
--- End quote ---
Sorry... I made some concept art to try and understand this better and it took a bit longer than it anticipated as you appear to have started coding but I've attached the art I made, my idea of the bot is, the central grey blob is a brain, surrounded by blue protectors which also are for storage, then a certain ammount of tentacles stretch out to get away from the body, the green blobs you see clinging to the tentacle base are plants (don't ask how they got there) anyways at the end of the base are a few yellow movement cells which can work dependently to move the entire organism or independently too mauneveur tentacles so the face an anemy. Then finally on the end there is a mish-mash of branching tentacles which can pick up veggies, shoot, send signals to other bots and see plus anything else they need to.
To reproduce (this wouldn't seem true looking at the picture but oh well, can't be perfect) a tentacle breaks of at the base near the brain, the end of the tentacle where the movment cells are attached becomes the brain and the movement cells multiply to make a body. Then somehow the tentacles order themselves so that they are like the parents.
By the way the art is kind of what I hope darwinbots 3 will look like (hope your listening Nums) .
--- Quote from: Tj3 ---And the gene for processing it when it gets to its destination might look something like this.
[div class=\'codetop\']CODE[div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']cond
*.multi 0 =
*.tin 0 !=
*.tin1 *.botid =
*.type [bottype] =
start
'action
stop
--- End quote ---
Also for this I belive doing something like this would be better:
[div class=\'codetop\']CODE[div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']cond
start
*.multi 0 =
*.tin 0 !=
*.tin1 *.botid =
*.type [bottype] = and
'action
not
'send code to next bot
stop
I think you might need that to get signals past the first tentacle node...
Houshalter:
Awesome, we already have concept art. This brings up a whole new question: What will the bots structure be?
ashton15:
--- Quote from: Houshalter ---Awesome, we already have concept art. This brings up a whole new question: What will the bots structure be?
--- End quote ---
That's partially why I made it... I'm very confudled about what it is supposed to look like, do you like my design though? I think it might possibly be practical but probably needs many changes and I have the feeling other people have diffrent ideas...
Houshalter:
--- Quote ---That's partially why I made it... I'm very confudled about what it is supposed to look like, do you like my design though? I think it might possibly be practical but probably needs many changes and I have the feeling other people have diffrent ideas...
--- End quote ---
No one knows what "its supposed to look like" because theres no real goal except to make a kick ass multibot. Your idea is good though.
bacillus:
Looks like Hydra
I think tie IDs should be calculated on-site. What I did for the spine is alternate between 1 and 2 so bots only have to remember which one's in front or behind (this should be the first tie formed anyway), then 3 and 4 for tentacles, depending on if they were formed to the left or right of the spine. In this way, you can describe every cell, its function and its position in relation to the spine it's attached to. Tentacle bases would have an extra variable, or a different tie ID, that would signal new cells to act as tentacles rather than spines. I know this sounds a bit overwhelming, but the bottom line is that we need a non-static tie ID at some point, else something like 102 .readtie will become ambiguous and erratic at some point.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version