Code center > Old Suggestions Awaiting Programming

Looking into memory snapshots

<< < (2/3) > >>

PurpleYouko:
Maybe so but it would still take you a couple of years or so to make any sense out of the save file

Greven:
No it would not! If the saved file has proper formatting, a program could make some beautifull statictics! But then again this could be done directly from DB...

PurpleYouko:
I guess graphing it would be pretty easy but I'm not sure what that would really acheive.

The point of saving memory locations and/or stacks is that you can follow a specific organism through the cycles of its life and see exactly what external stimuli effect it and in what way.
Critically examining all the inputs and outputs for one robot over 1000 cycles is still a pretty tall order. I have spent hours just looking at a single robot in a given situation while attempting to analyze exactly what, where, when, why everything is happening.
A bunch of pretty graphs wouldn't tell me diddly squat about what I really want to know. Stuff like exactly how much is stored into .aimsx when I have a variety of different eye inputs.
Try running HDV4 for a few cycles to see what I mean.
He doesn't use simple turning with stuff like "If eye3 > eye5 then store 23 in aimsx"
He uses a complex and infinitely variable formula based on several eye inputs.

1000 cycles of memory information from a single HDV4 would take me a couple of days to really sort out.

Numsgil:
The problem is just figuring out what it is you want to record in the bots memory.  Probably, the only useful things to record are memory locations that are set more or less at birth, or locations that directly relate to a bots success, like *.kills or *.body.

So you don't need to record 1000 memory locations.  You're probably only really interested in maybe 10.  Let the user create a small list of memory locations he wants to record.  Then record only when those memory locations change, and list how they changed.

Something like this:

robot 6985
born on 102540
died on 107654
*50
cycle# | value | changed by
102541 | 214 | self
103251 | 52 | positive shot
105315 | 314 | positive shot
107600 | 322 | self

In the end you really just want one snapshot tool.  Have it be able to record DNA, specified memory locations, and/or anything else you can come up with.

PurpleYouko:
Agreed Num.
You certainly need a lot more than 10 memlocs saved though.
Maybe 10 user definable memlocs in addition to most of the senses.
We certainly need all the eyes, the refvars, the myrefvars (in case you want to see anyone messing with them) and a few others recorded all the time.
Possibly about 100 memlocs per cycle. That wouldn't bee too bad for a single robot but it would make a pretty big snapshot file.

Navigation

[0] Message Index

[#] Next page

[*] Previous page