You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we discussed in #820, if there is no problem with recently updated content, two bug in current metabolic tasks:
Essential tasks failed under default solver(GLPK), but not with gurobi;
Failed tasks could not get any feedback.
Proposed changes:
Modify the line 38 in the testMetabolicTasks function as below
setRavenSolver('gurobi')
% change the third parameter to `true` to printOutput.
verificationTaskReport=checkTasks(model,[],true,true,false,verificationTasks);
The text was updated successfully, but these errors were encountered:
Regarding the solver in #820 is suggested that RAVEN should automatically swap solvers. This would not be preferred behaviour of native RAVEN functions, to swap mid-function to a different solver that might not be installed on the user's computer. A better behaviour is indeed to set the preferred RAVEN solver before running testMetabolicTasks. However, that would make this task depend on gurobi, which again might not always be installed/functional.
Irrespective, this tasks shouldn't fail with glpk. I looked into the RAVEN code, and it seems like some glpk parameters are incorrectly set, which cause the FBA here to time out.
Current behavior:
As we discussed in #820, if there is no problem with recently updated content, two bug in current metabolic tasks:
GLPK
), but not withgurobi
;Proposed changes:
Modify the line 38 in the testMetabolicTasks function as below
The text was updated successfully, but these errors were encountered: