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

gorule-0000057 is not implemented but showing up in reports #2243

Closed
pgaudet opened this issue Feb 22, 2024 · 11 comments
Closed

gorule-0000057 is not implemented but showing up in reports #2243

pgaudet opened this issue Feb 22, 2024 · 11 comments
Assignees

Comments

@pgaudet
Copy link
Contributor

pgaudet commented Feb 22, 2024

Hi @mugitty

According to @dustine32 , gorule-0000057 was never implemented (see #1553), but it's showing up in reports, see

http://current.geneontology.org/reports/assigned-by-gorule-report.html

Can you please remove it from the pipeline?

Thanks, Pascale

@kltm
Copy link
Member

kltm commented Feb 22, 2024

There is a report filter list in the pipeline (variable) to deal with things like this.

@mugitty
Copy link
Contributor

mugitty commented Feb 22, 2024

@kltm, If the rule is valid, then we need to ensure it is implemented correctly and @pgaudet will add tests. When I discussed with @dustine32, he indicated that the rule was no longer necessary and I was going to remove

@dustine32
Copy link
Contributor

dustine32 commented Feb 22, 2024

@mugitty As @kltm mentioned (different list, sorry), there is a list of GoRules here:
https://github.com/biolink/ontobio/blob/57adf9c2bcdc9385c45116b58535e446f6b30bd0/ontobio/io/qc.py#L950
You can try removing GoRule57 from this list and running the validation to see if the rule row is removed from the assigned-by-gorule-report.html.

@dustine32
Copy link
Contributor

@kltm Is this GORULE_TAGS_TO_SUPPRESS the rule filter variable you were referring to?
https://github.com/geneontology/pipeline/blob/5990c634683d2e5fc51f6c1baa4db8e8cc67b96b/Jenkinsfile#L135C4-L135C27

@mugitty
Copy link
Contributor

mugitty commented Feb 22, 2024

I know how to remove the rule so that it does not appear in the reports.
@pgaudet has deprecated the rule, however @kltm may want to keep it. I am not sure how to proceed. There are config parameters that can be passed to filter out the annotations.

@kltm
Copy link
Member

kltm commented Feb 22, 2024

There are two approaches: one is not running the rule (internal variable); one is filtering the rule (pipeline variable). Both are viable. It may be worth considering on what timeline the activity of the is being considered. If it is not planned and has no code, it may be worth excising from ontobio altogether as it may be more confusing for future developers figuring out what is going on. I'm happy with any decision made here by the two of you.

@kltm
Copy link
Member

kltm commented Feb 22, 2024

@mugitty If the rule is deprecated, I would consider excising unnecessary code and commenting as such in the rule implementation notes in the rule metadata itself.

@mugitty
Copy link
Contributor

mugitty commented Feb 22, 2024

#biolink/ontobio#667

@pgaudet
Copy link
Contributor Author

pgaudet commented May 6, 2024

Not shown in go-rules reports, so this is OK for me -

@kltm Do you want a 'cleaner' solution to this?

@kltm
Copy link
Member

kltm commented May 6, 2024

@pgaudet I'm okay with whatever is practical, but I just wanted to make sure we're all on the same page about expectations.

@pgaudet
Copy link
Contributor Author

pgaudet commented May 29, 2024

Working as needed for curators. We can revisit the system if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants