16
Darwinbots3 / Make v3 support decimals
« on: May 15, 2008, 08:52:44 PM »
Ooo, nice. (I looked at http://www.mathpath.org/Algor/cuberoot/algor.cube.root.htm earlier, which has a different method, but I didn't attempt to implement it)
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Doesn't *.tiepres .readtie store do that?
I've been thinking about that too. The upside is that it would allow things like sqr to return more interesting results. But in the end it isn't much different from the integer stack. So I think it's probably the most realistic option. I could be persuaded, I think.
It takes the timer (an infitely expanding number and wraps it around the number of ties a bot has), that means every cycle a new tie is read.
I've long made the argument that there should be some penality for being a veggie and getting all that free nrg from heaven such as no movement or vision or similar but have constantly been overruled by the evo veggie crowd. There are several topics on this in the suggestiosn forum where I make detailed suggestiosn as to what to do. Again, I have been consistantly overruled... This is one reason both my IM sims have the sun turned off...
does sqrt only work if you use 10+? sqrt of 1 is a floating decimal.
Its actually a translation of a 4-d sphere (which 4d is always time, its a constant, just as two always are x,y or horizontal vertical) onto 2d space; the simulation also uses depth and bouyancy in pond mode, so a third axis sort of exsists as a number anyways. But reardless of what plain of exsistance you are in, the 4th dimension will always be time, and its important that this remain true if you look at the example on wiki:
printmem .setboy
314-> 2000
printmem .rdboy
315-> 0
robot genes execution: - =not executed
1 executed
2 -
3 -
4 -
5 -
printmem .rdboy
315-> 0
Its becuase the dist results and angles are scaled around a mod of a default of some sort I assume. Very odd that you should have any errors beyond environmental interference, producing these results; it could be that your bots arent focused on the same bot allt eh way through, or your bot cant see the bot froom 400 units away due to eye restriction.