-
Notifications
You must be signed in to change notification settings - Fork 6
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
GO Error Reports: Deprecated rules in report; Warnings vs. errors; Counting #387
Comments
I looked through the wiki for user-oriented SOP docs but not sure if there's anything other than https://wiki.geneontology.org/Release_Pipeline#Annotation_QC_checks ? |
It looks like http://current.geneontology.org/reports/rgd-summary.txt is not behaving correctly? I think there were two kinds of scripts, one with owl-tools and one with ontobio, and some rules were implemented in both (although the older owl-tools implementation should be removed when the newer ontobio implementation was done.) In any case, the correct file should be: http://current.geneontology.org/reports/rgd-report.html#rmd @tutajm , where is the doc stating that you should look at http://current.geneontology.org/reports/rgd-summary.txt and then look for details in the other files, f.e http://current.geneontology.org/reports/rgd-report.html ? We should update that documentation. Thanks, Pascale |
It's odd because these .txt files are not available in our files: @kltm Should they even be generated? Indeed gorule-0000014 is deprecated, and not shown in other reports. Thanks, Pascale |
@pgaudet The (Also geneontology/go-site#1816) |
Regarding question: "where is the doc stating that you should look at http://current.geneontology.org/reports/rgd-summary.txt and then look for details in the other files, f.e http://current.geneontology.org/reports/rgd-report.html ? " It is my personal workflow, not in any particular docs: I am simply looking first at the summary file, to see if there are any issues classified as 'Error'. And then I am looking at the detailed report to see the actual problematic lines. Issues tagged as 'Error' will make me look into the problems promptly. However, when seeing 'Warning' issues, (often supplemented by comment that they were autocorrected) I usually go to my other tasks. That's why I liked the summary file to quickly see what's going on with RGD GAF submission. |
Thanks for the clarification. Looks like these files are out of date compared with the current workflow (since this error does not appear in other reports). @tutajm Can you use http://current.geneontology.org/reports/rgd-report.html#rmd in your workflow? @kltm can you stop producing these .txt files? Thanks, Pascale |
@pgaudet That ticket now at geneontology/pipeline#281 and in project |
This was emailed through helpdesk, but there appear to be at least a few different things to be addressed so this ticket can be moved/duplicated as appropriate.
The text was updated successfully, but these errors were encountered: