-
Notifications
You must be signed in to change notification settings - Fork 43
generate_steady_states
fails when you edit a model's optimal percentage twice
#83
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
Comments
Hi, Using optimal percentage = 10/20 %: model = dingo.MetabolicNetwork.from_json("ext_data/e_coli_core.json")
model.set_opt_percentage(10)
sampler = dingo.PolytopeSampler(model)
sampler.generate_steady_states()
model.set_opt_percentage(20)
sampler = dingo.PolytopeSampler(model)
sampler.generate_steady_states() Output 1
As pointed out by @rkstu, a fix to the code runs the code but causes a Segmentation fault at the end. On my end, even on not making any changes results in the same. Using optimal percentage = 90/20 %: Output 2
The most likely reason for this error would be that using 90% as the optimal percentage and then generate_steady_states() followed by any percentage and generate_steady_states() takes up most of the available RAM (~85-95%). Using optimal percentage = 20/10/5 % (i.e. running generate_steady_states() 3 times) results in the following error in the end
Thirdly, I ran the method generate_steady_states() twice without changing the optimal percentage. The first time, it ran only 3-4 phases. The second time, it ran >70 phases. Why does it change so much? |
Uh oh!
There was an error while loading. Please reload this page.
would return:
It seems the error is related to the https://github.com/GeomScale/dingo/blob/aaae4ae63f432da45eb0f4363a92767ba537a074/dingo/gurobi_based_implementations.py#L109
and the
status == GRB.OPTIMAL
that is not the case in the second edit.where the status is
INF_OR_UNBD
for some reason (https://www.gurobi.com/documentation/current/refman/optimization_status_codes.html)The text was updated successfully, but these errors were encountered: