OverviewFilesCommitsIssuesDocsReleasesPeers

opencog-agents commits / 5ba28dc

Update the TODO list
5ba28dcbcaec992086a7099df968358e4e665900
by Linas Vepštas <linasvepstas@gmail.com> · 2024-05-03T13:59:05.000Z

Changed files (2) +9 -1

README.md +1 -1
……@@ -3,7 +3,7 @@ Atomese Agents
33Experiments and prototyping for interactive learning agents.
44
55### Status
6Version 0.0.1 -- Extremely early prototyping stage.
6Version 0.0.2 -- Extremely early prototyping stage.
77
88### Overview
99The [Opencog Learn](https://github.com/opencog/learn) project showed
scm/pair-agent/README.md +8 -0
……@@ -15,6 +15,7 @@ environment.
1515
1616## Pair counting agent
1717Prototype proof of concept. Implemented in `pair-agent.scm`.
18Based on demo in `examples/pair-count.scm`, which explains it in detail.
1819Counts word-pairs, observed by looking at a text file. The Sensory API
1920(implemented in `(use-modules (opencog sensory))`) is general enough to
2021allow arbitrary text sources, including chat.
……@@ -56,3 +57,10 @@ Some unresolved issues.
5657 that have a `Filter` in the middle.
5758* End-of-file results in a throw from parser. This is a side effect.
5859 The throw should happen from the file-reader, directly.
60* Update AtomSpace to support an atomic `IncrementLink`. Under the
61 covers, this would call `asp->increment_count(h, key, fvp->value()));`
62 So it has the form `(IncrementLink atom key incr zero)` where `incr`
63 is, for example `(Number 0 0 1)` and `zero` is `(Number 0 0 0)`. Note
64 that this resembles a generic fold. The alternative to this is a
65 `AtomicSetValueLink` which holds a lock to make sure the update is
66 atomic. The risk is that naive users will discover deadlocks. Hmmm.