Notice: On March 31, it was **announced** that Statalist is moving from an email list to a **forum**. The old list will shut down at the end of May, and its replacement, **statalist.org** is already up and running.

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

From |
"Nick Cox" <n.j.cox@durham.ac.uk> |

To |
<statalist@hsphsun2.harvard.edu> |

Subject |
st: RE: RE: RE: RE: Replace missing values by 0 |

Date |
Tue, 10 Aug 2010 19:33:04 +0100 |

I'd put it this way. If blanks that should be zeros are interpreted by Stata on input as missings, then it's appropriate to map those missings to zeros before analysis. It's easy enough to show that this can happen, e.g. by copy and paste from a spreadsheet to Stata's data editor. Clearly, anyone doing this should be certain that it is exactly what they want. If there are other genuine missings, replacing them by zero is a very bad idea. Nick n.j.cox@durham.ac.uk Lachenbruch, Peter But the original question was about missing values being represented as 0. Use of a blank cell for 0 allows the confusion of missing and true 0. At any rate, if you want to code missing as 0 that's a problem to my mind. * * For searches and help try: * http://www.stata.com/help.cgi?search * http://www.stata.com/support/statalist/faq * http://www.ats.ucla.edu/stat/stata/

**References**:**st: Replace missing values by 0***From:*Hobst <tobias.friedli@access.uzh.ch>

**st: RE: Replace missing values by 0***From:*"Lachenbruch, Peter" <Peter.Lachenbruch@oregonstate.edu>

**st: RE: RE: Replace missing values by 0***From:*"David Radwin" <dradwin@mprinc.com>

**st: RE: RE: RE: Replace missing values by 0***From:*"Lachenbruch, Peter" <Peter.Lachenbruch@oregonstate.edu>

- Prev by Date:
**st: RE: mfx 2 command** - Next by Date:
**RE: st: RE: mfx 2 command** - Previous by thread:
**st: RE: RE: RE: Replace missing values by 0** - Next by thread:
**Re: st: RE: RE: Replace missing values by 0** - Index(es):