On Tue, 20 Oct 2015, Sven Schreiber wrote: > don't know whether it's a new thing, but with gretlcli (version > 1.10.2) I get a huge amount of messages like these: > > gretl_cholesky_decomp_solve: rcond = 2.88435e-08 (info = 0) > > This output doesn't go into the specified output file (the "out" in > "gretlcli -b prog.inp > out"), but ends up in what the server > automatically captures in a kind of log file for the job. First I > thought it was a minor nuisance, but now some of these files reached > >150MB. > > I remember there was something similar a couple of months ago, but > that was a different gretl message, and I think you then turned it off > or diverted it or something. This message is going to stderr. It's not new. In some contexts if gretl_cholesky_decomp_solve fails there's a fallback, in others not. If there's a fallback then printing this message is probably redundant; if not, it might be useful for tracing failure. But maybe it could be scrapped altogther. If you're getting a ton of these messages it seems you must be working with a lot of ill-conditioned data!