-
Notifications
You must be signed in to change notification settings - Fork 53
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
Update Genes from OMIM (do not merge) #7806
base: master
Are you sure you want to change the base?
Conversation
The first draft of the pipeline basically removes _all_ "has germline mutation" relations and swaps in the new ones.
@@ -963,6 +963,20 @@ update-%-mappings: $(TMPDIR)/new-exact-matches-%.owl | |||
make NORM | |||
mv NORM $(SRC) | |||
|
|||
$(TMPDIR)/mondo-omim-genes.robot.owl: | |||
wget "https://raw.githubusercontent.com/monarch-initiative/mondo-ingest/hgnc-template/src/ontology/external/mondo_genes.robot.owl" -O $@ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you asked in the HGNC PRs to re-name this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes thanks, we wont merge this before the mondo ingest pr is merged!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
File has been renamed: mondo-omim-genes.robot.owl
I'm sure this is also on your radar to update it so it pulls from the main
branch eventually.
Just thinking about this now, that necessitates that we merge that PR into main
after merging it into develop
, so I'll do the merging / build running a couple more times when we're ready for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hasn't been merged into main
yet, but has been merged into develop
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once we hear from Sabrina when the alignment work is done, we can decide when to bring updates from mondo-ingest develop
back into main
and make sure the proper test builds are done.
|
||
.PHONY: update-omim-genes | ||
update-omim-genes: | ||
$(MAKE) $(TMPDIR)/mondo-omim-genes.robot.owl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need a -B
at the end of it?
I could be having a brain blip, but I think it needs it, and that's the only reason I can think of for putting this in the body instead of in the prereqs in this case.
Other than this, I don't understand the rest of this robot
-foo, but you know what you're doing it looks like what you did worked correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point about -B, thanks!
We should not have more than 1 gene annotation per disease. In other words, we should only bring gene annotations when there is only 1 disease-1 gene. Having more than 1 gene associated per disease is a bug in the pipeline. Note that the rules for the gene to disease annotations we bring in the Monarch KG are different than what we bring in Mondo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI: Merged other PRs
@matentzn I've just merged the following PRs. Don't know if that means anything for this PR at all; just letting you know.
This PR is a draft. The main issue is this:
How can we justify having so many gene links for colorectal cancer? they are certainly not all strictly causal?
Related