Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing createNeighbors to omit redundant genus in equivalence axiom… #177

Merged
merged 3 commits into from Apr 25, 2017

Conversation

cmungall
Copy link
Member

@cmungall cmungall requested a review from kltm March 11, 2017 01:01
Copy link
Member

@kltm kltm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cmungall I'm still getting three parents for GO:1902401.

This test, for graph/neighbors-test.obo:

		// 2 axioms for f7:
		// f7 = f5 and p some f6
		// f7 SubClassOf f1

Previously the test assumed f7 is_a f5 was desired as a direct neighbor, in fact it is not.
The main code now correct omits f5, this commit fixes the test to be in line with this
@cmungall
Copy link
Member Author

cmungall commented Mar 11, 2017 via email

@cmungall
Copy link
Member Author

odd, 2490d2c should have failed.

@cmungall
Copy link
Member Author

Add a test explicitly for

[Term]
id: GO:1902401
name: detection of stimulus involved in mitotic DNA damage checkpoint
namespace: biological_process
def: "Any detection of stimulus that is involved in mitotic DNA damage checkpoint." [GOC:mtg_cell_cycle, GOC:TermGenie]
synonym: "perception of stimulus involved in mitotic DNA damage checkpoint" RELATED [GOC:TermGenie]
synonym: "stimulus detection involved in mitotic DNA damage checkpoint" EXACT [GOC:TermGenie]
synonym: "stimulus sensing involved in mitotic DNA damage checkpoint" RELATED [GOC:TermGenie]
is_a: GO:0072400 ! detection of stimulus involved in mitotic DNA integrity checkpoint
intersection_of: GO:0051606 ! detection of stimulus
intersection_of: part_of GO:0044773 ! mitotic DNA damage checkpoint
created_by: jl
creation_date: 2013-09-12T12:07:12Z

@kltm
Copy link
Member

kltm commented Mar 11, 2017

Are the tests now catching this?

@cmungall
Copy link
Member Author

Yes:

assertFalse(neighbors.hasEdge(new OWLShuntEdge("GO:1902401", "GO:0051606", "is_a")));

so the code is functioning as expected, and does not include the redundant genus term

@kltm
Copy link
Member

kltm commented Mar 12, 2017

So the test is passing (with a cut down ontology load?), but my loads still have the errant third edge? Hm.
Is there any way to prosecute owltools about where the edge is coming from on the cli?

@cmungall
Copy link
Member Author

not sure what you mean about the cli query...

@kltm
Copy link
Member

kltm commented Mar 14, 2017

Just trying to find a way to test/probe it without having to load the full ontology set.

@cmungall
Copy link
Member Author

I find it easiest to do ad-hoc tests using--solr-url mock, which will create a Mock solr loader (emits json)

cmungall added a commit that referenced this pull request Apr 24, 2017
@cmungall cmungall merged commit 46ba478 into master Apr 25, 2017
@cmungall cmungall deleted the issue-360-b branch April 25, 2017 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants