Ben: It's a little more than that (more than just speed optimization), because the declarative knowledge may be uncertain, but the procedure derived from it will often be more determinate... [...] Well, we are trying to make NOvamente actually do stuff (and succeeding, to a limited but
You are placing your aesthetic preferences for how an AGI should work over the data regarding how real intelligences do work. Knowledge clearly becomes proceduralized and inaccessible to reasoning
with use.
I see your point now. I guess proceduralization is quite necessary for efficiency, rather
On 6/3/06, Ben Goertzel [EMAIL PROTECTED] wrote:
It's a little more than that (more than just speed optimization),because the declarative knowledge may be uncertain, but the procedurederived from it will often be more determinate...
I'm curious - how can a procedure be more certain than the
On 5/30/06, Yan King Yin [EMAIL PROTECTED] wrote:
It seems that your approach is to store the function add(x,y) directly
*inside* a node. This destroys the nice uniformity of the KR. Secondly,
the AGI should be able to process addition just like ANY other concept.
add(x,y) is inside a node
On 6/2/06, Charles D Hixson [EMAIL PROTECTED] wrote:
Rule of thumb:First get it working, doing what you want.Thenoptimize.When optimizing, first check your algorithms,then check tosee where time is actually spent.Apply extensive optimization only to
the most used 10% (or less) of the code.If you
Mike Dougherty wrote:
On 6/2/06, *Charles D Hixson* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Rule of thumb: First get it working, doing what you want. Then
optimize. When optimizing, first check your algorithms, then
check to
see where time is actually spent.
Ben:
The procedures contained inside nodes are expressed as tree structures which may be textually expressed in a language called Combo.These Combo procedures may be expanded into semantic nodes and links for the
purpose of reasoning on them.Also, inferentially derived knowledge expressed as
YKY,
First, can you define procedural knowledge?
I don't want to give a formal definition in the context of this email
discussion...
The informal notion is a piece of procedural knowledge is something
that can directly be used to generate a series of actions.
Here directly should be
After reading Ben's response I had to ask- what possible value would
there be in NOT pre-compiling reusable procedures? Advocating a
strict adherence to a single type of general purpose container when
there is a clear advantage to specialization sounds like idealistic
dogma. When my existence is
