You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using MatlabStan for cognitive modeling right now. It's very helpful for me. Thanks so much for developing this amazing toolbox!
The problem of getting stan version
However, when I first tested it by using the 8-school example, the following error messages pop out,
Having a problem getting stan version.
This is likely a problem with Java running out of file descriptors
Trying again. (6 times)
Giving up.
You can try setting the Stan version explicitly using the stan_version attribute.
i.e. StanModel.stan_version = [2 15 0]
Error using cellfun
Non-scalar in Uniform output, at index 1, output 1.
Set 'UniformOutput' to false.
Error in StanModel/get_stan_version_ (line 932)
ver = cellfun(@str2num,regexp(str{3},'\.','split'));
Error in StanModel/get_stan_version (line 897)
ver = self.get_stan_version_();
Error in StanModel (line 197)
self.stan_version = self.get_stan_version();
It seems that some other users came across this problem as well (e.g. #17).
I'm using Cmdstan 2.22.0, Matlab 2016a & Windows 10.
I looked into the script (StanModel.m) and found that the string that the command (Line 923 in StanModel.m) obtained is actually,
stanc3 b5b5a3ca (Win32)
which might not stand for the version of Stan.
I think that might originate from the update of CmdStan. After 2.22.0, Stan was using stanc3 to transcompile Stan to C++. This compiler was actually named as stanc.exe and the old stanc.exe was then named as stanc2.exe instead. Hence, my problem could be simply solved by adapting the original code (line 923 in StanModel.m)
Nonetheless, users might still want to make sure that their MatlabProcessManager & CmdStan work smoothly beforehand.
The problem of using make in Windows systems
Besides, there might be another part in StanModel.m that needs adaptation for Windows users.
Given that Windows users should use mingw32-make instead of make in the command line, line 990, 994 & 996
There might be some other similar cases in the scripts that needs to be adapted for Windows users.
The 8-school example could run smoothly after these two adaptations in my case. Hopefully my experience could help other users that came across these problems.
Best,
Ma, Tianye
The text was updated successfully, but these errors were encountered:
Hi Brian,
I'm using MatlabStan for cognitive modeling right now. It's very helpful for me. Thanks so much for developing this amazing toolbox!
The problem of getting stan version
However, when I first tested it by using the 8-school example, the following error messages pop out,
It seems that some other users came across this problem as well (e.g. #17).
I'm using Cmdstan 2.22.0, Matlab 2016a & Windows 10.
I looked into the script (StanModel.m) and found that the string that the command (Line 923 in StanModel.m) obtained is actually,
which might not stand for the version of Stan.
I think that might originate from the update of CmdStan. After 2.22.0, Stan was using stanc3 to transcompile Stan to C++. This compiler was actually named as stanc.exe and the old stanc.exe was then named as stanc2.exe instead. Hence, my problem could be simply solved by adapting the original code (line 923 in StanModel.m)
as
Nonetheless, users might still want to make sure that their MatlabProcessManager & CmdStan work smoothly beforehand.
The problem of using make in Windows systems
Besides, there might be another part in StanModel.m that needs adaptation for Windows users.
Given that Windows users should use mingw32-make instead of make in the command line, line 990, 994 & 996
should be respectively adapted as
There might be some other similar cases in the scripts that needs to be adapted for Windows users.
The 8-school example could run smoothly after these two adaptations in my case. Hopefully my experience could help other users that came across these problems.
Best,
Ma, Tianye
The text was updated successfully, but these errors were encountered: