« Accueil » : différence entre les versions

De Assothink Wiki
Aller à la navigation Aller à la recherche
Contenu ajouté Contenu supprimé
Aucun résumé des modifications
Aucun résumé des modifications
 
(34 versions intermédiaires par le même utilisateur non affichées)
Ligne 1 : Ligne 1 :

The Assothink approach involves three complementary levels.
The Assothink approach involves three complementary levels.


*A general '''theory''' of associative intelligence
*A general '''theory''' of associative intelligence
*A '''model'''
*The Assothink '''model'''
*A set of hardware and software '''architectures''' implementing the model
*A set of '''software''' components


The three levels are readable as separated parts (sets of articles) in this wiki.
The three levels are readable as separated parts (sets of articles) in this wiki.


An [[abstract]] provides a business oriented summary.
Assothink is a project of [mailto:philippe.gonze@matscape.com Philippe Gonze] hosted by Matscape.


Assothink is a project of [mailto:philippe.gonze@matscape.com Philippe Gonze].
== The assothink theory: overview<br> ==


== The assothink theory: overview ==
The Assothink theory is both ''descriptive'' and ''elaborative''. It is descriptive when attempting to describe parts of ''natural'' intelligence processes. It is elaborative when trying to set up forms of ''artificial'' intelligence.


The Assothink theory is both ''descriptive'' and ''elaborative''. It is descriptive when attempting to describe parts of ''natural'' intelligence processes. It is elaborative when trying to set up forms of ''artificial'' intelligence.
Unlike other approaches (ontologies, dictionaries, thesaurus), the Assothink approach tends to manipulate concepts free from language anchoring.&nbsp; At the basic level, concepts are intrinsically ''unnamable'' objects.


Unlike other approaches (ontologies, dictionaries, thesaurus), the Assothink approach tends to manipulate concepts free from any kind of language anchoring.&nbsp; At the basic level, concepts are intrinsically ''unnamable'' objects.
The key hope in the assothink theory is ''emergence''. This clearly distinguishes Assothink from reductionnist enterprises.<br>


The key hope in the assothink theory is ''emergence''. This clearly distinguishes Assothink from reductionnist initiatives (see "reductionnism vs emergence"),.
A more detailed description of the theory is developped in the [[Theory|theory pages]].


A more detailed description of the theory is developped in the [[Theory|theory pages]].
== The assothink model: overview ==


More recent document describe the theory using various simple but instructive&nbsp;diagrams:
A more detailed description of the model is developped in the [[Model|model pages]].


== Assothink software: overview ==
*[http://www.gonze.org:8080/GwtApp/?e=Alex Assothink overview]
*[http://www.gonze.org:8080/GwtApp/?e=DataModel Assothink data model]


== The assothink model ==
The hardware suited to adequately run Assothink would be very simple but massively parallel, with millions of basic active components; highly interconnected. This kind of hardware architecture is not currently available. As a consequence, the Assothink sotware is an '''emulation''' software, running on available components (CPU, memory, OS...).<br>


A detailed description of the model is developped in the [[Model|model pages]].
An intermediary relevant architecture is the [[DPDM_Architecture|DPDM architecture]].


== Assothink architecture ==
You can directly access the online web application on [http://www.assothink.com www.assothink.com]. <br>


The standard computers are poorly adapted to the need on an associative parallel software, like Assothink.
Online '''user guides''' exist for the [[Passive Jelly Browser|Passive Jelly Browser]] and for the&nbsp;[[Active Jelly Browser|Active Jelly Browser]].


So several [[Architecture|architectures]] are considered, more or less realistic, more or less expensive.
Various tehnical notes related to the software are developped in the [[Software|software pages]]. <br>

The currently worked architecture (2012, 2013, 2014) is the [[A3_architecture|A3 architecture]].


== Assothink online ==

You can directly access the online web application (basic architecture) on [http://www.assothink.com www.assothink.com]&nbsp; (note: currentlydisabled).

Online '''user guides''' exist for the [[Passive_Jelly_Browser|Passive Jelly Browser]] and for the&nbsp;[[Active_Jelly_Browser|Active Jelly Browser]].

Various technical notes related to the software are described in the [[Software|software pages]].

&nbsp;


== Additional internal notes ==
== Additional internal notes ==


The current and planned development are in the [[Roadmap|Roadmap]].
Originally the project name was Alex. This was the [[Alex old main page|old main page of the Alex project]].

Originally the project name was Alex. Both names refer to the same project, but Assothink is used for the model and for the theory, while Alex would be used to name the emerging object with AI&nbsp;capacities.


And here is an overview of the Alex [[Phasing|phasing process]].
And here is an overview of the Alex [[Phasing|phasing process]].

&nbsp;

&nbsp;

== Project sizing and status&nbsp;(as of&nbsp;end of 2016) ==

The project hibernates since 2014, the main reason being its global size (human resources, staffing, time horizon, financial resources).&nbsp;

It is now considered that

*a minimal staff would include&nbsp;3 programmers
*a reasonable and effcient staff would include 3 more profiles (including probably an advanced linguist).
*staffing might give possibly work to 20+ profiles (depending on the assigned goals)
*financial resources for entreprise-based project should then be at least&nbsp;200 k€ per year during at leat two year
*public money is certainly available for such projects (european&nbsp;? , national&nbsp;? , chinese&nbsp;? ...) but public money requires academic frame or enterprise frame (with mid/long term vision)

&nbsp;

&nbsp;

&nbsp;

&nbsp;

Dernière version du 26 janvier 2017 à 19:29

The Assothink approach involves three complementary levels.

  • A general theory of associative intelligence
  • The Assothink model
  • A set of hardware and software architectures implementing the model

The three levels are readable as separated parts (sets of articles) in this wiki.

An abstract provides a business oriented summary.

Assothink is a project of Philippe Gonze.

The assothink theory: overview

The Assothink theory is both descriptive and elaborative. It is descriptive when attempting to describe parts of natural intelligence processes. It is elaborative when trying to set up forms of artificial intelligence.

Unlike other approaches (ontologies, dictionaries, thesaurus), the Assothink approach tends to manipulate concepts free from any kind of language anchoring.  At the basic level, concepts are intrinsically unnamable objects.

The key hope in the assothink theory is emergence. This clearly distinguishes Assothink from reductionnist initiatives (see "reductionnism vs emergence"),.

A more detailed description of the theory is developped in the theory pages.

More recent document describe the theory using various simple but instructive diagrams:

The assothink model

A detailed description of the model is developped in the model pages.

Assothink architecture

The standard computers are poorly adapted to the need on an associative parallel software, like Assothink.

So several architectures are considered, more or less realistic, more or less expensive.

The currently worked architecture (2012, 2013, 2014) is the A3 architecture.


Assothink online

You can directly access the online web application (basic architecture) on www.assothink.com  (note: currentlydisabled).

Online user guides exist for the Passive Jelly Browser and for the Active Jelly Browser.

Various technical notes related to the software are described in the software pages.

 

Additional internal notes

The current and planned development are in the Roadmap.

Originally the project name was Alex. Both names refer to the same project, but Assothink is used for the model and for the theory, while Alex would be used to name the emerging object with AI capacities.

And here is an overview of the Alex phasing process.

 

 

Project sizing and status (as of end of 2016)

The project hibernates since 2014, the main reason being its global size (human resources, staffing, time horizon, financial resources). 

It is now considered that

  • a minimal staff would include 3 programmers
  • a reasonable and effcient staff would include 3 more profiles (including probably an advanced linguist).
  • staffing might give possibly work to 20+ profiles (depending on the assigned goals)
  • financial resources for entreprise-based project should then be at least 200 k€ per year during at leat two year
  • public money is certainly available for such projects (european ? , national ? , chinese ? ...) but public money requires academic frame or enterprise frame (with mid/long term vision)