-
Notifications
You must be signed in to change notification settings - Fork 37
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
Another "Error in seq.int(cutpoints[1] + 1, cutpoints[2] - 1) : 'from' must be a finite number" problem #28
Comments
I am having the exact same problem with the exact same version of Stata. |
Same. It worked for me once and then it's no longer working for me. Whenever I try to run a load a dataframe from stata like this: I get this: I even tried running: |
Same problem, is it because I am using StataBE? Appreciate if anyone knows a solution |
Was this ever resolved. I have also been having this use w/ stataMP |
I used the following: I confirmed in terminal as being the correct non-GUI path using: Any advice would be appreciated. Thanks! |
Hi, I know there have been other posts about this issue (namely here #11) but none of these solutions have been working for me. I am getting the following error:
"
Error in seq.int(cutpoints[1] + 1, cutpoints[2] - 1) :
'from' must be a finite number
"
My Stata path and version are set up as follows:
options("RStata.StataPath" = "/Applications/Stata/StataBE.app/Contents/MacOS/StataBE")
options("RStata.StataVersion" = 17)
When I try to run any Stata code, the program starts but immediately crashes, and the .do files says the following:
capture noisily {
/RSTATA: cut me here/
clear
/RSTATA: cut me here/
} /* end capture noisily */
exit, clear STATA
I've tried changing my path to say:
options("RStata.StataPath" = "/Applications/Stata/StataBE.app/Contents/MacOS/stata-be")
Since this seems to have worked for other users, but I get an error that this file or directory doesn't exist. Has anyone figured out any other solutions to this?
Thanks so much for any help you can provide!
The text was updated successfully, but these errors were encountered: