Help with Penn State LCA for Stata Plugin?

[Jessica Breland]

I just downloaded the Penn State LCA plugin and am having some trouble. Before going on I'd like to note that I've already spoken with the plugin in creators. They were very responsive, but couldn't figure out what was wrong. They did confirm there didn't appear to be anything wrong with how I saved the files or the file paths.

When I first tried to run the first example, I got a "could not load plugin" error. I removed the line spaces at the end of the ado file and tried to run it again, the plugin seems to load, but before it can complete I get an "unrecognized command" error (see below).
I'm running Stata/IC 12.1 for Windows (64-bit x86-64).

Any had a similar problem and overcome in?

Thanks!


This is what the output looks like just before the unrecognized command error in case that helps:


[....]EcstasyEver was float now byte
SexBefore13 was float now byte
ManyPartners was float now byte
ID was float now int
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
(0 real changes made)
unrecognized command
r(199);

[ben earnhart]

link? without more info and access to the plugin, nobody can help you. Most of us don't attend Penn State and take the same classes as you, so it's up to you to provide info to let us try to help you.

[Jessica Breland]

Here's a link to the program developed by individuals at Penn State that I referenced in my first post:

https://methodology.psu.edu/downloads/lcastata

The plugin download includes a few example datasets, which are what I reference above when I say I couldn't run the examples.

Is there other information that would be helpful?

Any insight is appreciated.

And, in case it matters, I'm not a student (at Penn State or elsewhere), which is why I was so impressed that the Penn State creators got back to me so quickly.

[Jessica Breland]

Well, never mind, saving it to the desktop (as opposed to a networked drive) and adding a space to the end of the ado file seemed to fix the problem!