Add intermediates option to extract #441
Merged
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.
Replaces #436, from the docs:
Intermediates
When extracting (especially with MIREOT), sometimes the hierarchy can have too many intermediate classes, making it difficult to identify relevant relationships. For example, you may end up with this after extracting
adrenal gland
:By specifying how to handle these intermediates, you can reduce unnecessary intermediate classes:
--intermediates all
: default behavior, do not prune the ontology--intermediates minimal
: only include intermediate intermediates with more than one sibling (i.e. the parent class has another child)--intermediates none
: do not include any intermediatesRunning this command to extract, inclusively, between 'material anatomical entity' and 'adrenal gland':
Would result in the following structure:
You can chain this output into reduce to further clean up the structure, as some redundant axioms may appear.
Running the same command, but with
--intermediates none
:Would result in:
Any term specified as an input term will not be pruned.