Re: Wire Computing? A Theory
- I honestly didn't think that capacitor idea all the way through, I have no idea how to isolate individual data sets within a single current level, if that's even possible. And simply getting the data to last a while is a bit tricky as well. So instead of doing that, what I propose is having a sort of analog CPU, with an instruction register composed of, say, memristors or such. This register could hold all the constants, variables, and operators in an equation which is transmitted to the bias points of the ALU. The ALU then takes an input variable(the virtual adress) and plugs it into the the equation to yield the data point located at that address. What the equation is is a polynomial summation of all known data points, so that when any x-coordinate is plugged in, it spits out the corresponding y-coordinate. If the x-coordinate is unknown, however, then rather than reading zero, the CPU will try to generate a y-coordinate for that unknown point based on the function it's currently emulating. If you don't want this to affect the program, then tell it to write first, and then read. However, it could be an extremely useful tool for a learning algorithm, given that it allows the AI to infer what it should do without further instruction, and work off of its initial error. Writing would entail the CPU reworking the entire formula to include the new specified data point. The formula may be as simple as in a pseudo-random generator, perhaps something like x*5-13. This results in a string of seemingly unrelated values that in truth all came from the same function. Not a lot of memory would be required to accomplish this, and the processing unit could supposedly update the formula dynamically.
> One thing that can, indeed, help, is to surround the positive pin by a
> guard ring driven by a buffer. Then, when you disconnect the outside world
> ( through hopefully a single switch ) it is basically just the capacitor's
> self-discharge that is draining it as opposed to external loads, or board (
> circuit ) resistances, etc. There will still need to be a high impedance
> buffer for the voltage "read," but there are plenty of options for that as
> While some few of my ideas might simplify things slightly, I usually do so
> because that means I can add more complexity elsewhere without feeling as
> though I'm overdesigning!
> I certainly think that there are many cases where analog can match or
> surpass the performance of digital. Indeed, the issue is, typically, that
> digital is simply "easier" ( for some definition thereof ). Digital may be
> more repeatable, or less expensive, it may use less power or simply be more
> flexible. In the end, though, top of the line oscilloscope front ends
> remain analog right up to the ( optimized ) ADC. Scaling is done there,
> bandwidth limiting is done there. There are simply things that digital
> cannot touch. The area may be larger ( from an absolute performance
> standpoint ) than analog is currently given credit for and I think it will
> basically take enough people forcing analog back into the light to make
> that clear.
> It is a wonderful thing that there are so many options, it keeps the search
> interesting. And I think it is admirable to push as much as possible
> toward analog. I must admit though, that is just not a place that my brain
> plays as well as the digital domain. I keep trying though!
> Martin Jay McKee
- 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