Hi all,
This happens on Stata 13.1 MP for Unix (May 2014 build). I am merging m:1 data with using data which has no missing values. The match variable is type long in both datasets. The resulting data has many missing in the variable that comes from the using data, and I checked and clearly _merge == 3 (matched) cases will have missing values sometimes (~25% of cases). The merge raised no errors nor warnings. What might I be overlooking here? The variable in question is of type byte. This was an MP-heavy operation (64-cores) but it is hard to imagine that only 25% of threads would have read in corrupted data. An int variable next to the byte one in the using data is merged in uncorrupted.
Thanks,
Laszlo
This happens on Stata 13.1 MP for Unix (May 2014 build). I am merging m:1 data with using data which has no missing values. The match variable is type long in both datasets. The resulting data has many missing in the variable that comes from the using data, and I checked and clearly _merge == 3 (matched) cases will have missing values sometimes (~25% of cases). The merge raised no errors nor warnings. What might I be overlooking here? The variable in question is of type byte. This was an MP-heavy operation (64-cores) but it is hard to imagine that only 25% of threads would have read in corrupted data. An int variable next to the byte one in the using data is merged in uncorrupted.
Thanks,
Laszlo
Comment