-
Notifications
You must be signed in to change notification settings - Fork 47
GPR rules for specific fatty acid oxidation reactions MAR02121, MAR02122, MAR02123 #966
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
Comments
Yea I have come across a lot of similar issues with fatty acid oxidation reactions (see most of the issues between #736 and #801), and while I think it would be good to systematically go through all of the peroxisomal fatty oxidation reactions to fix issues like this, most of the issues I've already opened about other issues with fatty acid oxidation reactions haven't been resolved yet (because nobody else has had time to double check that all of the fixes I propose are correct), so I've been hesitant to open any more issues about things like this |
in the case of these specific reactions, I suspect that the appropriate fix would be similar to the changes made to |
While it is true that |
Uh oh!
There was an error while loading. Please reload this page.
Hey, this is a bit of a question/suggestion but I was looking at GPR rules for these reactions (MAR02121, MAR02122, MAR02123) and the genes listed for these reactions are CPT2, CPT1B but these are mitochondrial and as far as the literature suggests, are not expressed in the peroxisome. Actually further to this, peroxisomes don't appear to import carnitine species but instead export fatty acid-carnitine species for further oxidation in the mitochondria. They import activated fatty acids, which appear to have relevant reactions in the peroxisome already in Human1. I think simply deleting these reactions are a bit problematic but I'd like to hear what the Human1 curators think about this and whether these reactions are supported in the literature.
The text was updated successfully, but these errors were encountered: