Skip to content
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

Wave becomes ordered factor when using wave.factor=T #34

Open
guymorlan opened this issue Aug 21, 2020 · 0 comments
Open

Wave becomes ordered factor when using wave.factor=T #34

guymorlan opened this issue Aug 21, 2020 · 0 comments

Comments

@guymorlan
Copy link

I have a numeric wave identifier. I create a panel_data object, and then pass the panel_data object to the wbm() function for estimation, using use.wave = T and wave.factor = T, which should use wave variable as an unordered factor according to the documentation.

However, in the model output the wave variable becomes ordered, and wbm() spits out "Unordered factor wave variable was converted to ordered. You should check that the order is correct.". While this error message comes from the panel_data() function, it doesn't arise when I call panel_data(), only when wbm() is called. And so my guess is that somewhere down the line the wave variable is converted to a factor, and then panel_data() is called again, converting the unordered factor to an ordered one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant