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

Pattern analysis simplifications. #2687

Open
linas opened this issue Jun 13, 2020 · 0 comments
Open

Pattern analysis simplifications. #2687

linas opened this issue Jun 13, 2020 · 0 comments

Comments

@linas
Copy link
Member

linas commented Jun 13, 2020

Pattern analysis can be simplified and generalized as follows:

  • Create a map of all literals contained in a given clause. This effectively creates a unified pmandatory plus absents on a per-clause basis.
  • Then, clause by clause, try to ground those literals, and evaluate the clause if possible (if it is evaluatable).
  • Mark present-links as evaluatable... alter PatternMatchEgine.cc to handle them directly.
  • always has to be kept separate....
  • Remove _fixed and use the ptm->hasAnyVirtual() to determine component bridging.

This is a blocker for #2644

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

No branches or pull requests

1 participant