Skip to main content

AI, robots, Action sensation....all in the same solution stew.

The image above, a plastinated human brain and central nervous system along with distributed nerves. It fascinates me that so many researcher or thinkers in the areas of machine learning and artificial intelligence are factoring out the importance of this distributed sensation and memory network in attempting to create highly agile and responsive intelligence's.

We can see in fact hints at the need for externalized sensory capability in an intelligence when we look at the cutting edge techniques in robotics. In robotics the problem was approached for nearly 40 years with the idea that you can computationally determine all the necessary motions of external limbs in order to dynamically balance and ambulate walking robots...but it turned out that doing that top down approach was not only extremely difficult, requiring massive amounts of computational power...but it was also doomed to always be less efficient from a power utilization stand point as well as simply not nearly as dexterous for free flowing motions (once where a precise path of motion is not followed).

The pieces started coming together in the mid 80's and came out of the work of people at MIT who started thinking seriously about asking how nature does these things. The Leg lab was famous for producing attempts at ambulation that mimicked animals and insects in various ways to reduce the necessary degrees of freedom and thus enable reduced  computation for ambulation with steady balance but these were still not getting it right.

The key insight came from Marc Raibert then at the Leg Lab, he reasoned quite obviously that if it  is true that ants and roaches can ambulate their limbs at astonishing speed while having barely a few thousand neurons for brains, there must be something else to how they do it.

He went to work building distributed sensation into his robots, allowing the limbs to meter the degrees of freedom and thus reduce the complexity of the ambulation calculations....however the real innovation came when the application of statistical learning algorithms combined with these distributed sensors on limbs made it's debut.

These methods allow for a massive collapse in computational requirements by simply training the limbs to "replay" previously stored successful movements for a priori sensed positions of body and limb positioning. This allows the robot to "remember how to walk" rather than "computer how to walk" for every ambulation cycle. In the early 2000's many teams applied genetic programming to train mechanical robots in virtual environments ...allowing them to build the statistical maps of successful ambulation for given terrain encountered....and here we are...2013 and seeing the fruit of these advanced methods in the work of Raibert (now head of Boston Dynamics).

Big Dog


Little Dog


:All use these critical insights of distributed sensation and statistical learning to reduce computational complexity by orders of magnitude BUT all the proof we need to know that current method still have lots wrong is that no robots currently are as fast or agile on uneven or mixed terrain as a roach.

To me this means quite simply that either the type or amount of distributed sensation necessary to achieve that level of dexterity is not yet discovered. I don't think it has anything to do with the computational muscle...which at this point is quite overkill for the problem by orders of magnitude.

The work I've been doing with the Action Oriented Workflow algorithm is very much related to these ideas, AOW is a generalized algorithm for defining arbitrary "action" attributes these are then sampled in as dense or sparse a set as necessary to gather data on when those actions are performed. The Action Delta Assessment algorithm is the underlying statistical learning function for the algorithm, allowing historical information for action execution to be compared in real time in a distributed fashion...precisely as what is needed to refine ambulation in robotic limbs.  It is quite simple to see that mechanical ambulation of limbs is directly analogous to this  , I have some ideas on how I can apply the algorithm to discover and learn these patterns but am focused on applying AOW to the abstract action space of interacting human and business objects in software (to learn and refine). The fractal nature of the algorithm makes it ideal for solving problems of very messy data sets once the sufficient level of resolution to the "action" points are made.



Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…