Darwinbots Forum
Bots and Simulations => DNA - General => Topic started by: Endy on November 04, 2005, 09:19:37 PM
-
Alright, I'll admit it, I don't have a clue what this does. :D
You wrote in Humilis that it will help it out, just not how exactly.
-
Older bots were limping along in because they were just blithely firing along at some number .up store.
Nowadays, that force is divided by mass to get actual acceleration.
To help older bots make the transition, all .up/.dn etc. are multiplied automatically by mass of the bot.
But I think this is somewhat cheating. So newer bots are encouraged to use:
use NewMove
to tell DB that it doesn't want it's .up's and .dn's multiplied by mass automatically.
Did that make any sense?
-
Yep, thanks :)
-
bots without use NewMove will operate (or should operate) the same as they did in older versions.
Humilis is correctly using the use NewMove command. View it as a template for how it's supposed to work.
I thought my first response post answered alot of your questions, so maybe you can point out what specifically doesn't make sense in that post so I won't be repeating myself in a way that was ineffective the first time?
-
you should do like im gonna do nums, it gives a specefic trust and then do all that newton stuff.
F=MA
-
you should do like im gonna do nums, it gives a specefic trust and then do all that newton stuff.
F=MA
That's exactly what's going on in 2.4. That's the physics stuff I fixed.
Griz, I was referring to my first post in this thread, not on the wiki...
syntax:
use works exactly like def. They both go at the start of the code before the first cond statement. They may even work anywhere in the code, I'm not sure. Traditionally they go at the start.
If you don't understand def, then you have an issue with knowing how the DNA works in general and that's really a seperate issue.
As to what use NewMove is actually doing:
upon encountering use NewMove, the robot's NewMove register (may be named something else, I forget) is set to true.
When the program enters the part that applies thrust to a bot, it will take what's in the .up/.dx, etc. registers and multiply them by current mass unless the NewMove flag is set to true.
-
Then you figured it out...?