-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 in conversion of bmp related to regulation rule #49
Comments
should be positively regulates |
Looks like part of the issue comes up because BMP:BMPR is listed as both an input to 'Type II receptor phosphorylates type I receptor' and its catalyst. |
Other part is that splitting up the active unit on the complex confused the rule. |
Fixed. but note:
|
We are going to have to think about this double-edge. It seems to me that we also need more rules to infer direct positive regulation. It seems strange that this is the only one in the pathway. |
The biology we want to capture is complicated. First, a physical entity does something that activates it. e.g. a receptor binds a ligand. Then that activated entity carries out a function that results in a chemical change to itself, e.g. the activated receptor - ligand complex catalyzes its own phosphorylation. And typically the physical entities in these events are complexes and different components of the complex have different functions, e.g., ligand-binding and kinase-activity. But indeed the ligand-receptor complex both enables the kinase function and is the input for the kinase reaction, and that double role is a key feature of the biological process. If it helps, it is probably OK to assert that the receptor protein is the enabler and the kinase - the ligand molecule doesn't have a direct role in either. Per the BMP discussion, I guess the ligand-binding step would be modeled in GO-CAM as positive regulation of the phosphorylation (kinase) step. |
From 2019-03-01 discussion at NYU: |
http://noctua-dev.berkeleybop.org/editor/graph/gomodel:1847456024
The text was updated successfully, but these errors were encountered: