-
Notifications
You must be signed in to change notification settings - Fork 9
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
optlang error in optimization #21
Comments
@arabidopsis @Midnighter sorry for pushing this again but I really can't get it run. I tried different python versions (2.7,3.6,3.7), solvers (gurobi,cplex) and systems (debian, centos) and I'm stuck... |
I'm a bit hesitant to step in here because we're not officially supporting this package yet. There's a lot of work to do, we haven't released anything yet, so it's a mixed bag of really old code and some newer code that hasn't been glued together. |
hi @Midnighter thanks for your answer! But are there plans to continue this project? Would be really great to have some python code for creating tissue-specific models! |
Yes, we do want to pick up work on this again. For starters we will focus on diversifying data types, i.e., better support for fluxomics, metabolomics. Even though tissue-specific models are not our speciality, we do want to make transcriptomics and proteomics more useful so there will naturally be some overlap in methods. Timeline-wise you might see something appearing as soon as July. |
Btw, you should also look around at https://opencobra.github.io/cobrapy/packages/ you might find a fit for your use-case there. |
I'm getting an error when trying to compute a condition-specific model by
driven.imat
.It seems to be an issue with optlang:
A small example with random expression data to reproduce the problem:
Although this error occurs with gurobi and cplex set as solver, it works fine with glpk (in reasonable time only for smaller models).
I tried python 2 and 3. The optlang package is the latest version (1.4.4)
Complete error log
The text was updated successfully, but these errors were encountered: