Add possibility to forbid orientation within same tier in BackgroundKnowledge #253
+73
−1
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.
Added a new attribute to
BackgroundKnowledge, calledforbidden_within_tiers, which is a set of integers that correspond to tiers within which we forbid all orientation.Methods
forbid_within_tierandallow_within_tierare added to add and remove tiers from the new set. By default, the set is empty and orientation within tiers is allowed, as it was before.The method
is_forbiddenis slightly modified in order to check if the two nodes are from the same tier, and if it is the case and the tier is inforbidden_within_tiers, returnTrue.Tested using the PC algorithm.