Not sure if this is a bug or intended behaviour, but a heads up to all Windows cmdstanr users who suddenly get “CmdStan path has not been set yet.” error, even when they succesfully used cmdstanr previously.
Between cmdstanr 0.7.1 and 0.8, the location where a Cmdstan installation is expected by default has changed from something like C:/Users/<YOUR-USERNAME>/Documents/.cmdstan to C:/Users/<YOUR-USERNAME>/.cmdstan (i.e. the Documents part is missing).
Moving the .cmdstan folder lets you use cmdstanr again as expected, without reinstalling.
A suggestion for @andrjohns - maybe CmdStanR should - at least for a while - search in both the old and new default locations?
I didn’t realize cmdstanr was using a different default location than cmdstanpy (we are just in the user folder, not Documents/). It doesn’t look like that is documented, either.
I think some windows configs essentially symlink the documents folder into OneDrive, so I would be sure that changing it back doesn’t just re-break those systems
Seems to fix things for cmdstanr at least! Was legitimately questioning my sanity when calling make in C:/cmdstan failed with errors about the onedrive folder though