Open cortner opened 11 months ago
I also encountered this issue recently. Has it been resolved? Could it be a solution to change BLR to LSQR?
This definitely does need better error handling and a more helpful message. I can't do it today but will push something later this week.
The following error seems to occur quite frequently:
and it keeps going for a while. Maybe this could be caught with a nicer error message explaining what might have gone wrong and what to try next, e.g. adding better data or trying a different solver.
If the solver can be fixed to actually handle this case, even better.