-
Notifications
You must be signed in to change notification settings - Fork 11
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
N/A from MIP but value from MRO. #22
Comments
Hello, This means that something in the simulation failed. If there were no possible interactions the value would be 0 and not NA. It is hard to debug this without further details. Does it happen for some communities? All communities? Are you specifying a growth medium ? |
I am giving it communities of co-occuring pairs. It gives n/a for about half my communities. I do not specify a growth medium. This is my command: smetana *.xml -c size_2_part_1.tsv -g -v --flavor cobra --molweight -o out |
I can send a 2 model community if that helps. |
Hi, I am experiencing the same issue. I am running communities of 2 species with specified growth media and --solver gurobi. MIP comes out as n/a for 63/66 communities. In one case it reutrns a MIP value but not MRO. It fails to find a valid solution for MRO for about half of the communities. Everything seems to work fine in --detailed mode. I have also tried running with --molweight. It then returns fewer MIP and MRO values and only a fraction of the interactions in --detailed. |
Sorry for the late reply. Can you both send me some examples to debug ? |
I have tried running the communities in "pairwise.tsv" with the "M9glu" media specified in M9media.tsv. Files are here: |
Thanks, Daniel. Here is a Google Drive to 2 models I used as a community that can't calculate the MIP. https://drive.google.com/drive/folders/1-hhxj8YojrdHeoBTXbIL90YOyxrSFfoh?usp=sharing |
@zburcham I found the problem. Please use By the way, if you ever update CarveMe to the latest version, please use |
@liseklaks your case is more complicated, your models use mixed ids (from BiGG and KEGG) and have a few strange features... For example in This really breaks our code when merging species into a community and creating mappings between extracellular compartments and exchange reactions. To be honest, I don't really see a way to solve this... It is not possible to support all models with unexpected structures and maintain a biologically meaningful outcome... |
Okay, I see. Thank you for looking into it and finding where the issue was! |
Thank you @cdanielmachado , that seemed to fix the problem with MIP calculation. I am having an issue with a few models now working with MRO calculation now but that is only a few. |
Hi guys, I have a similar problem, but the solutions mention above do not seem to fix it. I run SMETANA on a single community with 7 species and I get N/A MIP. Any suggestions on why might this happen and how to fix it? |
P.S. I also tried adding "--flavor cobra/ucsd", but I get: > .........................................
iulia |
Hi again, I really need your opinion on this. My actual community is bigger than what I previously tried (but not more than 25 MAG's) and the MIP is still N/A for all the communities I have. I really need this to work (or at least understand the problem) in order to move forward with my analysis. I will be very grateful for your help. |
Hi Iulia, Are you specifying a growth medium when you calculate MIP ? If you specify a growth medium it is only possible to calculate MIP if every species can grow alone in that medium, because we compare growth alone vs growth in community to estimate the interaction potential. |
Hi Daniel, But the growth media specification vs. MIP calculation explanation is welcomed. Thank you. |
hi @cdanielmachado |
Hello,
I am running smetana global on models with '--flavor cobra' and '--molweight'. I am getting values for MRO but my MIP values are only coming back as N/A. Is this normal and interpreted that the solver could not determine if any cooperative interactions take place?
Thank you
The text was updated successfully, but these errors were encountered: