Match Tree Implementation Added #6
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Gecode 5.0.0 doesn't allow client code to set propagation level directly any more
* Added check to ExtensionalConstraint::update() to assess whether the extension passed as an argument is empty. If so, the method returns false, signaling that the CSP is unsolvable (since an empty extensional constraint has no models).
* ADDED: Option to filter out static atoms when determining the set of goal relevant atoms * ADDED: Propagated configuration setting all the way down to where it matters
* Removed unnecessary check to avoid overwriting paths to sub goals
* Added ability to print out the arguments used to invoke the planner binary. This is quite helpful when one wants to call the planner manually for profiling etc.
* Now we allocate nodes using an allocator
* Ported Match Tree data structure from LAPKT "agnostic" backend. See class MatchTreeActionManager in files applicability/match_tree.hxx and applicability/match_tree.cxx. * Added option to planner configuration to select what is the implementation of A(s) to use. * Converted GroundStateModel::build_manager() into a factory method of sorts to instance the implementation of A(s) following the settings in the selected planner "default" option set. * Added "default" option set with the match tree activated.
gfrances
reviewed
Dec 23, 2016
| return new SmartActionManager(actions, constraints, tuple_idx, analyzer); | ||
| } | ||
| LPT_INFO( "main", "Successor Generator Strategy: \"Match Tree\""); | ||
| return new MatchTreeActionManager( actions, constraints, tuple_idx, analyzer ); |
There was a problem hiding this comment.
Is the memory allocated to this object freed somewhere??
There was a problem hiding this comment.
Wishful thinking 👎 in action Guillem... I forgot to make it a shared_ptr<>
|
This is related to the discussion in aig-upf/heuristic-via-lookaheads#10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says