Closed christophergandrud closed 6 years ago
I believe the issue is the use of the match.data
call within the zelig
call.
This is unnecessary and, because it returns a data frame rather than a matchit object removes zelig
's ability to know about the weights.
So, if you don't use match.data
everything should work as normal.
I'm going to close this issue, but feel free to reopen if it doesn't solve your problem.
From Eric Meng via email:
"do I have to specify "weights" in the Zelig command on purpose if it is run right after MatchIt, because it is said that "Weights that are creating using the matching mechanisms in the MatchIt package will be automatically employed in Zelig analyses if the output object from MatchIt is passed to Zelig as the data argument." in http://docs.zeligproject.org/articles/weights.html?"
with weights specified:
Noninteger weights were set, but the model in Zelig is only able to use integer valued weights.
A bootstrapped version of the dataset was constructed using the weights as sample probabilities.
without weights specified: