Re: [beam] Re: Wire Computing? A Theory
- Martin Jay McKeeI agree whole-heartedly that BEAM still has great potential, even if it is just for fun. It is the same everywhere... why duplicate simple CPU architectures in discrete logic or FPGAs? There is not "advantage." Why create yet another imperative programming language. But, more than just for the play aspect, I think it is important to consider the fact that people learn most effectively when they are playing. We do it all the time as children, and it's okay. As we get older, play starts to become a bad word, but the way our brains are wired doesn't change. Sometimes, doing "simple" things just for fun is the most efficacious way to move forward. It can get one's brain out of a rut and lead you to new discoveries.I have become quite aware, over the past few years, how powerful non-traditional use of sensors can be. By rearranging them one can force particular behavior or avoid weaknesses ( blind spots ). A combination of flexible control circuitry, careful sensor layout, and careful tweaking, certainly do show their potential in the spider bot. The behavior of the robot is, as you say, quite complex and impressive. Sadly, it wouldn't be able to handle much from a mechanical standpoint. Even the "obstacle" test ( with chop sticks ), is fairly simple to achieve. I would be surprised if it were not almost immediately stuck when placed in a real natural environment. But that's not the point. The mechanical design could be expanded and the same concepts used to control it. The result would be a more capable robot. The question becomes one of how much work is required and what the perceived benefit is. If the benefit is that one has fun in the process, anything is justifiable. And anything can add to understanding.
On Tue, Jul 30, 2013 at 11:00 PM, connor_ramsey@... <connor_ramsey@...> wrote:
Forgot to mention, I just got an idea for a solar engine that's like a type 1, except the charge rate is responsive to motor stall, wherein the motor continuously draws current from the solar cell even while the SE is charging, but the SE will only actually discharge when the motor starts spinning, meaning it will pulse very quickly when picked up, but if a motor is stuck, it will wait until there's enough power to free that motor to discharge. I think this would make for a more life-like bug, having an internally dynamic energy metabolism, and probably more efficient, because the bot only charges up as much as it needs in order to start moving, which means it only takes as much time to charge as absolutely necessary.
I want to add flagella to make it easier for the bug to get out of a stuck position, by adding some of the merit of a turbot. And combined with the near-sighted photophobic light sensitivity of the spider-bot, I think this could make for an incredibly interactive device.
I think people here have forgotten that even if BEAM loses its place, it's still fun to play around with.
- Yeah, the usability bit is a primary focus of mine. Just for fun, really, I've taken an approach at a very traditional style, basically using a set of counters in place of an actual processing unit. At it's simplest, it lacks the hardware to perform Boolean logic operations outside of 1's and 2s complement, but these can still be used to simulate logic functions in a few cycles. It can also simulate bit shifting easily enough by multiplying or dividing by 2. It also places quotients and remainders into different registers for easy handling of remainders. Not to mention floating point math isn't difficult, either. It could even perform <, =, > comparisons between values. As a matter of fact, I can't really say that any electronic computer has ever been built in this fashion. I'm pretty much basing the design entirely on DigiComp2, a mechanical 4-bit binary computer distributed as an educational toy from 1968-1976.
Yes, the 1-bit processor array concept is in fact cellular automata, which is why I refer to each unit as a "cell". I don't entirely understand bandwidth, yet. But the idea doesn't really focus on that. It regards robustness of the system, as well as massive parallel processing without most of the usability problems. I would also think it much more flexible, because a key construct is that each cell can alter its connectivity with its neighbors. It would take several orders of magnitude more component failures to trash the system than your traditional hardware, it could also be incredibly fault tolerant, and I'm thinking on the lines that the entire system would be programmed as a whole, so that determining how each cell should connect can be left up to the OS shell. Also, even if bandwidth restricts how quickly information is processed, another perk of the idea is that a very large amount of data could be processed at once.
On a side note, I once came up with an idea for a machine that was mostly electronic, but stored data temporarily as photon states(like, particle for 0 and wave for 1), and would be able to take advantage of the fact that photons, being 4-dimensional objects, can move in more directions than we can perceive, and thus allow the machine to literally do everything at once. What I mean is that each new cycle would take place in the same time frame as the last cycle, so that it could register an infinite amount of data in about a billionth of a second or so. It would only ever have to go forward in time if it needed to write a result back to main memory or update I/O, because the way it works, the events that occurred in previous steps literally would have never happened, and so the electronic memory wouldn't be able to remember such a result, and the outside world could only observe the final state of the program, if there was one. Fundamentally it is a photon based delay line with a negative delay. As in, instead of the delay propagating forward in time, it "rewinds" time slightly. So the potential would be literally instant computation, a stack of infinite size could be fed into the computer and processed in less than a billionth of a second, and an entire program run could be accomplished in the same amount of time. Branches and subroutines would be included. Only writing data back to memory or porting to the I/Os would really take any time at all. Only the program's final result could be observed from outside, as each step in between would never have happened in our timeline. Also, the program counter would have to be photon based, somehow, since if it was electronic, it wouldn't be able to remember what program line to go to next after time was rewritten again. The only thing I can see being interpreted as dangerous with this is that it does, indeed, rewrite time. But it only rewrites about a billionth of a second each time, and it doesn't effect outside events whatsoever. It has absolutely no way to affect reality.
> For myself, life is catching up with me. Come Monday, I'll be starting a
> new degree ( one not even tangentially related to my first ), so I've been
> rushing around trying to get all that in order -- no time for seriously
> thinking about robotics at all.
> I've only got a minute or two now, but, some few comments. The massively
> parallel 1-bit processors sounds a bit like a cellular atomaton type
> system. I remember having see once ( but can I find it now? of course not!
> ) a computer system that was being developed in that vein, compiler and
> all. There is certainly potential for quite a bit of performance, but for
> maximum performance, the bottleneck is often memory bandwidth, and not,
> strictly, computational. A large number of processors with a handful of
> neighbors and a 1-bit interconnect is not going to help in that line.
> To be honest, much of the architecture design lately has been targeted at
> increasing performance ( adding parallel instruction sets, vectorizability,
> hyperthreads, etc. ) but because of memory access issues and programming
> concurrency issues, simple small instructions and a minimal set of fully
> atomic instructions has seemed to have the best balance of usability and
> performance. No one has really been able to demonstrate an architecture
> that is both highly performant and efficient in the face of concurrency (
> and many parallel computational units ) while remaining easy to program. I
> think what can be said about "traditional" architectures, is that they are
> easy to understand and they work "well enough."
> Back to work...
> Martin Jay McKee