-
Notifications
You must be signed in to change notification settings - Fork 3
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
Export sucrose from Synechococcus #20
Comments
Make sure that cyano excretes sucrose under co2 + light inputs |
By setting the The objective values are:
Reactions that
Reactions that
|
hey. I have a real sucrose export data from batch experiment if want to validate or constrain the model |
You have exported metabolite data for axenic Rhodosporidum toruloides growing on sucrose? If so, that would be awesome, as we currently only have exported metabolite data for Rhodo in a co-culture |
It is content (g/L) of sucrose in axenic S.elongatus when it is growing alone and content in S.elongatus-Rhodo co-culture when they grow together mixed, or when they are separated by membranes |
Got it. At what point in time after inoculation was the measurement taken for each condition (axenic, co-culture mixed, co-culture separated)? Do we also have measurements of biomass (or a proxy such as OD) taken at the same time as sucrose was measured? |
@mcnaughtonadm getting Rhodo to grow on sucrose solves half the problem. The other half is adding sucrose export to cyano, and ensuring it secretes it. |
As a point of reference towards this, here is the base optimization through CobraPy of the cyano model. We have an objective value of: 0.0539 with the following Uptake
Secretion
The current state of
|
Current Pull Request waiting for Review and Approval by either @JamesPino or @djinnome introducing Jupyter Notebook showing how to generate a Synechococcus model capable of exporting sucrose. Moving this task to done, but not closing the issue until PR goes through. |
Issue solved with #33 , closing issue. |
No description provided.
The text was updated successfully, but these errors were encountered: