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
pre-import PAINT checks, PAINT IGNORING TAXON RESTRICTIONS #1873
Comments
PANTHER family issue ?
see |
|
|
|
Does this mean that the taxon checking code was removed from PAINT? It use to be built-in. |
I guess some will be for checking the PAINT annotation. I think ssn6 is a panther family issue? The taxon checks don't appear to be working. I think this might be a general GO issue now I think about it. Let me know if you want these 2 split out into different tickets. |
see #1954
(Tra2 in NuA4 is a pseudo-kinase, I think this is a general across species thing but I'm not sure) |
we wouldn't make these annotations:
|
|
see
|
|
|
see InterPRo summary the phosphate transport is from some old 1996 genetics, indirect (queried original annotation with SGD) 2/Apr/2018, I followed this up with SGD, the original annotation was deleted |
I scanned the first 1000 they look pretty good!) It would be really helpful to suppress redundant annotation more generally ..... |
We can't import the PAINT annotations into PomBase until these are fixed. However, the pombe annotations are now in AMiGO. Because they have the incorrect gene ID in the db object symbol column they are also causing problems for downstream softwares (see helpdesk ticket). |
Right, I forwarded your message to Anushya and Huaiyu to draw their
attention to this.
…On Mon, Apr 2, 2018 at 12:48 PM, Val Wood ***@***.***> wrote:
some of these will need to be addressed by PAINT curators.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1873 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABcuENlWRWf_h3HX67at8OT5PDTL15JXks5tkoCOgaJpZM4So_9y>
.
|
Other than the taxon restriction issue I think they are mostly annotation problems. .... |
@pgaudet this is an earlier batch. Do you want these into separate tickets? |
Please create separate tickets. Thanks ! Pascale |
Is that applicable to these reports? As I understand it, the taxon constraints are already present in the ontology, but annotations that should be flagged or blocked are getting through. Is that still an ontology issue? |
yes I think in many cases the taxon restrictions are present but the taxon restrictions are not in place. I have asked about this in multiple tickets. anyway I'll start by separating this list out. |
ticket about taxon checks (and other QC checks) |
There are 2 issues really...... 1 . Why aren't the taxon restrictions being included more generally (i.e when a gene products is annotated to a taxonomically restricted term, why isn't it flagged in the logs. but Both of these problems need resolving. The taxon checks not working issue is already reported to @cmungall The entries in this ticket related to taxon checks is about PAINT ignoring taxon restrictions.... |
It seems to be a mixture. I'll move any queries that do not appear to be this particular problem to separate tickets |
@ValWood Thanks, Pascale |
OK this particular ticket is now only about PAINT ignoring taxon restrictions. |
Thanks ! |
If it helps, taxon restrictions are being ignored for everything, and have been for a while. Not just for PAINT (although I had assumed that there would be an extra upstream step to prevent PAINT annotations being created if a taxon restriction exists?) |
GO:0060271 | cilium assembly | Never in Taxon | 4890 | Ascomycota via |
There ought to be (and indeed use to be) at least two built-in checks for passing the taxon constraints. First during PAINT handling and second during the standard pipeline
|
Moved to implementation ticket here: geneontology/go-site#758 |
We should leave this ticket open as it provides nice examples to do QC. |
@pgaudet If they are to be implemented, they should go with the ticket; if they are documentation, the wiki may be a more appropriate place. |
I think this is all done. Please reopen if not. |
this batch should be taxonomically restricted:
fhl1 forkhead transcription factor Fhl1 cell differentiation GO_Central Schizosaccharomyces pombe IBA PANTHER:PTN001371846 PAINT_REF:11829 20170427see #1873
fhl1 forkhead transcription factor Fhl1 anatomical structure morphogenesis GO_Central Schizosaccharomyces pombe IBA PANTHER:PTN001371846see #1873
MULTICELLULAR ORGANISM DEVELOPMENT IS TAXONOMICALLY RESTRICTED FOR YEAST
(I would question this annotation more generally anyway)
THIS TERM SHOULD BE TAXONOMICALLY RESTICTED ITS PARENTS ARE
geneontology/go-ontology#15685
THIS TERM SHOULD BE TAXONOMICALLY RESTICTED ITS PARENTS ARE
CELL MIGRATION IS ALREADY TAXONOMICALLY RESTRICTED, IGNORED BY PAINT???
GO:0040011 | locomotion | Never in Taxon | 451864
CILLIUM ASSEMBLY IS ALREADY TAXONOMICALLY RESTRICTED, IGNORED BY PAINT???
GO:0060271 | cilium assembly | Never in Taxon | 4890 | Ascomycota
The text was updated successfully, but these errors were encountered: