-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
de/serialization issues #2179
Comments
This issue was moved to stan-dev/rstan#373 |
I will try to fix it in stan rather than rstan so all are happy. |
OK, if you want to fix it there, it should be a Stan issue.
But it should be opened as a Stan issue rather than as a comment
about RStan to CmdStan translation.
But why not just go back to having RStan generate the same output as before?
- Bob
… On Dec 21, 2016, at 11:08 PM, maverickg ***@***.***> wrote:
I will try to fix it in stan rather than rstan so all are happy.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
see here for why rstan changed this function: stan-dev/rstan#366 The issue is kind of with stan/io/dump.hpp now. In the case of zero length array/matrix/vector, dump in stan depends on a technically wrong behavior of
|
Got it. Thanks for re-opening. R never ceases to amaze me:
|
Summary:
When using rstan 2.13 stan_rdump to serialize arrays with zero size , then these cannot be read with cmdstan 2.13
Description:
Serializing with stan_rdump and starting a cmdstan run does not work any more if the arrays has size zero. This used to work with rstan 2.12 and cmdstand 2.12.
This releated to the issue rstan#371 .
Reproducible Steps:
serialized data with rstan 2.13 which does not work with cmdstan 2.13:
this data works with cmdstan 2.13 and was generated with rstan 2.12:
Here is a dummy Stan program:
Current Output:
cmdstan fails to run
Expected Output:
Error from cmdstan:
cmdstan Stan Version:
2.13.1
Operating System:
RHEL 6.7
The text was updated successfully, but these errors were encountered: