Version 0.0
Draft.
Discussion on this post can be found: here.
~
As a pre-requisite for this post, see: A way to no-thing but perhaps dust. Which takes a purely reductionist view. This post is the opposite of the reductionist view in that it examines the effects of things that take more than a single quanta to represent or are therefore "abstract."
~
Visual memetics of abstract reality: Parabola.
Lyrical memetics of abstract reality: Parabola.
In our Universe and perceived reality there are objects we interact with. These objects are not "real" in an absolute sense rather they are simplifications created by our senses that we interact with at "higher" levels of reality. A "higher" level simply means that the complete details of an object have been collapsed somewhat and we do not perceive the complete detail of an object when interacting with it.
All the reality that is presented by our senses is abstract. We are incapable of perceiving the "real" quanta and instead our senses operate above the base level of reality. We are also thinking beings in that we process information and emit actions into our environment which in turn absorbs those actions and results in changes that follow a logical physics.
Everything in our Universe can be viewed as a "thinking" thing. A rock sits there all day and "thinks" about being a "rock." A solar-system "thinks" about being a "solar-system." You "think" about being "you." This may be tautological in a sense but the illustration is that things that "are", "are."
With the addition of "time" another property of our Universe is exposed in thinking things. This is "information flow." When multiple thinking entities interact, information can be emitted from one and absorbed by another, processed in both and repeating as long as the entities are within an affect range of each other. The process of absorbing, processing, and emitting information between entities can be described as "communication." With a "calculating" stance taken towards this process entities within an affect range of each other may be "combined" into a "higher-level form" or "entity" for the duration of the affect. This "collapsing" is similar to the sense that 2 + 2 can be thought of as 4 while they are together.
"Higher-level" entities may or may not be apparent to the entities they are composed of. The composing entities have their own reason and reality and these are separate from the combined entity they collapse into. A "higher-level" or "collapsed" entity composed of other entities has its own reality with its own objects and logical physics to interact with but it's reality is a further abstraction and the "realities" of its composing objects are not necessarily able to be sensed from the "higher-level".
There, however, is still calculation that ebbs between the levels of reality. The compositions that create a "higher-level" entity still do processing on their own levels and while they do their processing, their own affects are emitted and absorbed on their own level of reality. These information transactions affect the higher-level collapsed entity as well.
All levels of reality are represented in the totality of our Universe, all of them "are" at the same time. Anything that has a logical structure to it is valid in the totality but as humans, our reason may not perceive everything that is valid in a specific moment.
Saturday, July 24, 2010
Monday, June 21, 2010
A way to no-thing but dust.
Zen
Expressions are computed and the representations are in substrate. Every thing is an expression, every substrate is matter, for our Universe.
All scales and scopes have their own expressions.
Finely interwoven expressions are, we know not the true physics.
Reminded that there is only dust. Endless forms evolved and evolving are representations and are not dust. Arranged dust, yes, are, no.
Considering arrangements of word dust, which is still far removed from real dust:
Each word is a concept and is a machine. How they run together defines the qualities and quantities of thought. Still, there is only dust.
Language is but a machine, and I push and pull it's levers. And the machine crumbles to dust in an instant.
Reason
The dust is a metaphor for matter. There is only dust is a purely reductionist view: the only thing that exists are quanta and everything else made up of more than a quanta is a representation. Representations interact with each other and have logic but they do not actually exist: only the quanta exist. There is only dust. A galaxy has a logic to it but there is no galaxy object in our Universe, there is only a collection of dust that the human mind lumps together into a representation and calls that representation a galaxy.
Physics, whatever it may be, is contained within the word "computed."
"what does the computing?"
That is undefined. You could say, it is the mystery of dust.
Dust depends on a base form to the Universe. If there are things infinitely smaller and smaller than quanta then dust becomes just another expression.
Method
The method between the Universe and quanta is recursive. The top is the Universe and the bottom is quanta. Between, the parameter to subdivide or combine with is expressions, which are representations which exist in substrate. The parameter encapsulates phenomena by being generic. There is an assumed base case, the quanta, which ends the recursion when you start at the top but if things go infinitely beyond quanta then the recursion may continue infinitely as well. Beginning from the bottom, at quanta, using the same parameter you can recursively combine towards the top as well. Which also may or may not be infinite. The scaling occurs in either direction, top to bottom, or bottom to top.
The perspective taken with this framework is that of a passive observer. All scales of the Universe have interrelating expressions which you may scale up and down. While scaling the expressions represent an instant in time and are therefore static. Once you have more than one instant then an expression becomes a scope which is a thinking thing, like a solar-system, the scope you may enter and examine it's process but you are never able to directly experience what it is to be the scope.
Consequences
With the set of dust only representing "Reality" representations built on top of that dust have a degree of "realness" that is less than the base Reality. The reality that you and I experience is "real" but it's degree of "realness" is less than dust's degree of Reality.
Saturday, June 19, 2010
Linux Desktop
Here is a short video demonstration of my computer's desktop environment.
For reference, here is how my previous demonstration of a Linux desktop went:
For reference, here is how my previous demonstration of a Linux desktop went:
Tuesday, June 8, 2010
Mnemonics, Statements, and Connectors.
As a continuation of: Continuui, I'm going to examine some of the logic you can get Continuui and Continuums to hold.
A suitable set of mnemonics to practice with is defined: Sid Meier's Alpha Centauri
Each quote on that page is it's own mnemonic, take some time to peruse through them. Most of them are related around fictional modern human issues but the occasional mnemonic is also drawn from our actual history.
Mnemonics can be thought of as a sequence of statements that illuminate various concepts. They work with your imagination to shine light on structure when applied to different situations. The set of mnemonics defines a complex as possible imaginary structure. You ponder pieces of it and relate each piece to your own personal experience. They are in effect programs for specific interrelation of domains. The human mind takes care of all the messy details like making the concepts fit exactly.
Statements are fragments of mnemonics. They are singular logical constructs which relate qualities or quantities or both. Fragments pool around and you launch each one making note of what you think for the following ones.
Connectors can be thought of as little helpers that just gracefully bridge statements. Some classical ones include and, or, and not. Human ones are not so brittle. You can have connectors such as compatible with, is part of, is a flavor of, and as many as you can imagine.
As you practice statements and connectors Mnemonics emerge. Most of your mnemonics will remain unnamed and you just use them by feel.
Mnemonics are what you use inside of Continuui and Continuums.
A suitable set of mnemonics to practice with is defined: Sid Meier's Alpha Centauri
Each quote on that page is it's own mnemonic, take some time to peruse through them. Most of them are related around fictional modern human issues but the occasional mnemonic is also drawn from our actual history.
Mnemonics can be thought of as a sequence of statements that illuminate various concepts. They work with your imagination to shine light on structure when applied to different situations. The set of mnemonics defines a complex as possible imaginary structure. You ponder pieces of it and relate each piece to your own personal experience. They are in effect programs for specific interrelation of domains. The human mind takes care of all the messy details like making the concepts fit exactly.
Statements are fragments of mnemonics. They are singular logical constructs which relate qualities or quantities or both. Fragments pool around and you launch each one making note of what you think for the following ones.
Connectors can be thought of as little helpers that just gracefully bridge statements. Some classical ones include and, or, and not. Human ones are not so brittle. You can have connectors such as compatible with, is part of, is a flavor of, and as many as you can imagine.
As you practice statements and connectors Mnemonics emerge. Most of your mnemonics will remain unnamed and you just use them by feel.
Mnemonics are what you use inside of Continuui and Continuums.
Saturday, June 5, 2010
Continuui
Version 3.20
Continuui and Continuums are mnemonics. As mnemonics you need to practice or train your own set of Continuui and Continuums to use them.
As a pre-requisite for using these mnemonics you should have a basic memory system. What fits well and what I recommend is the Roman Room technique with each Continuui and Continuum being it's own distinct room.
My main goal of writing these mnemonics is to further my understanding of object-orientated programming in a computer. Everything else is secondary but I posted it here so that minds other than myself can winnow out the errors in it and perhaps use it for their own purposes.
--
Continuui and Continuums are both flavors of structure. Continuui are a control structure and Continuums are a value structure.
A Continuui can be thought of as a container containing further Continuui or referenced Continuums. Each Continuui contains a logic to traverse it, values it can report - including consequences, and actions it can perform. Traversing the structure of a Continuui using it's logic you get a result. The type of the particular result depends on how the Continuui represents it's knowledge. In this manner a Continuui is a generic concept that can be used to traverse or evaluate further Continuui and Continuums.
The logic to traverse a Continuui can be thought of as following a sequence of evaluations and actions between the contained Continuui and Continuums. Each Continuum in a Continuui is transformed in relation to other Continuums in the same Continuui. If a further referenced Continuui is not found in the current container the parent container is used for the definition and so on.
A Continuum can be thought of as a Symbol. A Continuum is also a container. As with a Continuui it also contains a logic, values, and actions. Continuums exist in hierarchies and a specific Continuum within a hierarchy is always referenced. The logic of a Continuum processes values contained within itself and if they are not present in that Continuum the parent Continuum is used for the definition and so on. Retrieving or setting a value in another Continuum uses that Continuum's logic.
Programming context: Continuui are roughly equivalent to a program in a computer language. Where they differ is that in Continuui, Continuums: Symbols or variables - are also programs.
--
Defining a Continuum can follow this process:
Continuum. Complete set of all information. The totality of a symbol. Totality means everything that was, is, and will be. To sum up a continuum, logically organize top-down into pieces. Discard all variation or take the set. Sets contain no duplicates. Interrelate* unique pieces into theories. Map sequences of action or consequences through the network of relationships between theories. Define a logic to process sequences of actions and consequences which gives a result. Result quality matches theory quality. At completion, the rest of the result is symbol specific.
* Interrelation is defined depending on the domain of the Continuum.
--
As a usage example:
From the Sciences. Say you have a Continuum named Physics which may reference more specialized sub-Continuums. Physics can be used to evaluate if another named Continuum is compatible with it. You could have a Continuui which contained many named Continuums and the logic of the Continuui is just to test whether each of those Continuums is compatible with Physics. You would winnow out the impossible Continuums you were comparing to the quality of your own understanding of your Physics Continuum.
--
The advantages of using Continuui and Continuum mnemonics is that the processing of information is done in your mind. The human mind is the most powerful computer we know of. The logics a computer is able to process is but a small slice of the logic a human is able to process. The concepts of Continuui and Continuums when combined with a memory system or other mnemonics allows you to logically organize and process the natural world in ways an actual computer just does not compute.
--
Discussion of Continuui to refine further can take place: here.
--
Continues: Here
Continuui and Continuums are mnemonics. As mnemonics you need to practice or train your own set of Continuui and Continuums to use them.
As a pre-requisite for using these mnemonics you should have a basic memory system. What fits well and what I recommend is the Roman Room technique with each Continuui and Continuum being it's own distinct room.
My main goal of writing these mnemonics is to further my understanding of object-orientated programming in a computer. Everything else is secondary but I posted it here so that minds other than myself can winnow out the errors in it and perhaps use it for their own purposes.
--
Continuui and Continuums are both flavors of structure. Continuui are a control structure and Continuums are a value structure.
A Continuui can be thought of as a container containing further Continuui or referenced Continuums. Each Continuui contains a logic to traverse it, values it can report - including consequences, and actions it can perform. Traversing the structure of a Continuui using it's logic you get a result. The type of the particular result depends on how the Continuui represents it's knowledge. In this manner a Continuui is a generic concept that can be used to traverse or evaluate further Continuui and Continuums.
The logic to traverse a Continuui can be thought of as following a sequence of evaluations and actions between the contained Continuui and Continuums. Each Continuum in a Continuui is transformed in relation to other Continuums in the same Continuui. If a further referenced Continuui is not found in the current container the parent container is used for the definition and so on.
A Continuum can be thought of as a Symbol. A Continuum is also a container. As with a Continuui it also contains a logic, values, and actions. Continuums exist in hierarchies and a specific Continuum within a hierarchy is always referenced. The logic of a Continuum processes values contained within itself and if they are not present in that Continuum the parent Continuum is used for the definition and so on. Retrieving or setting a value in another Continuum uses that Continuum's logic.
Programming context: Continuui are roughly equivalent to a program in a computer language. Where they differ is that in Continuui, Continuums: Symbols or variables - are also programs.
--
Defining a Continuum can follow this process:
Continuum. Complete set of all information. The totality of a symbol. Totality means everything that was, is, and will be. To sum up a continuum, logically organize top-down into pieces. Discard all variation or take the set. Sets contain no duplicates. Interrelate* unique pieces into theories. Map sequences of action or consequences through the network of relationships between theories. Define a logic to process sequences of actions and consequences which gives a result. Result quality matches theory quality. At completion, the rest of the result is symbol specific.
* Interrelation is defined depending on the domain of the Continuum.
--
As a usage example:
From the Sciences. Say you have a Continuum named Physics which may reference more specialized sub-Continuums. Physics can be used to evaluate if another named Continuum is compatible with it. You could have a Continuui which contained many named Continuums and the logic of the Continuui is just to test whether each of those Continuums is compatible with Physics. You would winnow out the impossible Continuums you were comparing to the quality of your own understanding of your Physics Continuum.
--
The advantages of using Continuui and Continuum mnemonics is that the processing of information is done in your mind. The human mind is the most powerful computer we know of. The logics a computer is able to process is but a small slice of the logic a human is able to process. The concepts of Continuui and Continuums when combined with a memory system or other mnemonics allows you to logically organize and process the natural world in ways an actual computer just does not compute.
--
Discussion of Continuui to refine further can take place: here.
--
Continues: Here
Wednesday, June 2, 2010
Knowledge Engineer Program
I'm planning a program. It is implemented using Python. It will be GPLv3 so as a public project if you'd like to help out then please post a comment or instructions in any form: hints, tips, where to setup project, similar existing projects, etc.
--
Research has led me to a framework called PyKE. PyKE is a Python Knowledge Engine.
PyKE is a meta-programming framework. Instead of traversing your program using the standard interpreter it in effect caches the traversal using an alternate form of logic processing and these custom sequences of traversal, called plans, can be then stored, executed, modified, or queried.
This in a further effect has the property of "compiling" your Python code to a very efficient form for Python to interpret from Python's point of view. Fast.
PyKE was originally developed as a caching method into SQL databases but was generalized and also contains a complete expert system framework.
--
The program I am planning is intended mainly to give myself some experience with the Python language and standard library with a few additional modules as well. However, as a specialized tool others may find it useful as well.
The program is a "Knowledge Engineer Shell"
Some initial constraints:
-> Completely web-based. It is written as a local web-application server that you point your web-browser at.
-> Uses PyKE as a template web-server to implement a web-application. Optionally, a URL to Class-Method mapping logic may be used from CherryPy.
-> Provides a shell into PyKE.
-> Shell allows manipulation and persistence of user-defined Knowledge Bases and Plans.
-> Knowledge Bases and Plans can be created, organized, modified, and iterated over using the web-application.
-> Graphing functions* are available:
-> * A mini-language to specify a particular view into your information. It may be graphical, textual, or anything else that can be represented in the information. The: Python Imaging Library can generate files to use server-side for the HTML served.
This is pretty general so far but creates hopefully an efficient and expressive interface to generate information for PyKE to consume. Nice web-application for non-programmers to use.
So, if you have any comments at all please do.
Bill.
--
Research has led me to a framework called PyKE. PyKE is a Python Knowledge Engine.
PyKE is a meta-programming framework. Instead of traversing your program using the standard interpreter it in effect caches the traversal using an alternate form of logic processing and these custom sequences of traversal, called plans, can be then stored, executed, modified, or queried.
This in a further effect has the property of "compiling" your Python code to a very efficient form for Python to interpret from Python's point of view. Fast.
PyKE was originally developed as a caching method into SQL databases but was generalized and also contains a complete expert system framework.
--
The program I am planning is intended mainly to give myself some experience with the Python language and standard library with a few additional modules as well. However, as a specialized tool others may find it useful as well.
The program is a "Knowledge Engineer Shell"
Some initial constraints:
-> Completely web-based. It is written as a local web-application server that you point your web-browser at.
-> Uses PyKE as a template web-server to implement a web-application. Optionally, a URL to Class-Method mapping logic may be used from CherryPy.
-> Provides a shell into PyKE.
-> Shell allows manipulation and persistence of user-defined Knowledge Bases and Plans.
-> Knowledge Bases and Plans can be created, organized, modified, and iterated over using the web-application.
-> Graphing functions* are available:
-> * A mini-language to specify a particular view into your information. It may be graphical, textual, or anything else that can be represented in the information. The: Python Imaging Library can generate files to use server-side for the HTML served.
This is pretty general so far but creates hopefully an efficient and expressive interface to generate information for PyKE to consume. Nice web-application for non-programmers to use.
So, if you have any comments at all please do.
Bill.
Tuesday, June 1, 2010
Environments, Agents, and Decisions.
I'm fleshing out some systems I intend to write right now.
It will be an environment with agents that are based on a decision system.
The decision system is an expert system. The expert system will include calling other expert systems or recursion as functions or procedures. The rules of the expert system will be based on fuzzy logic for control structures such as 'If' and 'While' and neural-networks for some mapping functions such as 'If a=b'. The expert system will contain custom data types for variables, including the already mentioned fuzzy and neural, and perhaps others such as bayesian and of course boolean.
The agents are where the traversal of decision systems take place. Each agent is expected to contain a Turing complete evaluation and control language. Embedded in this language are functions that provide sensors, effectors, and of course the decision systems. Agents contain their own local variables distinct from decision systems they contain. Agents are controlled by the environment and are therefore modeled after generators. The agent performs the maximum actions it can in the time-slice specified by the environment and then yields back to the environment. In the next time-slice the agent resumes exactly where it left off.
The environment holds agents and contains information that is not local to the agent for the agent to interact with. The environment is active in that it has rules of physics and the like but it is not a decision system per-se. The environment handles scheduling of agents. Agents are synchronized into environmental time-slices for output. The environment may be interactive as in a game or it may require no interaction as in a simulation.
Decision systems represent knowledge, agents represent programs that operate on top of that knowledge, and the environment represents multi-agent coordination.
The net-work of these three systems is filed under: artificial life.
So this is where I am right now.
Doing some digging around I came across an IDE called: breve. It seems to be similar to what I am trying to build so I'm going to spend some time using it and learning lessons from it.
It will be an environment with agents that are based on a decision system.
The decision system is an expert system. The expert system will include calling other expert systems or recursion as functions or procedures. The rules of the expert system will be based on fuzzy logic for control structures such as 'If' and 'While' and neural-networks for some mapping functions such as 'If a=b'. The expert system will contain custom data types for variables, including the already mentioned fuzzy and neural, and perhaps others such as bayesian and of course boolean.
The agents are where the traversal of decision systems take place. Each agent is expected to contain a Turing complete evaluation and control language. Embedded in this language are functions that provide sensors, effectors, and of course the decision systems. Agents contain their own local variables distinct from decision systems they contain. Agents are controlled by the environment and are therefore modeled after generators. The agent performs the maximum actions it can in the time-slice specified by the environment and then yields back to the environment. In the next time-slice the agent resumes exactly where it left off.
The environment holds agents and contains information that is not local to the agent for the agent to interact with. The environment is active in that it has rules of physics and the like but it is not a decision system per-se. The environment handles scheduling of agents. Agents are synchronized into environmental time-slices for output. The environment may be interactive as in a game or it may require no interaction as in a simulation.
Decision systems represent knowledge, agents represent programs that operate on top of that knowledge, and the environment represents multi-agent coordination.
The net-work of these three systems is filed under: artificial life.
So this is where I am right now.
Doing some digging around I came across an IDE called: breve. It seems to be similar to what I am trying to build so I'm going to spend some time using it and learning lessons from it.
Subscribe to:
Posts (Atom)