Skip to content
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

Dihydroorotate Dehydrogenase #609

Closed
3 of 4 tasks
Devlin-Moyer opened this issue Jun 6, 2023 · 6 comments
Closed
3 of 4 tasks

Dihydroorotate Dehydrogenase #609

Devlin-Moyer opened this issue Jun 6, 2023 · 6 comments
Labels

Comments

@Devlin-Moyer
Copy link
Collaborator

Devlin-Moyer commented Jun 6, 2023

DHODH (ENSG00000102967) catalyzes MAR04575: (S)-dihydroorotate [c] + ubiquinone [m] ⇔ orotate [c] + ubiquinol [m]

While DHODH is capable of oxidizing dihydroorotate to orotate and reducing ubiquinone to ubiquinol, it uses FMN (MAM01828c/e) as an intermediate electron carrier in between those two substrates (source). Most reactions that are catalyzed by similar enzymes that use FAD in the same way, speifically those catalyzed by some combination of ACADVL, ACADL, ACADM, ACADS, and ACADSB (that's over 100 reactions in total, so I'm not listing them out here) do not directly involve ubiquinone (MAM03103m), but instead oxidize/reduce FAD(H2) (MAM01802m/MAM01803m), which oxdizes/reduces ubiquinone/ubiquinol in MAR06911. To be consistent with the representation of the existing reactions catalyzed by FAD-dependent enzymes where the electrons eventually wind up reducing ubiquinone:

  • Change ID of MAM20022i to MAM20019i to be consistent with MAM20019r, since both metabolite objects are supposed to represent the same compound (FMNH2) addressed by Fix/fmn fmnh2 ids #712
  • Create new metabolite MAM20019c to represent cytosolic FMNH2
  • Replace MAM03103m (ubiquinone) with MAM01828c (FMN) and MAM03102m (ubiquinol) with MAM20019c (FMNH2) in MAR04575
  • Create a new reaction to represent redox of FMN(H2) and ubiquinone/ubiquinol catalyzed by DHODH: MAM20019c + MAM03103m <-> MAM01828c + MAM03102m, GPR: ENSG00000102967, references: PMID:34428349

Technically, the redox between FMN(H2) and ubiquinone/ubiquinol happens at the outer face of the inner mitochondrial membrane, but there isn't currently a mitochondrial FMN metabolite, and it seems like overkill to add mitochondrial versions of both FMN and FMNH2 as well as cytosol <-> mitochondria transport reactions for both.

There are some other FMN-dependent enzymes associated with reactions in Human1 that do not currently involve the FMN metabolite (e.g. PNPO, see Table 1 of this paper) that could probably have similar edits made to them, but I came across this issue when specifically looking into enzymes that use FAD to reduce ubiquinone, so I haven't looked into exactly what changes would need to be made to those reactions (yet).

@JonathanRob
Copy link
Collaborator

Seems like a reasonable suggestion, since as you say many FAD-binding enzymes are already represented this way in the model. My concerns are that by separating the reaction steps, it becomes a bit less clear what the overall reaction is because one needs to be aware of both steps. Also, if there are other reactions that can reduce/oxidize FMN, it opens the possibility to use those as the second step instead of coupling to ubiquinone/ubiquinol (I know there aren't any now because it's a new metabolite, but if some are added in the future).

For the new reaction step involving electron transfer between FMNH2 and ubiquinone, would the GPR of that reaction include all FMN-dependent enzymes?

@Devlin-Moyer
Copy link
Collaborator Author

Devlin-Moyer commented Jun 6, 2023

My concerns are that by separating the reaction steps, it becomes a bit less clear what the overall reaction is because one needs to be aware of both steps. Also, if there are other reactions that can reduce/oxidize FMN, it opens the possibility to use those as the second step instead of coupling to ubiquinone/ubiquinol (I know there aren't any now because it's a new metabolite, but if some are added in the future).

So while I agree that it does make the overall reaction less clear, that may actually (unfortunately) be a more accurate representation of reality, since no FMN-dependent flavoenzymes in humans bind their FMN covalently (a few of the FAD-dependent ones do, but the vast majority don't; source), and at least one human enzyme that had long been thought to depend on FAD and/or FMN bound to a different enzyme was shown to preferentially use free FAD and/or FMN to catalyze its redox reaction (source)

For the new reaction step involving electron transfer between FMNH2 and ubiquinone, would the GPR of that reaction include all FMN-dependent enzymes?

As far as I can tell, it would only contain DHODH, because that seems to be the only human FMN-dependent enzyme that is known to be capable of directly transferring electrons between its FMN and ubiquinone

@JonathanRob
Copy link
Collaborator

Sounds great, thanks for the detailed answers @Devlin-Moyer!

@Devlin-Moyer
Copy link
Collaborator Author

Devlin-Moyer commented Jun 8, 2023

I was just about to start working on this when I noticed that there are already two metabolites in Human-GEM called "FMNH2": MAM20019r and MAM20022i. While I'd still need to add cytosolic and mitochondrial FMNH2 metabolites for this issue, I get the impression that all compartment-specific versions of the "same" metabolite are supposed to have identical numeric bits of their IDs and only differ in their final characters that specify the compartments. Should I also change the ID of MAM20022i to MAM20019i for consistency with MAM20019r as part of the pull request for this issue (and then make the new FMNH2 metabolites for this issue be MAM20019c/m), or should I make that a separate issue?

(I verified that none of the proposed changes in #610, #617, #618, #620, #621, or #622 would address this specific pair of metabolites)
never mind; this was addressed in #712

@Devlin-Moyer
Copy link
Collaborator Author

Devlin-Moyer commented Jun 13, 2023

ope nevermind #626 and #627 both also mention MAM20019r and MAM20022i being duplicates; should I wait for those to be resolved before making a pull request to implement the proposed changes here?
never mind; this was addressed in #712

@Devlin-Moyer
Copy link
Collaborator Author

fixed in #713

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants