-
Notifications
You must be signed in to change notification settings - Fork 10
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
PTN002521528 / PTHR24418 NOT issue #3701
Comments
@pgaudet Right now the qualifier checking is same-term only: From the perspective of the 'non-membrane spanning protein tyrosine kinase activity' IBA, only all experimental annotations to its same term and same gene are checked. Since there are none of these to compare, there can be no qualifier disagreement, so we think the IBA is good. But we can talk about expanding it to also check experimental annotations to all ancestor terms, which would include 'protein kinase activity'. The other issue is we don't consider IKR to be "experimental" in this check, so the FlyBase IKR wouldn't be checked even if we did expand to ancestor terms: Perhaps for the purposes of comparing qualifiers here, we should expand this list of evidence codes to include IKR? Good topic for the PAINT call! |
FYI @hattrill |
Thanks @mugitty! Another good reason for me to finally finish the XML-to-GAF IBA formatter so that I can use the IBAs directly output from the PAINT tool. |
Hi @dustine32 @mugitty could you explain what is going on? Has a fix been made to the PAINT tool or are you dicussing a pipeline issue here? |
@hattrill Right, I was referring to a pipeline change to make the fix. Specifically, looks like the logic in the PAINT tool (as @mugitty pointed out) is blocking the IBA like we want, and I'm currently working to derive the PAINT IBA GAF files directly from this logic. (short answer: not fixed yet, but will be fixed soon!) |
Thanks @dustine32 I am unconfused now! :-) |
@pgaudet @hattrill While using this ticket's NOT conflict example for developing pantherdb/fullgo_paint_update#52, I noticed this change in AmiGO: Just tagging @thomaspd because we were just discussing this strategy and I think he'll approve of it! |
Thanks @dustine32 - that looks good to me from a FlyBase perspective. Does the PAINT 'NOT' only appear in the branch containing fly Wsck? I guess it should do as other members of pthr24418 are bona fide tyrosine kinases. |
@sjm41 is right - this only applies to a single sequence, I dont think the NOT IBA should be there, the PAINT curator would not have made an annotation here. The presence of a NOT should prevent the positive IBA from being made. |
Thanks for the quick response! @sjm41 This IKR @pgaudet Since the PAINT |
OK I see - attaching a new screenshot because this is different from what we used to have #3701 (comment) |
I think this is now resolved? |
Yes, I think can be closed. |
Hi @huaiyumi @mugity @dustine32
This has been reported in #3304 (comment)
In PTN002521528, FBgn0046685
I think the non-PAINT IKR is being ignored? We had requested that this gets fixed; has this happened ?
@huaiyumi this may be a good discussion topic for the next PAINT call.
Thanks, Pascale
The text was updated successfully, but these errors were encountered: