Sixth Data - Data storage and computing engine

• Download latest snapshot in TAR GZ format
• Browse Git repository online

• Clone Git repository using command:

  git clone https://www2.svjatoslav.eu/git/sixth-data.git
  

• See JavaDoc.

• Brain appears to be natural geometrical/parallel data storage and computational engine:
  • https://www.quantamagazine.org/the-brain-maps-out-ideas-and-memories-like-spaces-20190114/
  • Geometrical Thinking Offers a Window Into Computation
• Even more awesome is that brain appears to operate and is wired as arbitrary/variable dimensional structure: https://singularityhub.com/2017/06/21/is-there-a-multidimensional-mathematical-world-hidden-in-the-brains-computation/
• On top of this, this multidimensional space that brain represents has dynamic/variable resolution/density:
  • https://www.quantamagazine.org/goals-and-rewards-redraw-the-brains-map-of-the-world-20190328
• Such properties allow parallel Geometrical computation and beautifully fits CM-1 Connection Machine architecture (for extra hardware accelerated solution).

https://en.wikipedia.org/wiki/Connection_Machine

Massively parallel (thousands of CPUs) connected via machine's internal 12-dimensional hypercube network allows to efficiently simulate arbitrary dimensional hypercube and network topology between computational units. So that when we are solving/simulating for example 5 dimensional problem, we can arrange computational units into virtual 5D network. See: http://www.mission-base.com/tamiko/theory/cm_txts/di-ch2.html

we can pre-distribute data across computation units and perform parallel geometrical computation.

Lots of problems can be translated to geometry (use any shapes and as many dimensions as you need). Solution(s) to such problems could be then found via geometrical search/comparison/lookup results. As a bonus, such geometrical data storage AND computation can be naturally made in parallel and distributed.

Learning means building/updating/re-balancing the model (the hard part). Question answering is making (relatively simple) lookups (geometrical queries) against the model.

Object oriented programming is inspired by the way human mind operates. It allows programmer to express ideas to computer in a more human-like terms.

It is actually also possible to map object model and relational database to geometrical hyperspace:

• Object or database table row is a point in hypercube arbitrary dimensional space. Each object member variable or database table column can be mapped to its own dimension in hypercube. That is: if class declares 4 variables for an object, then corresponding object can be stored as a single point inside 4 dimensional hypercube. Variable values translate to point coordinates in that hypercube. That is: numbers and string can be translated to linear value that can be used as a coordinate along particular dimension.
• Each object class or database table declares its own hypercube that contain instances (objects) of that class or rows of a table.

Consider we want to create database of:

• Books.
• Authors.
• Effort: Amount of time contributed by every author to every book that he/she wrote.

Information above can be represented as 3D cube where dimensions are:

• X: Book
• Y: Author
• Z: Effort

Points in that cube would nicely capture many to many relations between authors and the books.