Daniel Lee
Daniel Lee
Thanks for looking into that. I’m away from a computer for the next few days. When I’m back, I can see if there are different compiler options we use for...
I'll second what @rok-cesnovar said. We might be able to split it out to a secondary library, but the integration pains will be no joke. I can already see some...
I just verified that this still happens with `develop` right now. I'll try with the code from PR #2806 to see if that helps.
I valided that #2806 fixes this issue.
This PR fixes #2804. @rok-cesnovar wanted to be assigned to it.
Can you provide a minimal example? An easy way to do it is to just put it on a branch. (The breadcrumbs you left aren't enough.) Or just isolate it...
I think action is on me to come up with possible exceptions to throw.
I would suggest using `std::system_error` (introduced in C++11). http://www.cplusplus.com/reference/system_error/system_error/ It takes a string and an error code. With pull request #2307, this should pass through and stop the samplers.
Sorry about the late reply. There's actually an `init_writer()` that should have the initial values written out to it. https://github.com/stan-dev/stan/blob/develop/src/stan/services/sample/hmc_nuts_diag_e_adapt.hpp#L51 https://github.com/stan-dev/stan/blob/develop/src/stan/services/sample/hmc_nuts_diag_e_adapt.hpp#L65 It's on the unconstrained scale. There are convenience functions...
That's right. It just needs to be stored somewhere. As a prototype, if you replaced that writer with one that writes out to `std::cout`, you should see the initial values....