stan::common::do_bfgs_optimize allows interruption

[maverickg]

I am not sure if there is alway an issue for this one. Now the loop in the API, rstan cannot check if there is an interruption from the user (such as a Ctrl+C).

[bob-carpenter]

Glad you're keeping an eye on this, as it's
an important point.

The only solution I see if the interrupts are
interface or platform specific is to provide callbacks
inside our algorithms for interrupters. I'm not
exactly sure how that would work. But I'd like to make
it a reasonably high priority because it's incredibly
frustrating to have to hard kill a process because it's
running something uninterruptible.

• Bob

On Jul 12, 2014, at 9:34 PM, maverickg notifications@github.com wrote:

I am not sure if there is alway an issue for this one. Now the loop in the API, rstan cannot check if there is an interruption from the user (such as a Ctrl+C).

—
Reply to this email directly or view it on GitHub.

[syclik]

Yes, thanks Jiqiang for spotting this!

Bob, I have a callback for the sampling, so the mechanism is already built.
I had to do it as part of the initial refactor.

I think we're close to sitting down and designing something that will be
sustainable moving forward.

On Jul 13, 2014 12:20 AM, "Bob Carpenter" notifications@github.com wrote:

Glad you're keeping an eye on this, as it's
an important point.

The only solution I see if the interrupts are
interface or platform specific is to provide callbacks
inside our algorithms for interrupters. I'm not
exactly sure how that would work. But I'd like to make
it a reasonably high priority because it's incredibly
frustrating to have to hard kill a process because it's
running something uninterruptible.

• Bob

On Jul 12, 2014, at 9:34 PM, maverickg notifications@github.com wrote:

I am not sure if there is alway an issue for this one. Now the loop in
the API, rstan cannot check if there is an interruption from the user (such
as a Ctrl+C).

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#768 (comment).