-
Notifications
You must be signed in to change notification settings - Fork 218
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
Fixing summary calls in simulating.ipynb #239
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those percentages still seem weird. Should fluxes of ~9 and ~6 not end up in perecentages of 9/15 (60%) and 6/15 (40%)? I think the percentages are calculated from the FBA solution and the values from the FVA (but both should be calculated based on the FVA solution).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly, the percentages are calculated from the FBA solution. This is probably another item to add to #240.
Its non-trivial to decide how percentages should be assigned in the FVA case. Mainly because the total flux through each node is no longer fixed, and the percentages will necessarily change. Even using the median values might not make sense, since the sum of the median inputs may not equal the sum of the median outputs.
Finding errors in percentages would probably also be too hard, although that would be a cool feature.
Perhaps they should just not be printed to avoid confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point here with the median input/output problem. Also the median solutions might be confusing. Statistically speaking they are not necessarily correct since the fluxes are continuous probability distributions on a bounded domain and the formula used here assumes complete symmetry which probably does not hold. To get "real" population estimates for the medians one would have to sample from the flux cone with the fixed objective. In papers I have only seen the ranges reported (at least if they do not use sampling) since FVA gives no information about the location of the mean or median of the flux distribution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, I used half-spans +/- range/2 because its a familiar format. Probably better to make summary just have "MAX" and "MIN" columns when called with FVA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could also do center of min, max
On Mar 16, 2016 12:24, "Peter St. John" [email protected] wrote:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's actually whats currently done:
Fluxes then get printed according to
median
±half_span
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pstjohn yes, completely agree. Sorry for spamming comments here. Maybe we should open a gitter to discuss stuff like this...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries about all the comments. It's all relevant to the discussion of
this bug.
On Mar 16, 2016 1:15 PM, "Christian Diener" [email protected]
wrote:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok :) I would vote for the min - max format since any center value could be interpreted as the mean/median/most likely flux, all of which are false. Also it could give the impression that taking the solution where each flux takes its center value yields the reported biomass objective, which is also not true...
Also,since we are discussing the summaries, wouldn't it be good to allow calculation of the normal summary with pFBA since the individual FBA fluxes are somewhat arbitrary (pFBA as well but much less).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So right now
summary
methods don't trigger an FBA solution, pFBA or otherwise. You can certainly get pFBA solutions in the summary methods, as long as the model is optimized prior to calling the summaries. This is partly by design, as they are supposed to be quick ways of examining a model's current state.This is muddled somewhat by the addition of the FVA options, which do trigger optimizations.