Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error messaging at: Error evaluating initial BFGS point. #3327

Open
jachymb opened this issue Jan 17, 2025 · 3 comments
Open

Improve error messaging at: Error evaluating initial BFGS point. #3327

jachymb opened this issue Jan 17, 2025 · 3 comments

Comments

@jachymb
Copy link

jachymb commented Jan 17, 2025

This error doesn't really give any insight to the user as of what the actual problem with the init value is. Perhaps there is a nan or infinity in the loglikelihood? Maybe there's a problem with computing the gradients? Perhaps it's something else? Ideally it should give the user some insight how to fix the init value.

@bob-carpenter
Copy link
Member

Hi, @jachymb and thanks for submitting.

Is this an issue with optimization or Pathfinder or both? Which interface is displaying this behavior?

Is the text of the exception not being printed to the console?

Would it be possible to supply a reproducible example in whatever interface you are using?

Thanks!

@jachymb
Copy link
Author

jachymb commented Feb 17, 2025

I didn't save all the necessary things when I encountered this, but I will post it here if I see it again.

Clearly, this is raised at

throw std::runtime_error("Error evaluating initial BFGS point.");
so I thought maybe simply more info could be added to the message that is available in the context. Is there is a perhaps detailed info about the type of error in the ret variable?

@bob-carpenter
Copy link
Member

so I thought maybe simply more info could be added to the message that is available in the context.

I'm not sure we're getting useful return codes there. We can certainly say more about why an error is being thrown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants