"Beau how do you propose something useful as a standalone device would work with your suggestion?"
That is almost like handing someone in the 1800's an airplane wing and asking what you could possibly use it for.
However, something of great interest to me, in answer to your question would be to setup a 'neural-net-engine'... think if each bit progressed internally on each prop building up a histogram for each pin. outside influences (sensors, even triggers) could affect some bits. Over time many 'F' generations back-n-forth between the props you would have a pattern based on the histogram of an event or series of events. This could be broken down into individual frames, or represent large spans of time. A particular setup like this between two propellers wouldn't need HUGE amounts of memory. This just provides an engine, that perhaps other (read one or several) propellers could tie into the 'neural-net-engine' and contribute.
Think of a 'Chair', a simple chair. You had to be told that it was a chair right, but now subconsciously, you know when you see a chair, only because you have identified it with some kind of reference 'data' or histogram. Now imagine several chairs, where each time the histogram builds upon the previous data, and only the common mode information that is pertinent remains.
Anyway, there is way more to this than I can describe here.
"Beau how do you propose something useful as a standalone device would work with your suggestion?"
That is almost like handing someone in the 1800's an airplane wing and asking what you could possibly use it for.
Well, since that was interpreted so generally, why don't you tell us how you would build the *wing* hardware so that we may be able put it to good use?
Then we can worry more about how fast that can be. My bet is that a synchronous 16 bit bus would be faster than an asynchronous 32 bit bus and it would allow bits for I/O in addition to inter-propeller communications.
setup a 'neural-net-engine'... think if each bit progressed internally on each prop building up a histogram for each pin. outside influences (sensors, even triggers) could affect some bits. Over time many 'F' generations back-n-forth between the props you would have a pattern based on the histogram of an event or series of events. This could be broken down into individual frames, or represent large spans of time. A particular setup like this between two propellers wouldn't need HUGE amounts of memory. This just provides an engine, that perhaps other (read one or several) propellers could tie into the 'neural-net-engine' and contribute.
Anyway, there is way more to this than I can describe here.
Now THIS is what I call cool. I'd like to see a separate thread for this topic.
How do I get started?
Comments
Thanks,
-Phil
"Beau how do you propose something useful as a standalone device would work with your suggestion?"
That is almost like handing someone in the 1800's an airplane wing and asking what you could possibly use it for.
However, something of great interest to me, in answer to your question would be to setup a 'neural-net-engine'... think if each bit progressed internally on each prop building up a histogram for each pin. outside influences (sensors, even triggers) could affect some bits. Over time many 'F' generations back-n-forth between the props you would have a pattern based on the histogram of an event or series of events. This could be broken down into individual frames, or represent large spans of time. A particular setup like this between two propellers wouldn't need HUGE amounts of memory. This just provides an engine, that perhaps other (read one or several) propellers could tie into the 'neural-net-engine' and contribute.
Think of a 'Chair', a simple chair. You had to be told that it was a chair right, but now subconsciously, you know when you see a chair, only because you have identified it with some kind of reference 'data' or histogram. Now imagine several chairs, where each time the histogram builds upon the previous data, and only the common mode information that is pertinent remains.
Anyway, there is way more to this than I can describe here.
Then we can worry more about how fast that can be. My bet is that a synchronous 16 bit bus would be faster than an asynchronous 32 bit bus and it would allow bits for I/O in addition to inter-propeller communications.
Now THIS is what I call cool. I'd like to see a separate thread for this topic.
How do I get started?