Back to device_0

-- Guide to the Ridge Route

DEVICE_1


Device_0 is re-organized around the principal diagonal


Device_0 has a constraint that, for every ensemble, the sets of contexts and details must be disjoint. (No context can be a detail, and no detail can be a context.)

The constraint forbids a hierarchical structure as in the adjacent image. Example: book contains parts; parts contain chapters; chapters contain sections.

Re-organization overcomes the constraint.



Data Field: Re-defining the ensemble

An Ensemble is:


Hardware Realization of Device_1

1. The resistance matrix is organized into a diagonal form and each location is identified with a position along the diagonal:

2. Each location has terminal hardware on the diagonal:


Interpretation

There are:
  1. data locations -- in connection with a particular command, a data location takes on the role of context or detail (only one at a time)
  2. on_locations

There are three forms of notation for structural events:

  1. Event notation -- the ordered pair from device_0: e.g, (context - detail)
  2. Matrix notation -- each location identified with a diagonal element (marked with a dot)
  3. Dot-arrow notation -- each location marked with a dot

Structural events can be assembled into structures. A structure familiar to programmers, the linked list, is notated in:

  1. matrix notation (see adjacent image)
  2. dot-arrow notation (see adjacent image)
  3. event notation for the adjacent image (arranged in visually convenient groups):
The notations and the device:

Problems interpreted through notation developed in Stage 3 of Water Trail --


Forward to Device_2.


All materials copyright by Robert Kovsky, 1997.