a reply to:
FlySolo
The current IO model is insufficient for more advanced AIs. You end up with so much iterations that you run out of space very fast not speaking about
aviable computing power that you need for such calculations. Generating an integrated environmental response chain is one thing, dynamically float
it´s parameters and cross validate the outcome with multiple datasets and then embed new rule-sets in near realtime is like stepping on an molehill
compared to the mount everest.
You run into so much problems, space(ram&disk), flops, energy, autark data assesement (simply meaning you cannot trust one sensor, you have to compute
both datastreams individually and run the same simulations in parallel just to compare both outcomes in the end that are useless most of the time or
contradict themselfes or even lead to corrupted datafields (like learning wrong knowledge and base further decisions on that. You have te re-evaluate
every single rule-set agains any new. That´s the reason it´s said our brain still outsmarts io-chips. We do that 24/7 in idle mode not being aware
of it.
Quantum computing it is. Everything else is just ninjaing around the problem. I´ve been working on several projects (I mentioned some over time
here) and you end up restraining the software so much you could have worked out your own algorythms and functions way faster and with much more
reliability.
Object oriented programming isn´t going to do the trick with current aviable hardware designs. Forget 1/0 model it´s to slow, to much iterations, to
much short-memory-data to be used. We simply run into infinity(!!)
To give you a real world example, imagine you´d have to build a flying bird.
That learns to fly on it´s own and optimize flight patterns to save energy or time (while considering and presimulating environmental parameters). We
did it and you end up ordering unique controllers at semiconductor writing your own protocol bus and all that comes entailed with it. You end up
writing your own physics engine...
And one day you come back to work, someone is waiting for you at the entrance to give you new access codes and a new project. Your personal belonings
from that labor your left 8 hours before unknowingly nicely stacked in two boxes and not a screw left to be seen through the windows. They waited
until the last idiot left the building and seized everything overnight.
Last hint: go analog not digital.
edit on 29-3-2015 by verschickter because: (no reason given)
edit on 29-3-2015 by
verschickter because: (no reason given)
Really last hint: You basically simulate every thing and execute the hardware functions and keep track/record of sensor values and compare them to
your simulations. I remember every second in freeflight in windchannel needs around two to three minutes of afterprocessing in our cluster and if that
finished, another couple of hours re-evaluating every single damn ruleset. The you run simulations with float parameters that can take weeks if give
it too much room. A room full of humans will then resume code optimizations or leave it running until you get a half-way stable castrated AI that will
give reliable results over a long period of time. Not like flying 10 minutes like a charm only to have one sensor # up and decide do tilt the Z axis
and kiss the ground.
edit on 29-3-2015 by verschickter because: (no reason given)