Closed jbedo closed 2 years ago
Hi @jbedo - sorry you're having problems with the solver. The error message above (and the log you've attached) are a result of running the solve
command. What do you see when you run hatchet check-solver
as suggested? The output you see there might be instructive.
EDIT:: Ok I see that this is the output of the actual hatchet check-solver
. Can you try to run hatchet check-solver
by first setting the environment variable HATCHET_COMPUTE_CN_SOLVER
to any other pyomo-supported solver? (Like cbc
, glpk
or even just gurobi
? (See docs). This should help us narrow down the problem I think.
Haven't tried setting HATCHET_COMPUTE_CN_SOLVER to gurobi, but CBC works fine with both check-solver and a real sample I've put through it.
I believe I've solved this: though hatchet was compiled and linked against the gurobi libraries, gurobipy was not available in the python environment. Adding gurobipy has allowed hatchet check
to succeed.
Hi, @jbedo could you please let me know how did you run with cbc solver? I am running HATCHet v1.1.2 using cbc. However, I seem to have a problem where it's taking > 72 hrs to run after reaching the process "Running diploid with 3 clones". Other than this, I don't see any errors in the log.
I didn't do anything special, CBC is pretty slow in this application. It really wasn't usable on our human WGS samples, gurobi is significantly faster.
I'm having issues getting
hatchet check-solver
to run, it seems to encounter a buffer overflow error:I don't think this is a gurobi licensing issue as it's a buffer overflow not the expected exception? Any suggestions on debugging?
Full log attached.
log.txt