-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
expose_stan_functions causes error: "$ operator is invalid for atomic vectors" #954
Comments
PS. This page (https://cran.r-project.org/web/checks/check_results_rstanarm.html) which appears to report build info has the same error (https://www.r-project.org/nosvn/R.check/r-devel-windows-x86_64-gcc10-UCRT/rstanarm-00check.html). I guess that page gets updated so the error might go away or something different reported; the one I'm looking at has the timestamp 2021-07-23 01:49:38 CEST. |
can confirm, I am also getting this issue.
|
I'm working with experimental version 2.26 of RStan on Windows and I'm getting an error, "$ operator is invalid for atomic vectors", from expose_stan_functions.
I researched this a bit and did not find anything the same. Issue #899 mentions expose_stan_functions in passing but that appeared to be about other errors.
I get the error from an existing .stan file for which expose_stan_functions does not cause an error with RStan 2.26 on macOS. Instead of including the .stan file I'm working with, here is a shorter example which I nicked from another discussion. See: https://discourse.mc-stan.org/t/mixture-models/17721/9
I put that into a file name example.stan and then I get, in my R session:
packageVersion ("RStan")
reports2.26.2
.R.version.string
reports"R version 4.1.0 (2021-05-18)"
.Operating system is MS Windows 10.
I installed RStan following these instructions. (I was trying the officially released version 2.21, however, it lacks the
%/%
operator which I want to use.) See: https://discourse.mc-stan.org/t/problems-installing-rstan-2-21-2-with-rtools-4/22492/5The text was updated successfully, but these errors were encountered: