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
What should I infer about my problem and/or its suitability for use with tron/trunk if I encounter solution status equal to :neg_pred?
The problem I am solving is unconstrained, and is definitely not globally convex (I am trying to minimize the negative log likelihood of a nested logit model). lbfgs does seem to "work" in the sense that if I give it a reasonable amount of time, it finds a reasonable fit (though I've yet to run it long enough to see if it converges). Is the failure mode I am encountering with tron and trunk telling me something about the structure of my problem? That I have perhaps a bug in my log-likelihood definition? Or something else?
When I solve a simpler non-convex problem using similar data ("vanilla" logit, but with scale parameters that vary across choice sets, this heterogeneity I believe makes the problem non-convex), both tron and trunk seem to work great. So I'm scratching my head about my nested logit setup...
Thanks in advance for any advice you might have.
The text was updated successfully, but these errors were encountered:
tcovert
changed the title
Negative predicted directions in tron/trunk
Negative predicted reduction in tron/trunk
Mar 28, 2024
Hi JSO team,
What should I infer about my problem and/or its suitability for use with
tron
/trunk
if I encounter solution status equal to:neg_pred
?The problem I am solving is unconstrained, and is definitely not globally convex (I am trying to minimize the negative log likelihood of a nested logit model).
lbfgs
does seem to "work" in the sense that if I give it a reasonable amount of time, it finds a reasonable fit (though I've yet to run it long enough to see if it converges). Is the failure mode I am encountering withtron
andtrunk
telling me something about the structure of my problem? That I have perhaps a bug in my log-likelihood definition? Or something else?When I solve a simpler non-convex problem using similar data ("vanilla" logit, but with scale parameters that vary across choice sets, this heterogeneity I believe makes the problem non-convex), both
tron
andtrunk
seem to work great. So I'm scratching my head about my nested logit setup...Thanks in advance for any advice you might have.
The text was updated successfully, but these errors were encountered: