-
Notifications
You must be signed in to change notification settings - Fork 0
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
Confirm correct directionality of Physical Entity regulates Function assertions #18
Comments
To get this converted to GO-CAM, you can try modifying your rule to link the activity that creates the physical entity, rather than the entity itself. So in your example, if physical_entity is an output of reaction_A, then reaction_A directly_negatively_regulates reaction. |
The 'physical entity' involved in regulation of 'function' relations are correct but the UI reverses them in the folded view - see geneontology/noctua#582 These reflect physical controllers from, e.g. Reactome, that are not catalysts but exert some other form of regulatory control. Leaving this issue open to explore the modification above to produce function regulates function assertions. |
Forgot, this rule is actually already in place. See rule slides 14 and 15 in https://docs.google.com/presentation/d/1_UAQN09WPCA5win5mbMs1ORMALNwiRwMBgZDPuyJEW8/edit?slide=id.g355425beec_0_3#slide=id.g360932a148_0_36 You can see in the reaction linked above that "Beta-catenin is released from the destruction complex" is positively regulated by 'Phosphorylation of LRP5/6 cytoplasmic domain by CSNKI'� |
This looks like a legacy problem that Reactome has now fixed. It used to be legal to annotate regulation of an entity. We decided that wasn't useful, removed all such annotations, and changed the curation process so no more can be made. However, depending when the BioPax used here was generated, it might have included some old regulation_of_entity instances. |
See e.g. 'Beta-catenin is released from the destruction complex' in http://noctua-dev.berkeleybop.org/editor/graph/gomodel:-80976963
The text was updated successfully, but these errors were encountered: