Difference between revisions of "Iematch"
Kbjarkefur (talk | contribs) |
Kbjarkefur (talk | contribs) |
||
Line 4: | Line 4: | ||
== Intended use cases == | == Intended use cases == | ||
'''Important Disclaimer:''' there is nothing in iematch that tests that a match is valid from an economic theory aspect. This command only performs the computational task of matching one set of observations to observations in another set. You must perform the tests that you find appropriate in your case. Our understanding is that there is no consensus on a general test for this, but if you have suggestions for tests that we should implement to this command, please let us know, contact information on our [https://github.com/worldbank/ietoolkit GitHub page] | |||
'' | |||
A very common use case for matching in impact evaluations is [[Propensity_Score_Matching|propensity score matching (PSM)]]. There are several user written commands developed specifically for propensity score matching that includes all steps required and in most cases you want to use one of those commands for PSM analysis. However, sometimes your PSM analysis might require a special step that none of the off-the-shelf PSM commands offer, and you will have to set up each step of the PSM analysis yourself. In such a case iematch can do the matching step for you. | |||
iematch can also be used to sample controls to treatment observations using baseline data. This is sometimes done when the controls to the treatment observation was not selected at the time of random treatment assignment and needs to be identified in a larger population. There are many factors that can make this type of pairing invalid despite the matching result provided by iematch being mathematically correct. You always need to use econometrical reasoning for the validity of this technique in your case given the data you have available. | |||
== Instructions == | == Instructions == |
Revision as of 10:49, 12 January 2018
iematch is used to match observations in one group to observations in another group based on a single variable. This single variable could be a p-score but could be any continuous variable.
This article is means to describe use cases, work flow and the reasoning used when developing the commands. For instructions on how to use the command specifically in Stata and for a complete list of the options available, see the help files by typing help iematch
in Stata. This command is a part of the package ietoolkit, to install all the commands in this package including this command, type ssc install ietoolkit
in Stata.
Intended use cases
Important Disclaimer: there is nothing in iematch that tests that a match is valid from an economic theory aspect. This command only performs the computational task of matching one set of observations to observations in another set. You must perform the tests that you find appropriate in your case. Our understanding is that there is no consensus on a general test for this, but if you have suggestions for tests that we should implement to this command, please let us know, contact information on our GitHub page
A very common use case for matching in impact evaluations is propensity score matching (PSM). There are several user written commands developed specifically for propensity score matching that includes all steps required and in most cases you want to use one of those commands for PSM analysis. However, sometimes your PSM analysis might require a special step that none of the off-the-shelf PSM commands offer, and you will have to set up each step of the PSM analysis yourself. In such a case iematch can do the matching step for you.
iematch can also be used to sample controls to treatment observations using baseline data. This is sometimes done when the controls to the treatment observation was not selected at the time of random treatment assignment and needs to be identified in a larger population. There are many factors that can make this type of pairing invalid despite the matching result provided by iematch being mathematically correct. You always need to use econometrical reasoning for the validity of this technique in your case given the data you have available.
Instructions
These instructions are meant to help you understand how to use the command. For technical instructions on how to implement the command in Stata see the help files by typing help iematch
in Stata.
Describe best practices related to this command here.
Reasoning used during development
Describe any non obvious decisions made during development of this command. This can help explain restrictions and requirements
Back to Parent
This article is part of the topic ietoolkit