Classical Bits
A very brief review of how classical bits work
Last updated
A very brief review of how classical bits work
Last updated
Computers require information to be passed to them in a very specific format. We must include explicit instructions about what to do next, for every single step of the process. Bits are the basic units of information on a computer system - they provide the basis for all instructions and decisions made on the system.
Bits contain exactly one piece of information each - 1 (for yes, true, on), or 0 (for no, false, off). For non-theoretical systems, this means "high" voltage for 1 and "low" voltage for 0. The bit is a physical quantity - we can measure it any time we like, but it needs to be stored (Vahid, F. & Givargis, T. - 2002).
You can see in the image above a voltage graph that illustrates this - the low portions are our 0 bits and the high portions are our 1 bits.
In this situation we can tell two things for sure:
First, a classical bit can only exist in one state at a time - it's either on or off. We can look at any time we like... it'll always be doing the same thing. We could even figure out the state of a bit indirectly - other information could lead us to the fact of what state that bit is in.
Second, a single bit isn't particularly useful... we can't do very much work with it. It's the combination of bits (preferably a whole bunch of them) that makes them useful.
Because a classic bit is a property of voltage, electricity going through a wire, there is potential for noise in our information.
We purposefully put a relatively wide gap between what we consider to be on and what we consider to be off. If the difference in voltage between the two states is too close together, we get a mushy answer. This is because electricity is electrons traveling along the wire - we're never in a place where there are no electrons traveling along the wire at all. So technically the wire is never "all the way off".
How does the computer know if some kind of problem has occurred? Not a "dead stick of RAM" problem, nor a "my code won't compile" problem. A fundamental problem.
Each "wire" gets measured by the system... each bit "self reports" about the state that it's in. How do we know that it's telling the truth?
In a regular computer system we do this through some clever math. We force the computer to check it's work and prove that the answer we got really is the answer the system arrived at. This allows us to rely on these fundamental, irreducible answers. The result is correct, the noise levels in our information remain at acceptable levels (Nielsen, M. - p. 8).
This concept will become important later on. We need to understand the clarity of the information we're looking at. How much precision can we expect?
Providing instructions with bits requires breaking down problems into yes or no decisions. By combining bits using computer logic, we can build up simple (atomic, irreducible) instructions into something more useful.
How is the result of combing to different bits? It depends on the operation we'd like to preform.
Boolean logic gives us a well defined set of fundamental operations, as well as a system by which to combine these into larger instructions. The idea is essentially that certain logical combinations of 0 and 1 (or true and false, or on and off) can be derived, and that all computations can be preformed based on those.
For example, what if we wanted to combine two bits and , such that if one of them is 0, the result is 0?
AND
0
0
0
0
1
0
1
0
0
1
1
1
Here we are. If AND are 1, we get 1. In any other situation, we get 0.
We'll see later on that for more complex combinations of bits, we can define a transformation matrix for these operations which takes our input and produces the output.
Other important operations include OR (if OR is 1, the result is 1), and NOT (given produce the opposite of ).
