World Compartment

AUTHOR: Dr. Gerd Döben-Henisch
FIRST DATE: December 28, 1995
DATE of LAST CHANGE: January 29, 1996



A world compartment is an autonomous process which has to be started started by an owner. It can either operate as a single process without any neighbours or it can be related to neighbours through a world master process. It has to be decided by the owner which one of these both cases has to be selected.

If a world compartment has to collaborate with a master process, it has to communicate with the master process, has to ask for a free section and will get from the master process the names of possible neighbours.

Whether a world compartment will operate as 'stand alone' or in connection with neihbours, in any case has it then to load a dedicated file with suffix 'world' which contains the information about all objects which will belong to this compartment from the beginning. Thus the world compartment has to generate itself (Jan-29, 96)


If a world compartment is 'installed' we can distinguish the following tasks where the usermanagement is all the times running and all the other tasks are processed in sequential order and then repeated:
  1. Usermanagement
    It has to be set up a usermanagement for the different possible clients of the generated world compartment (including the negotiations with neighbours and the master process).
  2. Receiving action strings
    All autonomous clients can sent action strings to the world compartment process.
  3. Computing world changes
    Induced by the actions or induced by some functions connected to the world data has the world compartment to compute possible changes (e.g. related to shape or position) of the objects and agents of the world compartment.

    If an object moves across the border of a compartment and there is no neighbour but a free section, then will the actual world compartment act in a twofold way: (i) If the client is a pseudoknowbot then will it ask this moving object whether it will cancel the action to stay in the actual world compartment or whether it will log out. In all other cases (ii) will the world compartment log out the client. If the client has sensory organs (like a knowbot), then will the client receive a specific 'border-sensation' if they are close to the border. This gives these objects a chance to built up an internal model of the border. Thus 'borders' become a property of the worlds they are living in.
  4. Computing collisions
    With regard to the computed possible changes the world compartment process has to compute possible collisions between objects and the effect of these collisions for the intended changes.
  5. Computing sensory values
    After the changes having beeing fixed the world compartment process has to compute the effect of the new configuration with regard to the sensory organs of all autonomous clients and has to generate sensory strings.
  6. Computing update values
    If the geometry has changed then will all clients, which have views into the world, need the information about the changes insofar the changes are in the scope of their view.



Comments are welcomed to kip-ml@inm.de
INM

Daimlerstrasse 32, 60314 Frankfurt am Main, Deutschland. Tel +49- (0)69-941963-0, Tel-Gerd: +49- (0)69-941963-10