Skip to content
Discussion options

You must be logged in to vote

Hi Alex,

Yeah good point, this is planned but has not been added. The reason initially was that (1) it's a lot of fluxes and take quite long to extract and store, and (2) internal fluxes are not unique, so there may be many possible flux distributions yielding a specific set of growth rates and exchanges.

But the idea is to add those as an attribute to GrowthResults (internal_fluxes or similar). The single model API for this is already proposed but the workflow API needs to be overhauled because I don't want to add yet another arg to grow().

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@AlexHoratio
Comment options

Answer selected by AlexHoratio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants