CLOSED LOOP INTERVAL ONTOLOGY
       The Digital Integration of Conceptual Form
TzimTzum/Kaballah | Loop definition | Home | ORIGIN    
Please sign in
or register

Email *

Password *

Home | About

Select display
Show public menu
Show all theme groups
Show all themes
Show all terms
Order results by
Alphabetical
Most recently edited
Progress level
Placeholder
Note
Sketch
Draft
Polished


Searches selected display

The Many Forms of Many/One
Universal conceptual form

Invocation
Aligning the vision

Project under development
Evolving and coalescing

Guiding motivation
Why we do this

A comprehensive vision
Ethics / governance / science

Cybernetic democracy
Homeostatic governance

Collective discernment
Idealized democracy

Objectives and strategy
Reconciliation and integration

Reconciliation of perspectives
Holistic view on alternatives

What is a concept?
Definitions and alternatives

Theories of concepts
Compare alternatives

What is truth?
How do we know?

Semantics
How meaning is created

Synthetic dimensionality
Foundational recursive definition

Universal hierarchy
Spectrum of levels

A universal foundation
The closed loop ensemble contains
all primary definitions

Set
Dimensions of set theory

Numbers
What is a number?

Venn diagrams
Topology of sets

Objects in Boolean algebra
How are they constructed?

Core vocabulary
Primary terms

Core terms on the strip
Closed Loop framework

Graphics
Hierarchical models

Digital geometry
Euclid in digital space

The dimensional construction
of abstract objects
Foundational method

The digital integration
of conceptual form
Compositional semantics

Closed loop interval ontology
How it works

Cognitive science
The integrated science of mind

Equality
What does it mean?

Formal systematic definitions
Core terms

Data structures
Constructive elements
and building blocks

Compactification
Preserving data under transformation

Steady-state cosmology
In the beginning

Semantic ontology
Domain and universal

Foundational ontology
A design proposal

Coordinate systems
Mapping the grid

Articles
From other sources

Arithmetic
Foundational computation

Plato's republic and
homeostatic democracy
Perfecting political balance

Branching computational architecture
Simultaneity or sequence

Abstract math and HTML
Concrete symbolic representation

All knowledge as conceptual
Science, philosophy and math
are defined in concepts

Does the Closed Loop
have an origin?
Emerging from a point


Theme
Computer hierarchy of abstraction
Placeholder

Definition / description

The Computer Level Hierarchy

If a machine is to be capable of solving a wide range of problems, it must be able to execute programs written in different languages, from FORTRAN and C to Lisp and Prolog.

Programming experience teaches us that when a problem is large, we should break it down and use a "divide and conquer" approach. In programming, we divide a problem into modules and then design each module separately. Each module performs a specific task and modules need only know how to interface with other modules to make use of them.

Computer system organization can be approached in a similar manner. Through the principle of abstraction, we can imagine the machine to be built from a hierarchy of levels, in which each level has a specific function and exists as a distinct hypothetical machine. We call the hypothetical computer at each level a virtual machine. Each level's virtual machine executes its own particular set of instructions, calling upon machines at lower levels to carry out the tasks when necessary. By studying computer organization, you will see the rationale behind the hierarchy's partitioning, as well as how these layers are implemented and interface with each other. Figure 2 shows the commonly accepted layers representing the abstract virtual machines.

Figure 2: The Abstract Levels of Modern Computing Systems

Level 6, the User Level, is composed of applications and is the level with which everyone is most familiar. At this level, we run programs such as word processors, graphics packages, or games. The lower levels are nearly invisible from the User Level.

Level 5, the High-Level Language Level, consists of languages such as C, C++, FORTRAN, Lisp, Pascal, and Prolog. These languages must be translated (using either a compiler or an interpreter) to a language the machine can understand. Compiled languages are translated into assembly language and then assembled into machine code. (They are translated to the next lower level.) The user at this level sees very little of the lower levels. Even though a programmer must know about data types and the instructions available for those types, she need not know about how those types are actually implemented.

Level 4, the Assembly Language Level, encompasses some type of assembly language. As previously mentioned, compiled higher-level languages are first translated to assembly, which is then directly translated to machine language. This is a one-to-one translation, meaning that one assembly language instruction is translated to exactly one machine language instruction. By having separate levels, we reduce the semantic gap between a high-level language, such as C++, and the actual machine language (which consists of 0s and 1s). Level 3, the System Software Level, deals with operating system instructions. This level is responsible for multiprogramming, protecting memory, synchronizing processes, and various other important functions. Often, instructions translated from assembly language to machine language are passed through this level unmodified.

Level 2, the Instruction Set Architecture (ISA), or Machine Level, consists of the machine language recognized by the particular architecture of the computer system. Programs written in a computer's true machine language on a hardwired computer can be executed directly by the electronic circuits without any interpreters, translators, or compilers.

Level 1, the Control Level, is where a control unit makes sure that instructions are decoded and executed properly and that data is moved where and when it should be. The control unit interprets the machine instructions passed to it, one at a time, from the level above, causing the required actions to take place. Control units can be designed in one of two ways: They can be hardwired or they can be microprogrammed. In hardwired control units, control signals emanate from blocks of digital logic components. These signals direct all of the data and instruction traffic to appropriate parts of the system. Hardwired control units are typically very fast because they are actually physical components. However, once implemented, they are very difficult to modify for the same reason.

The other option for control is to implement instructions using a microprogram. A microprogram is a program written in a low-level language that is implemented directly by the hardware. Machine instructions produced in Level 2 are fed into this microprogram, which then interprets the instructions by activating hardware suited to execute the original instruction. One machine-level instruction is often translated into several microcode instructions. This is not the one-to-one correlation that exists between assembly language and machine language. Microprograms are popular because they can be modified relatively easily. The disadvantage of microprogramming is, of course, that the additional layer of translation typically results in slower instruction execution.

Level 0, the Digital Logic Level, is where we find the physical components of the computer system: the gates and wires. These are the fundamental building blocks, the implementations of the mathematical logic that are common to all computer systems.

Hide Placeholder Note Sketch Draft Polished

Sun, Apr 4, 2021