-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Odd interaction between ode_adams
and threading
#2975
Comments
Here's what gdb reports when chain 1 and 4 are stuck: Details
|
I'll try to reproduce when I have some free time. |
I'm on |
This was develop on both machines I was using, independent of seed. Both were running Linux however |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have noticed some odd behavior using
ode_adams
andSTAN_THREADS
. This does not recur when usingode_bdf
orode_rk45
.Example
Using a simple SIR model, courtesy of @charlesm93:
data:
inits
When compiled via cmdstan with STAN_THREADS=1, I then run with
It seems to vary a bit between runs, but when run repeatedly the most common outcome is that two chains run/print their progress, until completion, and then the process hangs. I have recreated this on two separate linux systems.
strace
reports a lot of using ofsched_yield
fromtbb
, but otherwise there is nothing happening.gdb
seems to implicateset_zero_all_adjoints
in a backtrace, but not in any way I can track down.Expected Output
Expect all four chains to run simultaneously and the program to not hang.
Current Version:
v4.7.0
The text was updated successfully, but these errors were encountered: