-
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
Strange differences between text files in bin and XML file #3
Comments
Good spot! There is indeed some redundancy here. The reactionsToAdd file is read first, and the reaction (obviously) added to the model. Later, reactionsToUpdate is read, and the reactions updated. In an ideal world, the reactionsToAdd would have specified this reaction correctly, meaning that the update is not necessary. This is (probably) an oversight based on the confusion of curating a model with thousands of reactions. The final model contains 3 h_x reactants and 4 h_x products due to the auto-balancing method, which attempts to correct for missing water, protons and incorrect stoichiometry by applying linear programming to the task of balancing (see http://biecoll.ub.uni-bielefeld.de/volltexte/2011/5202/pdf/jib_186.pdf). The final reaction is therefore correctly mass / charge balanced. However, I appreciate the confusion here, as the initial reaction is (as far as I can see) mass and charge balanced: R_FAOXC220200x R_FAOXC220200x M_h2o_x + M_coa_x + M_o2_x + M_nad_x + M_c220coa_x --> M_h_x + M_h2o2_x + M_nadh_x + M_accoa_x + M_arachcoa_x Essentially, the reactionsToUpdate update (and subsequent auto-balancing) is probably superfluous. I'm sure that there will be other anomalies like this. However, the key take-home is that all reactions (except biomass production) are mass and charge balanced - hence the sensible ATP flux predictions. |
Well, the original metaoblite c220coa is replaced with M_docoscoa_x, which
is supposed to be identical.
Maybe the script got confused at some point during the replacement process?
It is also a bit weird, since I think the reaction FAOXC22C20x is already
present in RECON 2.04, see https://vmh.uni.lu/#reaction/FAOXC22C20x (and
reaction index 7054 if you're looking at the model file).
I'm just trying to figure out how common this kind of occurrence is, and if
it needs to be fixed.
Cheers,
Uri David
…On Wed, Mar 8, 2017 at 4:02 AM, Neil Swainston ***@***.***> wrote:
Good spot! There is indeed some redundancy here.
The reactionsToAdd file is read first, and the reaction (obviously) added
to the model. Later, reactionsToUpdate is read, and the reactions updated.
In an ideal world, the reactionsToAdd would have specified this reaction
correctly, meaning that the update is not necessary. This is (probably) an
oversight based on the confusion of curating a model with thousands of
reactions.
The final model contains 3 h_x reactants and 4 h_x products due to the
auto-balancing method, which attempts to correct for missing water, protons
and incorrect stoichiometry by applying linear programming to the task of
balancing (see http://biecoll.ub.uni-bielefeld.de/volltexte/2011/
5202/pdf/jib_186.pdf). The final reaction is therefore correctly mass /
charge balanced.
However, I appreciate the confusion here, as the initial reaction is (as
far as I can see) mass and charge balanced:
R_FAOXC220200x R_FAOXC220200x M_h2o_x + M_coa_x + M_o2_x + M_nad_x +
M_c220coa_x --> M_h_x + M_h2o2_x + M_nadh_x + M_accoa_x + M_arachcoa_x
Essentially, the reactionsToUpdate update (and subsequent auto-balancing)
is probably superfluous.
I'm sure that there will be other anomalies like this. However, the key
take-home is that *all* reactions (except biomass production) are mass
and charge balanced - hence the sensible ATP flux predictions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKGMZoMfftDlV63MwdGvQdsr_j3Opoydks5rjm6cgaJpZM4MUrp_>
.
--
Uri David Akavia, Ph.D.
Assistant Professor, Biochemistry Department
[email protected]
McIntyre Medical Sciences Building
3655 Promenade Sir William Osler, Room 805B
Montreal, Quebec H3G 1Y6
Office tel: 514-398-8526
fax: 514-398-7384
|
There is at least one reaction that has strange differences between the text files in bin and the XML file MODEL1603150001.xml. Specifically, the reaction R_FAOXC220200x (there might be others, I'm searching for them).
If we look at this reaction in the TXT files, it appears three times (once for genes, irrelevant for now, twice with different formulas)
mcisb-recon-master/bin/reactionsToAdd.txt:R_FAOXC220200x R_FAOXC220200x M_h2o_x + M_coa_x + M_o2_x + M_nad_x + M_c220coa_x --> M_h_x + M_h2o2_x + M_nadh_x + M_accoa_x + M_arachcoa_x
mcisb-recon-master/bin/reactionsToUpdate.txt:R_FAOXC220200x M_h2o_x + M_coa_x + M_o2_x + M_nad_x + M_c220coa_x + 3.0 M_h_x --> M_h2o2_x + M_nadh_x + M_accoa_x + M_arachcoa_x
However, in the XML file, it has a different formula, where it has 3 H+ as reactants and 4 H+ as products (relevant XML pasted below).
M_coa_x + M_o2_x + M_nad_x + M_docoscoa_x + 3* M_h_x --> 4*M_h_x + M_h2o2_x + M_nadh_x + M_accoa_x + M_arachcoa_x.
What is going on here?
The text was updated successfully, but these errors were encountered: