Bots and Simulations > Bot Tavern

Ambitious MB project

<< < (11/11)

Ta-183:
True. The format still needs to be ironed out, with species entries possibly using only two or three memory locations, with the ID in plain ASCII numerals and data stored as binary, each bit corresponding to a capability, but there would still need to be even more memlocs used to account for saving the values for things like the average energy and body levels. And the purpose of a memory bus would be to, for the most part, take a huge load off of the central brain cells for memory related tasks, such as finding and storing memory entries. Locating a single data entry in a large memory bank if it was all attached at a single point would take hundreds of cycles. And since there are no loops in DB-DNA, it would require the use of sim cycles as the loop used for searching memory and building/searching through lists. In addition, searching through memory requires building lists and arrays to iterate through, and this requires scratchpad memory to be allocated to bus operations, further reducing storage, meaning even more cells must be used. And yeah, it will need TONS of memory space. Once you start adding up all the entries that it will possibly be entering, it starts to get HUGE.

Once you really begin to think about what it will take to get this kind of thing working, it becomes clear that this thing would in no way be a viable evosim or combat organism. Evosim, maybe. But if you include commands and opcodes to be interpreted and executed, mutation goes out the window. But it would be SO freaking worth it. I wouldn't be able to do ANY of the coding required in such a bot, but I can help figure out how to make the thing go. I have a lot of free time to ponder things. This concept has taken up a lot of my thinking time recently.

Houshalter:
I want to see it work to. The dna would be huge, yes, but it would be mostly repetitive and structured, so once you figure out how it works you can piece together how it will work. I don't think the memory is the big issue here, its how it needs to use the memory. I think every cell should have an event it stores every cycle. This will include everything of importance that happened that cycle. It will keep several of these past cycles stored up. Every cycle it will make another one and, if theres no more room, probably delete one to. Every cycle it will look for important information thats being broadcasted and broadcast as much important things it knows as it can. This will require some kind of system for coordinating this mess. First you'll need a system for just making sure the bots are as aware of the other bots as possible and know whos reading from their touts and try to predict which bots touts it should be reading from. It can use the tloc/tval (im not sure thats the right sysvar but you get my point) to send a single piece of data to one other bot to, probably one that isn't actively reading from it. This will mostly be used to inform other cells that it has important information it needs to spread and they should read from them on the next cycle. Next you need a system of deciding whats important information and whats not. If a bot encouters a rare event, how important is the info it collected on the cycle before? How important is info collected from other bots on that cycle or previous cycles? This might have some flexibility in that over time bots can learn whats important and whats not, but in they still need some grand system for determining it. You can store the memory in the same manner. You'll need a system for creating "directories" which could be one way of organizing it. Bots would combine similiar pieces of information into a single more broader peice. They might be wrong alot but it would still be cool.  Heres how you can compress a single value to store 5. Just take each value you want, divide them by 5, and put them in binary into a single memory location. Sure, it will be off by 5 because of the stupid rounding, but most important values can be off by much more than 5 before they become usless.

bacillus:
Sounds like a really good idea. If it helps, there's no tie limit...

Sorry I've been out so long. My old computer totally stopped working, and I've got a new mac to replace it. Sadly, I haven't gotten round to figuring out how to run DB yet, and my time will be limited this year anyways - I'm doing a full high school course, as well as several uni papers, and five scholarships (harder than both) on top, so it's pretty much non-stop for me. In addition, I'm trying to make a national sports team, which eats up the rest of my time. Bottom line, I'll check in every now and then, but don't expect many contributions.
 

Navigation

[0] Message Index

[*] Previous page