Use robot export to generate subset TSV files.#1186
Merged
Conversation
For every subset, we produce a TSV file that is supposed to list the classes in the subset. This is done by a SPARQL query. However, this can be done much more efficiently with a `robot export` command, which is what we do here. On some ontologies that I have tested (Uberon, CL), this is about 2 to 3 times faster. This also automatically exclude blank nodes from the listing, contrary to the original SPARQL query. closes #798
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For every subset, we produce a TSV file that is supposed to list the classes in the subset. This is done by a SPARQL query.
However, this can be done much more efficiently with a
robot exportcommand, which is what we do here. On some ontologies that I have tested (Uberon, CL), this is about 2 to 3 times faster.This also automatically excludes blank nodes from the listing, contrary to the original SPARQL query.
closes #798