Comments (8)
I decided to keep all the labelled edges that have been already tried in the graph even if they failed.
The reason for this decision is the following:
If we leave such edges in the graph, these edges let me know what steps have been already tried for the corresponding or-nodes.
This information is likely help us when we change our evaluation strategy from the depth-first search to the best-first search.
from psl.
Still, there are things that do not seem right about cut_edge_to_andnode_if_no_parental_ornode_can_be_proved_assmng_subgoals
.
-
- This checking on the existing of an edge between an and-node and a labelled-edge got the order wrong.
PSL/Abduction/Seed_Of_And_Node.ML
Line 105 in 9084e8e
- This checking on the existing of an edge between an and-node and a labelled-edge got the order wrong.
-
- What is the point of computing this
and_key
here?
PSL/Abduction/Seed_Of_And_Node.ML
Line 110 in 9084e8e
- This
and_key
is meant be identical to the same asandnode_key
passed as an argument here.
PSL/Abduction/Seed_Of_And_Node.ML
Line 102 in 9084e8e
- What is the point of computing this
from psl.
These issues are addressed in 8d490fc.
from psl.
I decided to keep all the labelled edges that have been already tried in the graph even if they failed.
The reason for this decision is the following:
If we leave such edges in the graph, these edges let me know what steps have been already tried for the corresponding or-nodes.
This information is likely help us when we change our evaluation strategy from the depth-first search to the best-first search.
There aren't enough benefits in doing so to justify this complexity of the code.
Even after we adopt the best-first search, we still have to work on the same or-node multiple times.
If necessary, we can cache the results in a separate table, as well.
from psl.
I decided to keep all the labelled edges that have been already tried in the graph even if they failed.
The reason for this decision is the following:
If we leave such edges in the graph, these edges let me know what steps have been already tried for the corresponding or-nodes.
This information is likely help us when we change our evaluation strategy from the depth-first search to the best-first search.
Haha. I am even failing to save the failed or2and edges :D
from psl.
This function is also badly implemented.
PSL/Abduction/Seed_Of_And_Node.ML
Line 138 in 8d490fc
from psl.
This function is also badly implemented.
PSL/Abduction/Seed_Of_And_Node.ML
Line 138 in 8d490fc
This issue is fixed in 8a95d25.
from psl.
It is mostly fixed now.
The new flow is explained here.
We still need to work on bunched conjecturing. But that will be handled in a different issue.
from psl.
Related Issues (20)
- Abduction: should we pass around new `Proof.state` that contain proved conjectures? HOT 2
- Abduction: Don't use Unsynchronized.inc for proof_id in Or_Node.ML HOT 2
- Abduction: Seed_Of_And_Node.ML contains functions that belong to somewhere else.
- Abduction: Do not include refuted nodes in an abduction graph. HOT 1
- Abduction: graph_gg_parent_not_finished_updated HOT 1
- Abduction: lists of completely proved lemmas in Shared State. HOT 2
- Abduction: decremental conjecture identification in each layer. HOT 19
- Abduction: clear shared states before executing a deep abduction. HOT 1
- Abduction: order the terms in the key for and-nodes. HOT 1
- Abduction: The name Seed_Of_And_Node does not reflect what it is. HOT 1
- Abduction: More SeLFiE assertions to prune bad conjectures.
- Abduction: Shared_State for template-based conjecturing. HOT 1
- Can we get rid of chained state from `seed_of_or2and_edge`? HOT 1
- Abduction: More aggressive parallelism for simultaneous abduction.
- Synthetic SeLFiE: Soft Type
- Abduction: print incomplete proof attempts every once in a while
- Abduction: Evaluation script needed
- Abduction: Abduction Prover against MiniF2F
- Past version of Isabelle seems an error in README HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from psl.