Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down on April 23, and its replacement, is already up and running.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: st: Mhbounds v.s. rbounds in stata

From   William Buchanan <>
Subject   Re: st: Mhbounds v.s. rbounds in stata
Date   Mon, 25 Feb 2013 08:33:32 -0800

Hi Wen,

It is unlikely that resubmitting the same question will yield any substantively different results from what you've already experienced. The first answer most would likely provide, is to read the Statalist FAQ as users are required to do prior to posting to the Statalist.  -psmatch2- is a user written command which can be installed from ssc.  Posters are asked to identify where user-written packages come from for several reasons (not limited to, but including determining whether the version said person is using is the most updated version of the package).  Furthermore, the FAQ is explicit about showing your exact syntax and Stata's exact output.  There's good reasoning for this and it helps provide other users with information that could be important to answering your question and giving you the help that you need.


On Feb 25, 2013, at 8:23 AM, Wen Ci <> wrote:

> Dear readers,
> I employed the mhbounds after psmatch2. My outcome variable and treatment variable are all binary variables and I think the mhbounds are a better choice compared to rbounds.
> However the mhbounds produce all insignificant results even when gamm=1, which is inconsistent with my matching results.
> I also tried the rbounds, which produce normal results for my matching.
> Is it because the mhbounds are designed for the matching without replacement? My matching is completed with replacement due to the sample size limitation.
> Thank you for your answer.
> Best,
> Wen
> *
> *   For searches and help try:
> *
> *
> *

*   For searches and help try:

© Copyright 1996–2016 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index