It is during function evaluation in the line search, the value is either infinite or NaN, which may be caused too large step size. In the code, the step is reduced to half.
Thanks. Zhan Zhang On Mar 13, 2015, at 2:41 PM, cjwang <c...@cjwang.us> wrote: > I am running LogisticRegressionWithLBFGS. I got these lines on my console: > > 2015-03-12 17:38:03,897 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to 0.5 > 2015-03-12 17:38:03,967 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to 0.25 > 2015-03-12 17:38:04,036 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to 0.125 > 2015-03-12 17:38:04,105 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to > 0.0625 > 2015-03-12 17:38:04,176 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to > 0.03125 > 2015-03-12 17:38:04,247 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to > 0.015625 > 2015-03-12 17:38:04,317 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to > 0.0078125 > 2015-03-12 17:38:04,461 ERROR breeze.optimize.StrongWolfeLineSearch | > Encountered bad values in function evaluation. Decreasing step size to > 0.005859375 > 2015-03-12 17:38:04,605 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:04,672 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:04,747 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:04,818 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:04,890 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:04,962 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:05,038 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:05,107 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:05,186 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:05,256 INFO breeze.optimize.StrongWolfeLineSearch | Line > search t: NaN fval: NaN rhs: NaN cdd: NaN > 2015-03-12 17:38:05,257 ERROR breeze.optimize.LBFGS | Failure! Resetting > history: breeze.optimize.FirstOrderException: Line search zoom failed > > > What causes them and how do I fix them? > > I checked my data and there seemed nothing out of the ordinary. The > resulting prediction model seemed acceptable to me. So, are these ERRORs > actually WARNINGs? Could we or should we tune the level of these messages > down one notch? > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/LogisticRegressionWithLBFGS-shows-ERRORs-tp22042.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@spark.apache.org > For additional commands, e-mail: user-h...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
