- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I seek your kind help, I'm trying to carry out KMO test, but bellow are the errors:
ERROR: All variables have missing values for all observations in the input data set.
ERROR: All observations in data set WORK.MYDATA have missing values, or the sum of weights or frequencies is nonpositive.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I don't know what the KMO test is. When you post a question, it's helpful if you could include the log from running the step, showing the full code for the step, and all the notes and error messages.
In this case, the error messages you showed seem clear. If you look at the values in your data with PROC FREQ or PROC MEANS, do you see that they are all missing?
As to why they would all be missing values, it's impossible for us to know. Remember that when you run a SAS program, it's important to start debugging from the first error / warning / bad NOTE in the log. Often with this sort of problem, the cause is in earlier code that read in the data, or manipulated the data in some way, when creating WORK.MYDATA.
Next webinar will be in January 2025. Until then, check out our archives: https://www.basug.org/videos. And be sure to subscribe to our our email list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I don't know what the KMO test is. When you post a question, it's helpful if you could include the log from running the step, showing the full code for the step, and all the notes and error messages.
In this case, the error messages you showed seem clear. If you look at the values in your data with PROC FREQ or PROC MEANS, do you see that they are all missing?
As to why they would all be missing values, it's impossible for us to know. Remember that when you run a SAS program, it's important to start debugging from the first error / warning / bad NOTE in the log. Often with this sort of problem, the cause is in earlier code that read in the data, or manipulated the data in some way, when creating WORK.MYDATA.
Next webinar will be in January 2025. Until then, check out our archives: https://www.basug.org/videos. And be sure to subscribe to our our email list.