-
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
Pathway: oxidative phosphorylation (GO:0006119) #1
Comments
If we agree this is the way to model this process, the fly pathway should be identical, except ndi1 will be substituted by complex I |
Yikes - think if we are having to add components by has_part we could do with a bulk upload method....For complex I I have 44 members! |
Building the Fly version - not connected anything or filled in all the gaps yet: http://noctua.geneontology.org/workbench/noctua-visual-pathway-editor/?model_id=gomodel%3A67086be200000314 |
Added some connections - think will have to add H+ input to complex V and add Cytochrome c and electron transferring flavoproteins somewhere in the mix |
Adding this note: CHEBI has electron entry....CHEBI:10545 |
That's why this ticket should be a priority, please add your voice! |
If you can add these parts I will copy them. I will try to rationalize the assembly factors (I'll open a separate ticket) |
@tim18 ignore- it has binding sites! |
|
Pathway: oxidative phosphorylation (GO:0006119)
Complete gene set https://www.pombase.org/term/GO:0006119
The model is missing the
proton-transporting ATP synthase complex (GO:0045259)/
proton motive force-driven mitochondrial ATP synthesis (GO:0042776) sub-part
because I don't have a COmplex Portal ID for proton-transporting ATP synthase complex (GO:0045259)
https://www.pombase.org/term/GO:0045259
(I could add it with the complex sub-parts)
See geneontology/go-ontology#29067
Model Link: http://noctua.geneontology.org/workbench/noctua-visual-pathway-editor/?model_id=gomodel%3A663d668500000596
Current Model:
GOCAM viz
GOCAM viz complexes uncollapsed
The text was updated successfully, but these errors were encountered: