-
Notifications
You must be signed in to change notification settings - Fork 13
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
Filter MF unknowns with non-ND evidence out of annotation preview/GPAD #463
Comments
SGD curators would love this too. In our training exercises, we have been hacking this by removing the 'molecular_function' from the annoton so that it doesn't show up in the GPAD/annotation preview, but it isn't ideal. |
This should be live after the next Minerva restart. |
@krchristie can you check that this works as you expect now? Thanks. |
Looking for feedback from @krchristie (or @edwong57 ) before closing out. |
Apologies so slow to get to this, a combination of several different trips with an email rule that isn't specific enough to flag my attention for Noctua tickets I'm mentioned in. For the model I listed above when I opened the ticket, the filtering out of MF unknowns is great, leaving only the component annotations I want. I also tested that root MF annotations do not get filtered out using this model: ID: gomodel:59a105b300000000 Both look good to me. thanks! |
Today at MGI's GO group meeting, we were discussing the presence of the unknown, i.e. root level, MF annotations in the Annotation Preview.
We were wondering if it would be possible to filter out the root level MF annotations with non-ND evidence codes, i.e. the ones made from annotons where the function involved in the process or localized to a component is not known.
ID: gomodel:595a9ee700000731
Name: PMID:27914912-KRC Foxj1 targets
Note that this would only apply to root level MF annotations with non-ND codes. We would still want to be able to make root level annotations WITH the ND code as discussed in this ticket: #320
The text was updated successfully, but these errors were encountered: