Skip to content

Commit 0ba2af6

Browse files
committed
fix typo and placeholder text
1 parent a2d90f3 commit 0ba2af6

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

src/mdhlp/iematch.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Title
22

3-
__iematch__ - Matching base observations towards target observations using on a single continous variable.
3+
__iematch__ - Matching base observations towards target observations using on a single continuous variable.
44

55
# Syntax
66

@@ -58,17 +58,20 @@ this variable can be used to include a pair/group fixed effect in a regression.
5858

5959
`_matchCount`: In a many-to-one match, this variable indicates how many base observations were matched towards each matched target observation. This variable can be used as regression weights when controlling for the fact that some observations are matched towards multiple observations.
6060

61-
62-
6361
# Options
6462

65-
__**grp**dummy__(_varname_) is used for xyz. Longer description (paragraph length) of all options, their intended use case and best practices related to them.
63+
__**grp**dummy__(_varname_) is the dummy variable that indicates if
64+
an observation is a base or target observation.
65+
This variable, must be numeric and is only allowed to have the values 1, 0 or missing.
66+
1 indicates a base observation, 0 indicates a target observation,
67+
and observations with a missing value will be excluded from the matching.
68+
6669

6770
__**matc**hvar__(_varname_) is the variable used to compare observations when matching. This must be a numeric variable, and it is typically a continuous variable. Observations with a missing value will be excluded from the matching.
6871

6972
__**id**var__(_varname_) indicates the variable that uniquely and fully identifies the data set. The values in this variable is the values that will be used in the variable that indicates which target observation each base observations matched against. If this option is omitted, a variable called _ID will be generated. The observation in the first row is given the value 1, the second row value 2 and so fourth.
7073

71-
This command assumes only one ID variable as that is the best practice this command follows (see next paragraph for the exception of panel data sets). Here follows two suggested solutions if a data set this command will be used on has more than one ID variable. 1. Do not use the idvar() option and after the matching copy the multiple ID variables yourself. 2. Combine your ID variables into one ID variable. Here are two examples on how that can be done (the examples below work just as well when combining more than two ID variables to one.):
74+
This command assumes only one ID variable as that is the best practice this command follows (see next paragraph for the exception of panel data sets). Here follows two suggested solutions if a data set this command will be used on has more than one ID variable. 1. Do not use the `idvar()` option and after the matching copy the multiple ID variables yourself. 2. Combine your ID variables into one ID variable. Here are two examples on how that can be done (the examples below work just as well when combining more than two ID variables to one.):
7275

7376
```
7477
egen new_ID_var = group(old_ID_var1 old_ID_var2)

0 commit comments

Comments
 (0)