-
Notifications
You must be signed in to change notification settings - Fork 5
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
usability questions #61
Comments
Ah, thanks for finding these issues! I will look into C this week and get back to you. |
Actually, I have put time aside for this at the end of next week |
Hi, The solver-in-docker problem is not a nice one though; I'd love to be able to somehow get gurobi licenses in there :] |
How about mounting the license file at the expected location? |
yeah that should work, I really just need to find a moment try it (meaning I need to get the license etc. :D ) |
@mihai-sysbio, I think most of your issues actually came from the optimizer you were using, Tulip.jl. The latest release of FBCModelTests, v0.2.5, changes the way results are collected, and which tests are run. It should be more robust. We also changed the default solver to GLPK. Next week we will release v.0.3.0, which adds a few more SBO tests and makes some cosmetic changes. I tested your model, using Gurobi as the solver, and the results are shown below. Note, we do not yet handle split objective functions (see issue #27), so your model will fail all the tests that rely on identifying the objective function. Finally, we only use SBO annotations to identify reaction types, which might be another source of problems. Let me know if you have any questions! Edit: we will soon release v0.3.0, which improves some details of the tests, I have used this branch (#76) to generate the results below. |
Is there any news regarding the upcoming release? |
Hi, |
(done) |
Thanks for putting together these test suites, very nice work!
I have some usability questions (possibly issues):
A) Minor: it's unclear what model formats are accepted, since it's just a string of the model file. The example points to json, which is not what I would have expected.
B) Minor: it's unclear to me why there is the need to have 3 different docker images instead of one. As a user, I'd prefer to have one image that includes all everything (including dependencies), and pass different commands to it with
docker run
.C) Major: I can't seem to run the Memote-style test on yeast-GEM:
since it ends up in an infinite loop that prints:
The text was updated successfully, but these errors were encountered: