Code center > Old Suggestions Awaiting Programming

Simulation Tools

(1/7) > >>

Numsgil:
What simulation tools would you like to see?

I'd love to get better graphs.  The current ones, well, suck.  Darwinpond (google it) has some pretty good graphs going on.  And a way to save graph data to an excel exportable file, like the snapshot function, would be pretty cool.

Also, user definable 'best bot' parameters would rock.

And a control that charts the flow of energy in the simulation would be pretty cool too.  It would show you how much energy flows into vegs, how much energy vegs use, how much energy flows into veg feeding bots or is lost to the simulation, how much energy bots use, how much energy is flowing into carnivores, etc.

shvarz:
DNA analysis tool: load the DNA in, then go command by command and see the stack and all the memory locations visually with newly-written values lighting up.  When bot checks for something like the presence of tie or the value of eye, it asks you for input.  At the end of the cycle the summary is given: "bot will shoot such and such particle, bot will move so much, its energy is going to be..." and so on.

Shen:
New graphs would be nice, there not much use atm other than monitoring your sim while the video output is disabled.

Id like to see an improved console as well. Its a valuble tool for debugging bots but very user unfriendly. Maybe adjustable size, combine it with the 'Gene Activation' tool so you can view more than one cycles worth at a time without scrolling in a tiny box. And auto refreshed eye values. Current stack contents. As much as you can cram in basically.

More stats for indiviual bots as well. Nrg consumed/used, average nrg used per cycle, kills.

A DNA parser/checker would be cool as well. Nothin like hunting for a typo in 30 genes of F1 bot, useful for newbies as well.

Also theres an update for DarwinPond, GenePool4. Havnt used it much though, I always get die offs.

PurpleYouko:

--- Quote ---DNA analysis tool: load the DNA in, then go command by command and see the stack and all the memory locations visually with newly-written values lighting up.  When bot checks for something like the presence of tie or the value of eye, it asks you for input.  At the end of the cycle the summary is given: "bot will shoot such and such particle, bot will move so much, its energy is going to be..." and so on.
--- End quote ---
That shouldn't be toooooo difficult to program.
Would you prefer the output to go to the console or into a text file?

PurpleYouko:
Nice ideas Shen


--- Quote ---A DNA parser/checker would be cool as well. Nothin like hunting for a typo in 30 genes of F1 bot, useful for newbies as well.
--- End quote ---
You do realize that the best way to do this now is to run the bot then look at its DNA in the info window. All typos come out as zeroes. It is pretty easy to see mistakes this way.

Navigation

[0] Message Index

[#] Next page

Go to full version