Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add api to extract inference trace #48

Open
noskill opened this issue Nov 20, 2019 · 4 comments
Open

add api to extract inference trace #48

noskill opened this issue Nov 20, 2019 · 4 comments

Comments

@noskill
Copy link
Contributor

noskill commented Nov 20, 2019

Sometimes it is useful to have graph or tree for inference.
Like source -> rule -> rule -> rule -> result

Usecases:

  • theorem proving
  • planning
@ngeiswei
Copy link
Member

The backward chainer already somewhat supports that, i.e. the user can pass an auxiliary atomspace where the trace is stored. This is for instance used in the inference control meta-learning experiment https://github.com/opencog/opencog/tree/master/examples/pln/inference-control-learning

For more info on how to do that see (help cog-bc).

Regarding the forward chainer, the C++ code does some of that, but they are no scheme bindings for it. It could be added, although keep in mind that I eventually intend to merge the forward chainer into the backward chainer code (but that may far in the future, although I hope not).

@noskill
Copy link
Contributor Author

noskill commented Nov 21, 2019

I found that forward chainer also writes some trace into current atomspace, though it is not possible to find how all premises became satisfied for current rule application.

@ngeiswei
Copy link
Member

No inference control meta-learning experiments have been attempted with the forward chainer yet, so trace support is lacking.

@ngeiswei
Copy link
Member

The following constitute a start of an API to extract FC traces

https://github.com/ngeiswei/reasoning-bio-as-xp/blob/6006874a9918b29510080d5ef43ffc5b7fc809e4/bio-as-utils.scm#L348-L479

It just needs some work and being moved to the URE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants