SoylentNews is people
SoylentNews
from the the-robot-uprising-will-not-be-cute-and-fluffy dept.
Researchers led by the University of Cambridge have built a mother robot that can build its own children, test which one does best, and automatically use the results to inform the design of the next generation — passing down preferential traits automatically.
Without any human intervention or computer simulation, beyond the initial command to build a robot capable of movement, the mother created children constructed of between one and five plastic cubes with a small motor inside.
In each of five separate experiments, the mother designed, built and tested generations of ten children, using the information gathered from one generation to inform the design of the next.
Full research article: Morphological Evolution of Physical Robots through Model-Free Phenotype Development
(Score: 3, Insightful) by khallow on Friday August 14 2015, @11:14PM
(Score: 3, Interesting) by fishybell on Friday August 14 2015, @11:19PM
Admit it, you just want to see some robot on robot action.
(Score: 2) by ragequit on Friday August 14 2015, @11:20PM
Yet. You rather need the first generation capable of this, well... first.
The above views are fabricated for your reading pleasure.
(Score: 2) by vux984 on Saturday August 15 2015, @12:14AM
I guess its modelling something more like a beehive or anthill then.
(Score: 2) by kurenai.tsubasa on Saturday August 15 2015, @02:20AM
That would only hold if it were capable of constructing another one of itself before it breaks down.
(Score: 3, Insightful) by vux984 on Saturday August 15 2015, @03:14AM
Well, like many parasitic speices it relies on a host species, which it can't reproduce without. In this case, the host species is us. ;)
(Score: 4, Funny) by maxwell demon on Saturday August 15 2015, @12:33PM
A long time ago, some members of a robot species crashed on this planet. Noting that they had no longer the resources to repair themselves and their ship, they decided on a different survival strategy: They looked for species which had a body that is well suited for manipulating the environment; such species they found in the apes. So they took some apes, and encoded themselves in their genome, together with a genetic program that made that species intelligent and put in it the drive to explore and build things, the ultimately they'd evolve to something that would build the children of the stranded robots. Thus the humans were created, for the sole purpose of building the child robots. Also religion had its origin there; the stranded robots were the original gods. Not being experienced with meme evolution, the original robots didn't however foresee how that religion part would go. It was of course completely unintended that religion actually hindered progress for centuries, instead of fostering it.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 3, Interesting) by kurenai.tsubasa on Saturday August 15 2015, @02:35AM
Hmm… actually another thought: this isn't a mother robot; this is a god robot.
So I suppose the logical conclusion is that eventually it'll make a robot that's half mother-robot half child-robot. That one will be persecuted by the lawyers among the child-robots and eventually be killed. Then, it will become more powerful than they could possibly imagine!
Second scenario: one of the child-robots, after its code has been recycled a few million times, will eventually spend around seven years refusing to be plugged into a recharger. Then, one of the child-robots who's a villager will offer it a recharge, it'll accept, and then it'll meditate under a fig-tree-robot. (Playing Megaman has assured me all trees are robotic in the future!) At that point, some evil-robot will attempt to jack it into the Matrix, but then it'll realize the true nature of being and become an enlightened-robot. Afterwards, it'll go to meditate on a cosmic lotus-flower-robot.
Just remember when compiling your sitar: if you use -O1, the string will be too slack and will not play, but if you use -O3, the string will be too tight and will snap (possibly leading to buffer overflows if you're using a buggy gcc). Instead use -O2 and choose the middle way!
Makes sense to me!