Getting Started With Stata: For Unix Release 13

GETTING STARTED WITH STATA
R
FOR UNIX
RELEASE 13
A Stata Press Publication

StataCorp LP
College Station, Texas
®
Copyright c 1985–2013 StataCorp LP
All rights reserved
Version 13
Published by Stata Press, 4905 Lakeway Drive, College Station, Texas 77845
Typeset in TEX
ISBN-10: 1-59718-113-7
ISBN-13: 978-1-59718-113-6
This manual is protected by copyright. All rights are reserved. No part of this manual may be reproduced, stored
in a retrieval system, or transcribed, in any form or by any means—electronic, mechanical, photocopy, recording, or
otherwise—without the prior written permission of StataCorp LP unless permitted subject to the terms and conditions
of a license granted to you by StataCorp LP to use the software and documentation. No license, express or implied,
by estoppel or otherwise, to any intellectual property rights is granted by this document.
StataCorp provides this manual “as is” without warranty of any kind, either expressed or implied, including, but
not limited to, the implied warranties of merchantability and fitness for a particular purpose. StataCorp may make
improvements and/or changes in the product(s) and the program(s) described in this manual at any time and without
notice.
The software described in this manual is furnished under a license agreement or nondisclosure agreement. The software
may be copied only in accordance with the terms of the agreement. It is against the law to copy the software onto
DVD, CD, disk, diskette, tape, or any other medium for any purpose other than backup or archival purposes.
The automobile dataset appearing on the accompanying media is Copyright
c 1979 by Consumers Union of U.S.,
Inc., Yonkers, NY 10703-1057 and is reproduced by permission from CONSUMER REPORTS, April 1979.
Icons other than the Stata icon are licensed from the Iconfactory, Inc. They remain property of the Iconfactory, Inc.,
and may not be reproduced or redistributed.
Stata, , Stata Press, Mata, , and NetCourse are registered trademarks of StataCorp LP.
Stata and Stata Press are registered trademarks with the World Intellectual Property Organization of the United Nations.
NetCourseNow is a trademark of StataCorp LP.
Other brand and product names are registered trademarks or trademarks of their respective companies.
For copyright information about the software, type help copyright within Stata.
The suggested citation for this software is

StataCorp. 2013. Stata: Release 13 . Statistical Software. College Station, TX: StataCorp LP.
Contents
1 Introducing Stata—sample session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 The Stata user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3 Using the Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4 Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5 Opening and saving Stata datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6 Using the Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7 Using the Variables Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8 Importing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
9 Labeling data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10 Listing data and basic command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
11 Creating new variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12 Deleting variables and observations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13 Using the Do-file Editor—automating Stata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
14 Graphing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
15 Editing graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
16 Saving and printing results by using logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
17 Setting font and window preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
18 Learning more about Stata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
19 Updating and extending Stata—Internet functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
A Troubleshooting Stata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
B Advanced Stata usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
C Stata manual pages for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
conren — Set the color, etc., of Stata(console) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
stata — Stata invocation command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Subject index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
i
Cross-referencing the documentation
When reading this manual, you will find references to other Stata manuals. For example,
[U] 26 Overview of Stata estimation commands
[R] regress
[D] reshape
The first example is a reference to chapter 26, Overview of Stata estimation commands, in the User’s
Guide; the second is a reference to the regress entry in the Base Reference Manual; and the third
is a reference to the reshape entry in the Data Management Reference Manual.
All the manuals in the Stata Documentation have a shorthand notation:
[GSM] Getting Started with Stata for Mac

[GSU] Getting Started with Stata for Unix
[GSW] Getting Started with Stata for Windows
[U ] Stata User’s Guide
[R] Stata Base Reference Manual
[D ] Stata Data Management Reference Manual
[G ] Stata Graphics Reference Manual
[XT] Stata Longitudinal-Data/Panel-Data Reference Manual
[ME] Stata Multilevel Mixed-Effects Reference Manual
[MI] Stata Multiple-Imputation Reference Manual
[MV] Stata Multivariate Statistics Reference Manual
[PSS] Stata Power and Sample-Size Reference Manual
[P ] Stata Programming Reference Manual
[SEM] Stata Structural Equation Modeling Reference Manual
[SVY] Stata Survey Data Reference Manual
[ST] Stata Survival Analysis and Epidemiological Tables Reference Manual
[TS] Stata Time-Series Reference Manual
[TE] Stata Treatment-Effects Reference Manual:
Potential Outcomes/Counterfactual Outcomes
[I] Stata Glossary and Index
[M ] Mata Reference Manual
iii
About this manual
This manual discusses Stata for Unix R
. Stata for Windows R
users should see Getting Started
R
with Stata for Windows; Stata for Mac users should see Getting Started with Stata for Mac. This
manual is intended both for people who are completely new to Stata and for experienced Stata users
new to Stata for Unix. Previous Stata users will also find it helpful as a tutorial on some new features
in Stata for Unix and as a reference for Unix-specific Stata commands.
Following the numbered chapters are two appendixes with information specific to Stata for Unix
and a third appendix with three sections devoted to Unix-specific commands in Stata.
We provide several types of technical support to registered Stata users. [GSU] 4 Getting help
describes the resources available to help you learn about Stata’s commands and features. One of these
resources is the Stata website (http://www.stata.com), where you will find answers to frequently asked
questions (FAQs) as well as other useful information. If you still have questions after looking at the
Stata website and the other resources described in [GSU] 19 Updating and extending Stata—Internet
functionality, you can contact us as described in [U] 3.9 Technical support.
Using this manual

The new user will get the most out of this book by treating it as an exercise book, working through
each example at the computer. The material builds, so material from earlier chapters will often be
used in later chapters. Bear in mind that Stata is a rich and deep statistical package—just as statistics
itself is rich and deep. The time spent working the examples will be repaid with dividends when
doing true statistical analyses.
The experienced user may still have something to learn from this manual despite its name. We
suggest looking through the chapters to see if there is anything new or forgotten.
Stata’s two interfaces

With Stata for Unix, you can choose between two user interfaces. The first option is the graphical
user interface, or GUI, which we will refer to as Stata(GUI). The second option is the nongraphical
user interface, which we will refer to as Stata(console). If instructions apply to either interface, we
will refer simply to Stata.
This manual shows how to complete various tasks by using both the GUI and the console. When the
manual states that a command can be typed into the Command window, we imply that the command
could also be typed at the prompt in the console.
v
1 Introducing Stata—sample session
Introducing Stata
This chapter will run through a sample work session, introducing you to a few of the basic tasks
that can be done in Stata, such as opening a dataset, investigating the contents of the dataset, using
some descriptive statistics, making some graphs, and doing a simple regression analysis. As you
would expect, we will only brush the surface of many of these topics. This approach should give you
a sample of what Stata can do and how Stata works. There will be brief explanations along the way,
with references to chapters later in this book as well as to the system help and other Stata manuals.
We will run through the session by using both menus and dialogs and Stata’s commands so that you
can become familiar with them both.
If you are using Stata(console) rather than Stata(GUI) under Unix, you will not be able to use the
menus and dialogs as they are mentioned here. However, the commands used to produce the output
are included in the output in each case, so you can still work through the examples.
Take a seat at your computer, put on some good music, and work along with the book.
Sample session
The dataset that we will use for this session is a set of data about vintage 1978 automobiles sold
in the United States.
To follow along by pointing and clicking, note that the menu items are given by Menu > Menu
Item > Submenu Item > etc. To follow along by using the Command window, type the commands
that follow a dot (.) in the boxed listings below into the small window at the bottom of the Stata
interface. When there is something of note about the structure of a command, it will be pointed out
as a “Syntax note”.
Start by loading the auto dataset, which is included with Stata. To use the menus,
1. Select File > Example Datasets....
2. Click on Example datasets installed with Stata.
3. Click on use for auto.dta.
The result of this command is fourfold:
• The following output appears in the large Results window:

. sysuse auto.dta
(1978 Automobile Data)

The output consists of a command and its result. The command, sysuse auto.dta, is bold
and follows the period (.). The result, (1978 Automobile Data), is in the standard face
here and is a brief description of the dataset.
Note: If a command intrigues you, you can type help commandname in the Command window
to find help. If you want to explore at any time, Help > Search... can be informative.
1
2 [ GSU ] 1 Introducing Stata—sample session
• The same command, sysuse auto.dta, appears in the tall Review window to the left. The
Review window keeps track of all commands Stata has run, successful and unsuccessful. The
commands can then easily be rerun. See [GSU] 2 The Stata user interface for more information.
• A series of variables appears in the small Variables window to the upper right.
• Some information about make, the first variable in the dataset, appears in the small Properties
window to the lower right.
You could have opened the dataset by typing sysuse auto in the Command window and pressing
Enter. Try this now. sysuse is a command that loads (uses) example (system) datasets. As you will
see during this session, Stata commands are often simple enough that it is faster to use them directly.
This will be especially true once you become familiar with the commands you use the most in your
daily use of Stata.
Syntax note: In the above example, sysuse is the Stata command, whereas auto is the name of
a Stata data file.
Simple data management

We can get a quick glimpse at the data by browsing them in the Data Editor. This can be done
by clicking on the Data Editor (Browse) button, , or by selecting Data > Data Editor > Data
Editor (Browse) from the menus or by typing the command browse.
Syntax note: Here the command is browse and there are no other arguments.
When the Data Editor opens, you can see that Stata regards the data as one rectangular table. This
is true for all Stata datasets. The columns represent variables, whereas the rows represent observations.
The variables have somewhat descriptive names, whereas the observations are numbered.
The data are displayed in multiple colors—at first glance, it appears that the variables listed in black
are numeric, whereas those that are in colors are text. This is worth investigating. Click on a cell
under the make variable: the input box at the top displays the make of the car. Scroll to the right until
[ GSU ] 1 Introducing Stata—sample session 3
you see the foreign variable. Click on one of its cells. Although the cell may display “Domestic”,
the input box displays a 0. This shows that Stata can store categorical data as numbers but display
human-readable text. This is done by what Stata calls value labels. Finally, under the rep78 variable,
which looks to be numeric, there are some cells containing just a period (.). The periods correspond
to missing values.
Looking at the data in this fashion, though comfortable, lends little information about the dataset.
It would be useful for us to get more details about what the data are and how the data are stored.
Close the Data Editor by clicking on its close button.
We can see the structure of the dataset by describing its contents. This can be done either by
going to Data > Describe data > Describe data in memory or in a file in the menus and clicking
on OK or by typing describe in the Command window and pressing Enter. Regardless of which
method you choose, you will get the same result:

. describe
Contains data from /usr/local/stata13/ado/base/a/auto.dta
obs: 74 1978 Automobile Data
vars: 12 13 Apr 2013 17:45
size: 3,182 (_dta has notes)
storage display value

variable name type format label variable label
make str18 %-18s Make and Model

price int %8.0gc Price
mpg int %8.0g Mileage (mpg)
rep78 int %8.0g Repair Record 1978
headroom float %6.1f Headroom (in.)
trunk int %8.0g Trunk space (cu. ft.)
weight int %8.0gc Weight (lbs.)
length int %8.0g Length (in.)
turn int %8.0g Turn Circle (ft.)
displacement int %8.0g Displacement (cu. in.)
gear_ratio float %6.2f Gear Ratio
foreign byte %8.0g origin Car type
Sorted by: foreign

If your listing stops short, and you see a blue more at the base of the Results window, pressing
the Spacebar or clicking on the blue more itself will allow the command to be completed.
At the top of the listing, some information is given about the dataset, such as where it is stored on
disk, how much memory it occupies, and when the data were last saved. The bold 1978 Automobile
Data is the short description that appeared when the dataset was opened and is referred to as a data
label by Stata. The phrase _dta has notes informs us that there are notes attached to the dataset.
We can see what notes there are by typing notes in the Command window:

. notes
_dta:
1. from Consumer Reports with permission

Here we see a short note about the source of the data.
Looking back at the listing from describe, we can see that Stata keeps track of more than just
the raw data. Each variable has the following:
• A variable name, which is what you call the variable when communicating with Stata. Variable
names are one type of Stata name. See [U] 11.3 Naming conventions.
• A storage type, which is the way Stata stores its data. For our purposes, it is enough to know
that types like, say, strnumber are string, or text, variables, whereas all others in this dataset
are numeric. While there are none in this dataset, Stata also allows arbitrarily long strings, or
strLs. strLs can even contain binary information. See [U] 12.4 Strings.
• A display format, which controls how Stata displays the data in tables. See [U] 12.5 Formats:
Controlling how data are displayed.
• A value label (possibly). This is the mechanism that allows Stata to store numerical data while
displaying text. See [GSU] 9 Labeling data and [U] 12.6.3 Value labels.
• A variable label, which is what you call the variable when communicating with other people.
Stata uses the variable label when making tables, as we will see.
A dataset is far more than simply the data it contains. It is also information that makes the data
usable by someone other than the original creator.
Although describing the data tells us something about the structure of the data, it says little about
the data themselves. The data can be summarized by clicking on Statistics > Summaries, tables,
and tests > Summary and descriptive statistics > Summary statistics and clicking on the OK
button. You could also type summarize in the Command window and press Enter. The result is a
table containing summary statistics about all the variables in the dataset:

. summarize
Variable Obs Mean Std. Dev. Min Max
make 0
price 74 6165.257 2949.496 3291 15906
mpg 74 21.2973 5.785503 12 41
rep78 69 3.405797 .9899323 1 5
headroom 74 2.993243 .8459948 1.5 5
trunk 74 13.75676 4.277404 5 23

weight 74 3019.459 777.1936 1760 4840
length 74 187.9324 22.26634 142 233
turn 74 39.64865 4.399354 31 51
displacement 74 197.2973 91.83722 79 425
gear_ratio 74 3.014865 .4562871 2.19 3.89

foreign 74 .2972973 .4601885 0 1

From this simple summary, we can learn a bit about the data. First of all, the prices are nothing like
today’s car prices—of course, these cars are now antiques. We can see that the gas mileages are not
particularly good. Automobile aficionados can get a feel for other esoteric characteristics.
There are two other important items here:
• The make variable is listed as having no observations. It really has no numerical observations
because it is a string (text) variable.
• The rep78 variable has five fewer observations than the other numerical variables. This implies
that rep78 has five missing values.
Although we could use the summarize and describe commands to get a bird’s eye view of the
dataset, Stata has a command that gives a good in-depth description of the structure, contents, and
values of the variables: the codebook command. Either type codebook in the Command window
and press Enter or navigate the menus to Data > Describe data > Describe data contents (codebook)
and click on OK. We get a large amount of output that is worth investigating. In fact, we get more
output than can fit on one screen, as can be seen by the blue more at the bottom of the Results
window. Press the Spacebar a few times to get all the output to scroll past. (For more about more ,
see More in [GSU] 10 Listing data and basic command syntax.) Look over the output to see that
much can be learned from this simple command. You can scroll back in the Results window to see
earlier results, if need be. We will focus on the output for make, rep78, and foreign.
To start our investigation, we would like to run the codebook command on just one variable,
say, make. We can do this, as usual, with menus or the command line. To get the codebook output
for make with the menus, start by navigating to Data > Describe data > Describe data contents
(codebook). When the dialog appears, there are multiple ways to tell Stata to consider only the make
variable:
• We could type make into the Variables field.
• The Variables field is a combobox control that accepts variable names. Clicking on the drop
triangle to the right of the Variables field displays a list of the variables from the current dataset.
Selecting a variable from the list will, in this case, enter the variable name into the edit field.
A much easier solution is to type codebook make in the Command window and then press Enter.
The result is informative:

. codebook make
make Make and Model
type: string (str18), but longest is str17

unique values: 74 missing "": 0/74
examples: "Cad. Deville"
"Dodge Magnum"
"Merc. XR-7"
"Pont. Catalina"
warning: variable has embedded blanks

The first line of the output tells us the variable name (make) and the variable label (Make and Model).
The variable is stored as a string (which is another way of saying “text”) with a maximum length of
18 characters, though a size of only 17 characters would be enough. All the values are unique, so
if need be, make could be used as an identifier for the observations—something that is often useful
when putting together data from multiple sources or when trying to weed out errors from the dataset.
There are no missing values, but there are blanks within the makes. This latter fact could be useful
if we were expecting make to be a one-word string variable.
Syntax note: Telling the codebook command to run on the make variable is an example of using
a varlist in Stata’s syntax.
Looking at the foreign variable can teach us about value labels. We would like to look at the
codebook output for this variable, and on the basis of our latest experience, it would be easy to type
codebook foreign into the Command window (from here on, we will not explicitly say to press
the Enter key) to get the following output:

. codebook foreign
foreign Car type
type: numeric (byte)

label: origin
range: [0,1] units: 1
unique values: 2 missing .: 0/74
tabulation: Freq. Numeric Label
52 0 Domestic
22 1 Foreign

We can glean that foreign is an indicator variable because its only values are 0 and 1. The variable
has a value label that displays Domestic instead of 0 and Foreign instead of 1. There are two
advantages of storing the data in this form:
• Storing the variable as a byte takes less memory because each observation uses 1 byte instead of the
8 bytes needed to store “Domestic”. This is important in large datasets. See [U] 12.2.2 Numeric
storage types.
• As an indicator variable, it is easy to incorporate into statistical models. See [U] 25 Working
with categorical data and factor variables.
Finally, we can learn a little about a poorly labeled variable with missing values by looking at the
rep78 variable. Typing codebook rep78 into the Command window yields

. codebook rep78
rep78 Repair Record 1978
type: numeric (int)

range: [1,5] units: 1
unique values: 5 missing .: 5/74
tabulation: Freq. Value
2 1
8 2
30 3
18 4
11 5
5 .

rep78 appears to be a categorical variable, but because of lack of documentation, we do not know
what the numbers mean. (To see how we would label the values, see Changing data in [GSU] 6 Using
the Data Editor and see [GSU] 9 Labeling data.) This variable has five missing values, meaning
that there are five observations for which the repair record is not recorded. We could use the Data
Editor to investigate these five observations, but we will do this by using the Command window only
because doing so is much simpler. If you recall, the command brought up by clicking on the Data
Editor (Browse) button was browse. We would like to browse only those observations for which
rep78 is missing, so we could type

. browse if missing(rep78)

From this, we see that the . entries are indeed missing values. The . is the default numerical missing
value; Stata also allows .a, . . . , .z as user missing values, but we do not have any in our dataset.
See [U] 12.2.1 Missing values. Close the Data Editor after you are satisfied with this statement.
Syntax note: Using the if qualifier above is what allowed us to look at a subset of the observations.
Looking through the data lends no clues about why these particular data are missing. We decide
to check the source of the data to see if the missing values were originally missing or if they were
omitted in error. Listing the makes of the cars whose repair records are missing will be all we need
because we saw earlier that the values of make are unique. This can be done with the menus and a
dialog:
1. Select Data > Describe data > List data.
2. Click on the drop triangle to the right of the Variables field to show the variable names.
3. Click on make to enter it into the Variables field.
4. Click on the by/if/in tab in the dialog.
5. Type missing(rep78) into the If: (expression) box.
6. Click on Submit. Stata executes the proper command but the dialog remains open. Submit is
useful when experimenting, exploring, or building complex commands. We will primarily use
Submit in the examples. You may click on OK in its place if you like, and it will close the
dialog box.
The same ends could be achieved by typing list make if missing(rep78) in the Command
window. The latter is easier once you know that the command list is used for listing observations.
In any case, here is the output:

. list make if missing(rep78)
make
3. AMC Spirit
7. Buick Opel
45. Plym. Sapporo
51. Pont. Phoenix
64. Peugeot 604

We go to the original reference and find that the data were truly missing and cannot be resurrected.
See [GSU] 10 Listing data and basic command syntax for more information about all that can be
done with the list command.
Syntax note: This command uses two new concepts for Stata commands—the if qualifier and the
missing() function. The if qualifier restricts the observations on which the command runs to only
those observations for which the expression is true. See [U] 11.1.3 if exp. The missing() function
tests each observation to see if it contains a missing value. See [U] 13.3 Functions.
Now that we have a good idea about the underlying dataset, we can investigate the data themselves.
Descriptive statistics
We saw above that the summarize command gave brief summary statistics about all the variables.
Suppose now that we became interested in the prices while summarizing the data because they seemed
fantastically low (it was 1978, after all). To get an in-depth look at the price variable, we can use
the menus and a dialog:
1. Select Statistics > Summaries, tables, and tests > Summary and descriptive statistics >
Summary statistics.
2. Enter or select price in the Variables field.
3. Select Display additional statistics.
4. Click on Submit.
Syntax note: As can be seen from the Results window, typing summarize price, detail will get
the same result. The portion after the comma contains options for Stata commands; hence, detail
is an example of an option.

. summarize price, detail
Price
Percentiles Smallest
1% 3291 3291
5% 3748 3299
10% 3895 3667 Obs 74
25% 4195 3748 Sum of Wgt. 74
50% 5006.5 Mean 6165.257
Largest Std. Dev. 2949.496
75% 6342 13466
90% 11385 13594 Variance 8699526
95% 13466 14500 Skewness 1.653434
99% 15906 15906 Kurtosis 4.819188

From the output, we can see that the median price of the cars in the dataset is only $5,006.50! We can
also see that the four most expensive cars are all priced between $13,400 and $16,000. If we wished
to browse the most expensive cars (and gain some experience with features of the Data Editor), we
could start by clicking on the Data Editor (Browse) button, . Once the Data Editor is open, we
can click on the Filter Observations button, , to bring up the Filter Observations dialog. We can
look at the expensive cars by putting price > 13000 in the Filter by expression field:
Pressing the Apply Filter button filters the data, and we can see that the expensive cars are two
Cadillacs and two Lincolns, which were not designed for gas mileage:
We now decide to turn our attention to foreign cars and repairs because as we glanced through the
data, it appeared that the foreign cars had better repair records. (We do not know exactly what the
categories 1, 2, 3, 4, and 5 mean, but we know the Chevy Monza was known for breaking down.)
Let’s start by looking at the proportion of foreign cars in the dataset along with the proportion of
cars with each type of repair record. We can do this with one-way tables. The table for foreign
cars can be done with menus and a dialog starting with Statistics > Summaries, tables, and tests
> Frequency tables > One-way table and then choosing the variable foreign in the Categorical
variable field. Clicking on Submit yields

. tabulate foreign
Car type Freq. Percent Cum.
Domestic 52 70.27 70.27

Foreign 22 29.73 100.00
Total 74 100.00

We see that roughly 70% of the cars in the dataset are domestic, whereas 30% are foreign. The value
labels are used to make the table so that the output is nicely readable.
Syntax note: We also see that this one-way table could be made by using the tabulate command
together with one variable, foreign. Making a one-way table for the repair records is simple—it
will be simpler if done with the Command window. Typing tabulate rep78 yields

. tabulate rep78
Repair
Record 1978 Freq. Percent Cum.
1 2 2.90 2.90
2 8 11.59 14.49
3 30 43.48 57.97
4 18 26.09 84.06
5 11 15.94 100.00
Total 69 100.00

We can see that most cars have repair records of 3 and above, though the lack of value labels makes us
unsure what a “3” means. Take our word for it that 1 means a poor repair record and 5 means a good
repair record. The five missing values are indirectly evident because the total number of observations
listed is 69 rather than 74.
These two one-way tables do not help us compare the repair records of foreign and domestic cars.
A two-way table would help greatly, which we can get by using the menus and a dialog:
1. Select Statistics > Summaries, tables, and tests > Frequency tables > Two-way table with
measures of association.
2. Choose rep78 as the Row variable.
3. Choose foreign as the Column variable.
4. It would be nice to have the percentages within the foreign variable, so check the Within-row
relative frequencies checkbox.
5. Click on Submit.
Here is the resulting output:

. tabulate rep78 foreign, row
Key
frequency
row percentage
Repair
Record Car type
1978 Domestic Foreign Total
1 2 0 2
100.00 0.00 100.00
2 8 0 8
100.00 0.00 100.00
3 27 3 30
90.00 10.00 100.00
4 9 9 18
50.00 50.00 100.00
5 2 9 11
18.18 81.82 100.00
Total 48 21 69
69.57 30.43 100.00

The output indicates that foreign cars are generally much better than domestic cars when it comes
to repairs. If you like, you could repeat the previous dialog and try some of the hypothesis tests
available from the dialog. We will abstain.
Syntax note: We see that typing the command tabulate rep78 foreign, row would have given
us the same table. Thus using tabulate with two variables yields a two-way table. It makes sense
that row is an option—we went out of our way to check it in the dialog. Using the row option allows
us to change the behavior of the tabulate command from its default.
Continuing our exploratory tour of the data, we would like to compare gas mileages between
foreign and domestic cars, starting by looking at the summary statistics for each group by itself. A
direct way to do this would be to use if qualifiers to summarize mpg for each of the two values of
foreign separately:

. summarize mpg if foreign==0
mpg 52 19.82692 4.743297 12 34

. summarize mpg if foreign==1
mpg 22 24.77273 6.611187 14 41

It appears that foreign cars get somewhat better gas mileage—we will test this soon.
Syntax note: We needed to use a double equal sign (==) for testing equality. The double equal
sign could be familiar to you if you have programmed before. If it is unfamiliar, be aware that it is a
common source of errors when initially using Stata. Thinking of equality as “exactly equal” can cut
down on typing errors.
There are two other methods that we could have used to produce these summary statistics. These
methods are worth knowing because they are less error-prone. The first method duplicates the concept
of what we just did by exploiting Stata’s ability to run a command on each of a series of nonoverlapping
subsets of the dataset. To use the menus and a dialog, do the following:
1. Select Statistics > Summaries, tables, and tests > Summary and descriptive statistics >
Summary statistics and click on the Reset button, .
2. Select mpg in the Variables field.
3. Select the Standard display option (if it is not already selected).
4. Click on the by/if/in tab.
5. Check the Repeat command by groups checkbox.
6. Select or type foreign in the Variables that define groups field.
7. Submit the command.
You can see that the results match those from above. They have a better appearance than the two
commands above because the value labels Domestic and Foreign are used rather than the numerical
values. The method is more appealing because the results were produced without needing to know
the possible values of the grouping variable ahead of time.

. by foreign, sort : summarize mpg
-> foreign = Domestic

mpg 52 19.82692 4.743297 12 34
-> foreign = Foreign

mpg 22 24.77273 6.611187 14 41

Syntax note: There is something different about the equivalent command that appears above: it contains
a prefix command called a by prefix. The by prefix has its own option, namely, sort, to ensure
that like members are adjacent to each other before being summarized. The by prefix command is
important for understanding data manipulation and working with subpopulations within Stata. Make
good note of this example, and consult [U] 11.1.2 by varlist: and [U] 27.2 The by construct for more
information. Stata has other prefix commands for specialized treatment of commands, as explained
in [U] 11.1.10 Prefix commands.
The third method for tabulating the differences in gas mileage across the cars’ origins involves
thinking about the structure of desired output. We need a one-way table of automobile types (foreign
versus domestic) within which we see information about gas mileages. Looking through the menus
yields the menu item Statistics > Summaries, tables, and tests > Other tables > Table of means,
std. dev., and frequencies. Selecting this, entering foreign for Variable 1 and mpg for the Summarize
variable, and submitting the command yields a nice table:

. tabulate foreign, summarize(mpg)
Summary of Mileage (mpg)
Car type Mean Std. Dev. Freq.
Domestic 19.826923 4.7432972 52

Foreign 24.772727 6.6111869 22
Total 21.297297 5.7855032 74

The equivalent command is evidently tabulate foreign, summarize(mpg).
Syntax note: This is a one-way table, so tabulate uses one variable. The variable being summarized
is passed to the tabulate command with an option. Though we will not do it here, the summarize()
option can also be used with two-way tables.
A simple hypothesis test

We would like to run a hypothesis test for the difference in the mean gas mileages. Under the menus,
Statistics > Summaries, tables, and tests > Classical tests of hypotheses > t test (mean-comparison
test) leads to the proper dialog. Select the Two-sample using groups radio button, enter mpg for the
Variable name and foreign for the Group variable name, and Submit the dialog. The results are

. ttest mpg, by(foreign)
Two-sample t test with equal variances
Group Obs Mean Std. Err. Std. Dev. [95% Conf. Interval]
Domestic 52 19.82692 .657777 4.743297 18.50638 21.14747

Foreign 22 24.77273 1.40951 6.611187 21.84149 27.70396
combined 74 21.2973 .6725511 5.785503 19.9569 22.63769
diff -4.945804 1.362162 -7.661225 -2.230384
diff = mean(Domestic) - mean(Foreign) t = -3.6308

Ho: diff = 0 degrees of freedom = 72
Ha: diff < 0 Ha: diff != 0 Ha: diff > 0
Pr(T < t) = 0.0003 Pr(|T| > |t|) = 0.0005 Pr(T > t) = 0.9997

From this, we could conclude that the mean gas mileage for foreign cars is different from that of
domestic cars (though we really ought to have wanted to test this before snooping through the data).
We can also conclude that the command, ttest mpg, by(foreign), is easy enough to remember.
Feel free to experiment with unequal variances, various approximations to the number of degrees of
freedom, and the like.
Syntax note: The by() option used here is not the same as the by prefix command used earlier.
Although it has a similar conceptual meaning, its usage is different because it is a particular option
for the ttest command.
Descriptive statistics—correlation matrices

We now change our focus from exploring categorical relationships to exploring numerical relation-
ships: we would like to know if there is a correlation between miles per gallon and weight. We select
Statistics > Summaries, tables, and tests > Summary and descriptive statistics > Correlations
and covariances in the menus. Entering mpg and weight, either by clicking or by typing, and then
submitting the command yields

. correlate mpg weight
(obs=74)
mpg weight
mpg 1.0000
weight -0.8072 1.0000

The equivalent command for this is natural: correlate mpg weight. There is a negative correlation,
which is not surprising because heavier cars should be harder to push about.
We could see how the correlation compares for foreign and domestic cars by using our knowledge
of the by prefix. We can reuse the correlate dialog or use the menus as before if the dialog is closed.
Click on the by/if/in tab, check the Repeat command by groups checkbox, and enter the foreign
variable to define the groups. As done on page 12, a simple by foreign, sort: prefix in front of
our previous command would work, too:

. by foreign, sort: correlate mpg weight

(obs=52)
mpg weight
mpg 1.0000
weight -0.8759 1.0000

(obs=22)
mpg weight
mpg 1.0000
weight -0.6829 1.0000

We see from this that the correlation is not as strong among the foreign cars.
Syntax note: Although we used the correlate command to look at the correlation of two variables,
Stata can make correlation matrices for an arbitrary number of variables:

. correlate mpg weight length turn displacement
(obs=74)
mpg weight length turn displa~t
mpg 1.0000
weight -0.8072 1.0000
length -0.7958 0.9460 1.0000
turn -0.7192 0.8574 0.8643 1.0000
displacement -0.7056 0.8949 0.8351 0.7768 1.0000

This can be useful, for example, when investigating collinearity among predictor variables.
Graphing data
We are about to make some graphs. You must be using Stata(GUI) to see them.
We have found several things in our investigations so far: We know that the average MPG of
domestic and foreign cars differs. We have learned that domestic and foreign cars differ in other
ways as well, such as in frequency-of-repair record. We found a negative correlation between MPG
and weight—as we would expect—but the correlation appears stronger for domestic cars.
We would now like to examine, with an eye toward modeling, the relationship between MPG and
weight, starting with a graph. We can start with a scatterplot of mpg against weight. The command
for this is simple: scatter mpg weight. Using the menus requires a few steps because the graphs
in Stata may be customized heavily.
1. Select Graphics > Twoway graph (scatter, line, etc.).
2. Click on the Create... button.
3. Select the Basic plots radio button (if it is not already selected).
4. Select Scatter as the basic plot type (if it is not already selected).
5. Select mpg as the Y variable and weight as the X variable.
6. Click on the Submit button.
The Results window shows the command that was issued from the menu:

. twoway (scatter mpg weight)

The command issued when the dialog was submitted is a bit more complex than the command
suggested above. There is good reason for this: the more complex structure allows combining and
overlaying graphs, as we will soon see. In any case, the graph that appears is
40 30
Mileage (mpg)
20
10
2,000 3,000 4,000 5,000

Weight (lbs.)
We see the negative correlation in the graph, though the relationship appears to be nonlinear.
Note: When you draw a graph, the Graph window appears, probably covering up your Results
window. Click on the main Stata window to get the Results window back on top. Want to see the
graph again? Click on the Graph button, . See The Graph button in [GSU] 14 Graphing data
for more information about the Graph button.
Note: You must be using X Windows and Stata(GUI) for the graph to appear. If you are using
Stata(console), a graph will not appear when you use the scatter command. For more information
on obtaining graphs when using Stata(console), see the [G] Graphics Reference Manual .
We would now like to see how the different correlations for foreign and domestic cars are manifested
in scatterplots. It would be nice to see a scatterplot for each type of car, along with a scatterplot for
all the data.
Syntax note: Because we are looking at subgroups, this looks as if it is a job for the by prefix.
Let’s see if this is what we really should use.
Start as before:
1. Select Graphics > Twoway graph (scatter, line, etc.) from the menus.
2. If the Plot 1 dialog is still visible, click on the Accept button and skip to step 4.
3. Go through the process on the previous page to create the graph.
4. Click on the By tab of the twoway - Twoway graphs dialog.
5. Check the Draw subgraphs for unique values of variables checkbox.
6. Enter foreign in the Variables field.
7. Check the Add a graph with totals checkbox.
The command and the associated graph are

. twoway (scatter mpg weight), by(foreign, total)

Domestic Foreign
40
30
20
Mileage (mpg)
10
2,000 3,000 4,000 5,000
Total
40
30
20
10
2,000 3,000 4,000 5,000

Weight (lbs.)
Graphs by Car type
The graphs show that the relationship is nonlinear for both types of cars.
Syntax note: To make the graphs for the combined subgroups, we ended up using a by() option,
not a by prefix. If we had used a by prefix, separate graphs would have been generated instead of
the combined graph created by the by() option.
Model fitting: Linear regression

After looking at the graphs, we would like to fit a regression model that predicts MPG from the
weight and type of the car. From the graphs, we see that the relationship is nonlinear, so we will
try modeling MPG as a quadratic in weight. Also from the graphs, we judge the relationship to be
different for domestic and foreign cars. We will include an indicator (dummy) variable for foreign
and evaluate afterward whether this adequately describes the difference. Thus we will fit the model
mpg = β0 + β1 weight + β2 weight2 + β3 foreign +
foreign is already an indicator (0/1) variable, but we need to create the weight-squared variable.
This can be done with the menus, but here using the command line is simpler. Type

. generate wtsq = weight^2

Now that we have all the variables we need, we can run a linear regression. We will use the menus
and see that the command is also simple. To use the menus, select Statistics > Linear models
and related > Linear regression. In the resulting dialog, choose mpg as the Dependent variable
and weight, wtsq, and foreign as the Independent variables. Submit the command. Here is the
equivalent simple regress command and the resulting analysis-of-variance table.

. regress mpg weight wtsq foreign
Source SS df MS Number of obs = 74
F( 3, 70) = 52.25
Model 1689.15372 3 563.05124 Prob > F = 0.0000
Residual 754.30574 70 10.7757963 R-squared = 0.6913
Adj R-squared = 0.6781
Total 2443.45946 73 33.4720474 Root MSE = 3.2827
mpg Coef. Std. Err. t P>|t| [95% Conf. Interval]
weight -.0165729 .0039692 -4.18 0.000 -.0244892 -.0086567

wtsq 1.59e-06 6.25e-07 2.55 0.013 3.45e-07 2.84e-06
foreign -2.2035 1.059246 -2.08 0.041 -4.3161 -.0909002
_cons 56.53884 6.197383 9.12 0.000 44.17855 68.89913

The results look encouraging, so we will plot the predicted values on top of the scatterplots for each
of the types of cars. To do this, we need the predicted, or fitted, values. This can be done with
the menus, but doing it in the Command window is simple enough. We will create a new variable,
mpghat to hold the predicted MPG for each car. Type

. predict mpghat
(option xb assumed; fitted values)

The output from this command is simply a notification. Go over to the Variables window and scroll
to the bottom to confirm that there is now an mpghat variable. If you were to try this command
when mpghat already existed, Stata would refuse to overwrite your data:

. predict mpghat
mpghat already defined
r(110);

The predict command, when used after a regression, is called a postestimation command. As
specified, it creates a new variable called mpghat equal to
−0.0165729 weight + 1.59 × 10−6 wtsq − 2.2035 foreign + 56.53884
For careful model fitting, there are several features available to you after estimation—one is
calculating predicted values. Be sure to read [U] 20 Estimation and postestimation commands.
We can now graph the data and the predicted curve to evaluate separately the fit on the foreign
and domestic data to determine if our shift parameter is adequate. We can draw both graphs together.
Using the menus and a dialog, do the following:
1. Select Graphics > Twoway graph (scatter, line, etc.) from the menus.
2. If there are any plots listed, click on the Reset button, , to clear the dialog box.
3. Create the graph for mpg versus weight:

a. Click on the Create... button.
b. Be sure that Basic plots and Scatter are selected.
c. Select mpg as the Y variable and weight as the X variable.
d. Click on Accept.
4. Create the graph showing mpghat versus weight
a. Click on the Create... button.
b. Select Basic plots and Line.
c. Select mpghat as the Y variable and weight as the X variable.
d. Check the Sort on x variable box. Doing so ensures that the lines connect from smallest
to largest weight values, instead of the order in which the data happen to be.
e. Click on Accept.
5. Show two plots, one each for domestic and foreign cars, on the same graph:
a. Click on the By tab.
b. Check the Draw subgraphs for unique values of variables checkbox.
c. Enter foreign in the Variables field.
Here are the resulting command and graph:

. twoway (scatter mpg weight) (line mpghat weight, sort), by(foreign)

Domestic Foreign
40
30
20
10
2,000 3,000 4,000 5,000 2,000 3,000 4,000 5,000

Weight (lbs.)
Mileage (mpg) Fitted values
Graphs by Car type
Here we can see the reason for enclosing the separate scatter and line commands in parentheses:
they can thereby be overlaid by submitting them together. The fit of the plots looks good and is cause
for initial excitement. So much excitement, in fact, that we decide to print the graph and show it to
an engineering friend. We print the graph, being careful to print the graph (and not all our results),
by choosing File > Print... from the Graph window menu bar.
When we show our graph to our engineering friend, she is concerned. “No,” she says. “It should
take twice as much energy to move 2,000 pounds 1 mile compared with moving 1,000 pounds the
same distance: therefore, it should consume twice as much gasoline. Miles per gallon is not quadratic
in weight; gallons per mile is a linear function of weight. Don’t you remember any physics?”
We try out what she says. We need to generate an energy-per-distance variable and make a
scatterplot. Here are the commands that we would need—note their similarity to commands issued
earlier in the session. There is one new command, the label variable command, which allows us
to give the gpm100m variable a variable label so that the graph is labeled nicely.

. generate gp100m = 100/mpg
. label variable gp100m "Gallons per 100 miles"
. twoway (scatter gp100m weight), by(foreign, total)

Domestic Foreign
8
6
4
Gallons per 100 miles
2
2,000 3,000 4,000 5,000
Total
8
6
4
2
2,000 3,000 4,000 5,000

Weight (lbs.)
Graphs by Car type
Sadly satisfied that the engineer is indeed correct, we rerun the regression:

. regress gp100m weight foreign
F( 2, 71) = 113.97
Model 91.1761694 2 45.5880847 Prob > F = 0.0000
Residual 28.4000913 71 .400001287 R-squared = 0.7625
Total 119.576261 73 1.63803097 Root MSE = .63246
gp100m Coef. Std. Err. t P>|t| [95% Conf. Interval]
weight .0016254 .0001183 13.74 0.000 .0013896 .0018612

foreign .6220535 .1997381 3.11 0.003 .2237871 1.02032
_cons -.0734839 .4019932 -0.18 0.855 -.8750354 .7280677

We find that foreign cars had better gas mileage than domestic cars in 1978 because they were so
light. According to our model, a foreign car with the same weight as a domestic car would use an
additional 5/8 gallon (or 5 pints) of gasoline per 100 miles driven. With this conclusion, we are
satisfied with our analysis.
Commands versus menus

In this chapter, you have seen that Stata can operate either with menu choices and dialogs or with
the Command window. As you become more familiar with Stata, you will find that the Command
window is typically much faster for oft-used commands, whereas the menus and dialogs are faster
when building up complex commands, such as those that create graphs.
One of Stata’s great strengths is the consistency of its command syntax. Most of Stata’s commands
share the following syntax, where square brackets mean that something is optional, and a varlist is a
list of variables.

prefix: command varlist if in weight , options
Some general rules:

• Most commands accept prefix commands that modify their behavior; see [U] 11.1.10 Prefix
commands for details. One of the common prefix commands is by.
• If an optional varlist is not specified, all the variables are used.
• if and in restrict the observations on which the command is run.
• options modify what the command does.
• Each command’s syntax is found in the system help and the reference manuals or, for commands
specific to Stata for Unix, in [GSU] C Stata manual pages for Unix.
• Stata’s command syntax includes more than we have shown you here, but this introduction
should get you started. For more information, see [U] 11 Language syntax and help language.
We saw examples using all the pieces of this except for the in qualifier and the weight clause. The
syntax for all commands can be found in the system help along with examples—see [GSU] 4 Getting
help for more information. The consistent syntax makes it straightforward to learn new commands
and to read others’ commands when examining an analysis.
Here is an example of reading the syntax diagram that uses the summarize command from earlier
in this chapter. The syntax diagram for summarize is typical:

summarize varlist if in weight , options
This means that
command by itself is valid: summarize

command followed by a varlist
(variable list) is valid: summarize mpg
summarize mpg weight
command with if (with or without
a varlist) is valid: summarize if mpg>20
summarize mpg weight if mpg>20
and so on.
You can learn about summarize in [R] summarize, or select Help > Stata Command... and enter
summarize, or type help summarize in the Command window.
Keeping track of your work

It would have been useful if we had made a log of what we did so that we could conveniently
look back at interesting results or track any changes that were made. You will learn to do this in
[GSU] 16 Saving and printing results by using logs. Your logs will contain commands and their
output—another reason to learn command syntax is so that you can remember what you have done.
To make a log file that keeps track of everything appearing in the Results window, click on the
Log button, which looks like a lab notebook, . Choose a place to store your log file, and give
it a name, just as you would for any other document. The log file will save everything that appears
in the Results window from the time you start a log file to the time you close it.
Conclusion
This chapter introduced you to Stata’s capabilities. You should now read and work through the
rest of this manual. Once you are done here, you can read the User’s Guide.
2 The Stata user interface
The windows
This chapter introduces the core of Stata(GUI)’s interface: its main windows, its toolbar, its menus,
and its dialogs. This chapter assumes that you are running Stata(GUI). To reduce clutter, we will refer
to the Stata(GUI) as Stata throughout.
The five main windows are the Review, Results, Command, Variables, and Properties windows.
Except for the Command window, each window has its name in its title bar. These five windows are
typically in use the whole time Stata is open. There are other, more specialized windows such as the
Viewer, Data Editor, Variables Manager, Do-file Editor, Graph, and Graph Editor windows—these
are discussed later in this manual.
To open any window or to reveal a window hidden by other windows, select the window from
the Window menu, or select the proper item from the toolbar. You can also use Alt+Tab to cycle
through all open windows (Stata and other) if you want to change windows from the keyboard. Many
of Stata’s windows have functionality that can be accessed by clicking on the right mouse button
(right-clicking) within the window. Right-clicking displays a contextual menu that, depending on the
window, allows you to copy text, set the preferences for the window, or print the contents of the
window. When you copy text or print, we recommend that you always right-click on the window
rather than use the menu bar or toolbar so that you can be sure of where and what you are copying
or printing.
23
24 [ GSU ] 2 The Stata user interface
The toolbar
This is the toolbar:
The toolbar contains buttons that provide quick access to Stata’s more commonly used features.
If you forget what a button does, hold the mouse pointer over the button for a moment, and a tooltip
will appear with a description of that button.
Buttons that include both an icon and an arrow display a menu if you click on the arrow. Here is
an overview of the toolbar buttons and their functions:
Open opens a Stata dataset. Click on the button to open a dataset with the Open
dialog. Click on the arrow to select a dataset from a menu of recently opened datasets.
Save saves the Stata dataset currently in memory to disk.
Print prints the Results window. Clicking on the arrow displays a list of windows.
Select a window name to print its contents.
Log begins a new log or closes, suspends, or resumes the current log. See [GSU] 16 Sav-
ing and printing results by using logs for an explanation of log files.
Viewer opens the Viewer or brings a Viewer to the front of all other windows.
Click on the button to open a new Viewer. See [GSU] 3 Using the Viewer for more
information.
Graph brings a Graph window to the front of all other windows. Click on the button
to bring the Graph window to the front. Click on the arrow to select a Graph window
to bring to the front. See The Graph button in [GSU] 14 Graphing data for more
information.
Do-file Editor opens the Do-file Editor or brings a Do-file Editor to the front of
all other windows. Click on the button to open a new Do-file Editor. Click on the
arrow to select a Do-file Editor to bring to the front. See [GSU] 13 Using the Do-file
Editor—automating Stata for more information.
Data Editor (Edit) opens the Data Editor or brings the Data Editor to the front of
the other Stata windows. See [GSU] 6 Using the Data Editor for more information.
Data Editor (Browse) opens the Data Editor in browse mode. See Browse mode in
[GSU] 6 Using the Data Editor for more information.
Variables Manager opens the Variables Manager. See [GSU] 7 Using the Variables
Manager for more information.
Clear more Condition tells Stata to continue when it has paused in the middle
of long output. See [GSU] 10 Listing data and basic command syntax for more
information.
Break stops the current task in Stata. See [GSU] 10 Listing data and basic command
syntax for more information.
[ GSU ] 2 The Stata user interface 25
The Command window

Commands are submitted to Stata from the Command window. The Command window supports
basic text editing, copying and pasting, a command history, function-key mapping, and variable-name
completion.
From the Command window, pressing
Page Up steps backward through the command history.
Page Down steps forward through the command history.
Tab auto-completes a partially typed variable name, when possible.
See [U] 10 Keyboard use for more information about keyboard shortcuts for the Command window.
The command history allows you to recall a previously submitted command, edit it if you wish,
and then resubmit it. Commands submitted by Stata’s dialogs are also included in the command
history, so you can recall and submit a command without having to open the dialog again.
The Results window

The Results window contains all the commands and their textual results you have entered during
the Stata session. While you can scroll through the Results window to look at work you have done,
it is much simpler to search within the Results window by using the find bar. By default, the find bar
is hidden. You can toggle its visibility by clicking the magnifying glass button, , in the Results
window titlebar.
You can clear out the Results window at any time by right-clicking in the Results window and
selecting Clear Results from the contextual menu. This action is not undoable.
The Review window

The Review window shows the history of commands that have been entered. It displays successful
commands in black and unsuccessful commands, along with their error codes, in red.
The toolbar has two tools for manipulating the contents of the Review window. Clicking on the
magnifying glass button, , in the Review window titlebar toggles the visibility of these tools. Text
entered in the Filter commands here field will filter the commands appearing in the Review window.
By default, the filter will ignore case and find any commands containing any of the words in the filter.
Clicking on the arrow under the magnifying glass will allow you to change this behavior. Clicking
on the hide errors button, , toggles the hiding of commands that ran with an error.
No commands are deleted by using these tools—all that is affected is their visibility.
To enter a command from the Review window, you can
• Click once on a past command to copy it to the Command window, replacing the contents of
the Command window.
• Double-click on a past command to resubmit it. Executing the command adds the command to
the bottom of the Review window.
Right-clicking on the Review window displays a menu from which you can select various actions:
• Cut removes the selected commands from the Review window and places them on the Clipboard.
• Copy copies the selected commands to the Clipboard.
• Delete removes the selected commands from the Review window.
• Select All selects all the commands in the Review window, including those before and after
the commands currently displayed.
• Clear All clears out all the commands from the Review window, including those before and
after the commands currently displayed.
• Do Selected submits all the selected commands and adds them to the bottom of the command
history. Stata will attempt to run all the selected commands, even those containing errors, and
will not stop even if a command causes an error.
• Send to Do-file Editor places all the selected commands into a new Do-file Editor window.
• Save All... brings up a Save Review Contents dialog, which allows you to save all the commands
in the Review window, including those before and after the commands currently displayed, in
a do-file. (See [GSU] 13 Using the Do-file Editor—automating Stata for more information on
do-files.)
• Save Selected... brings up a Save Review Contents dialog, which allows you to save the selected
commands in the Review window in a do-file.
• Preferences... allows you to edit the preferences for the Review window.
The Variables window

The Variables window shows the list of variables in the dataset, along with selected properties of
the variables. By default, it shows all the variables and their variable labels.
Click once on a variable in the Variables window to select it. Multiple variables can be selected
in the usual fashion, either by Ctrl -clicking on nonadjacent variables or by clicking on a variable and
shift-clicking on a second variable to select all intervening variables.
Double-clicking on a variable in the Variables window puts the selected variable at the insertion
point in the Command window.
The leftmost column of the Variables window is called the one-click paste column. You can also
send variables to the Command window by hovering the mouse over the one-click paste column of
the Variables window and clicking on the arrow that appears.
The Variables window supports filtering and reordering of variables. Clicking on the magnifying
glass button, , in the Variables window titlebar toggles the visibility of the filter. Text entered in
the Filter variables here field will filter the variables appearing in the Variables window. The filter is
applied to all visible columns and shows all variables that match the criteria in at least one column.
By default, the filter will ignore case and show any variables for which at least one column contains
any of the words in the filter. Clicking on the arrow by the magnifying glass will allow you to change
this behavior as well as add or remove additional columns containing information about the variables.
You can reorder the variables in the Variables window by clicking on any column header. The
first click sorts in ascending order, the second click sorts in descending order, and the third click
puts the variables back in dataset order. Thus clicking on the Variable column header will make the
Variables window display the variables in alphabetical order. Sorting in the Variables window is live,
so if you change a property of a variable when the Variables window is sorted by that property, it will
automatically move the variable to its proper location. Reordering the display order of the variables
in the Variables window does not affect the order of the variables in the dataset itself.
Right-clicking on a variable in the Variables window displays a menu from which you can select
• Keep Only Selected Variables to keep just the selected variables in the dataset in memory.
You will be asked for confirmation. This affects only the dataset in memory, not the dataset as
saved on your disk. See [GSU] 12 Deleting variables and observations for more information.
• Drop Selected Variables to drop, or eliminate, the selected variables from the dataset in memory.
You will be asked for confirmation. Just as above, this affects only the dataset in memory, not
the dataset as saved on your disk. See [GSU] 12 Deleting variables and observations for more
information.
• Copy Varlist to copy the selected variable names to the clipboard.
• Select All to select all variables in the dataset that satisfy the filter conditions. If no filter has
been specified, all variables will be selected.
• Send Varlist to Command Window to send all selected variables to the Command window.
• Preferences... to change the preferences for the Variables window.
Items from the contextual menu issue standard Stata commands, so working by right-clicking is just
like working directly in the Command window.
If you would like to hide the Variables window, grab the divider between the Variables window
and the Results window and drag it all the way to the right. This is like resizing the Variables window
to have zero width. Hiding the Variables window will also hide the Properties window.
To reveal a hidden Variables window, drag the right edge of the main Stata window to the left.
You can also select Window > Variables to expose a narrow Variables window.
The Properties window

The Properties window displays variable and dataset properties. If a single variable is selected
in the Variables window, its properties are displayed. If there are multiple variables selected in the
Variables window, the Properties window will display properties that are common across all selected
variables.
Clicking the lock icon in the Properties window titlebar toggles the ability to alter properties of
the selected variables. By default, changes are not allowed. Once the properties are unlocked, you
can make any changes to variable or dataset properties you like. Each change you make will create
a command that appears in the Results and Command windows, as well as in any command log, so
the changes are reproducible. Using the Properties window is one of the simplest ways of managing
notes, changing variable and value labels, and changing display formats. See [D] notes, [D] label,
and [D] format.
Clicking the arrow buttons next to the lock icon will select the previous or next variable shown
in the Variables window, and that selection will be reflected in the Properties window.
If you would like to hide the Properties window, click on the disclosure control in the titlebar
of the Variables window. If you would like to reveal a hidden Properties window, click on the
disclosure control in the titlebar of the Variables window.
You should also investigate the Variables Manager, explained in [GSU] 7 Using the Variables
Manager, because it extends these capabilities and provides a good interface for managing variables.
Menus and dialogs

There are two ways by which you can tell Stata what you would like it to do: you can use menus
and dialogs, or you can use the Command window. When you worked through the sample session in
[GSU] 1 Introducing Stata—sample session, you saw that both ways have strengths. We will discuss
the menus and dialogs here.
Stata’s Data, Graphics, and Statistics menus provide point-and-click access to almost every
command in Stata. As you will learn, Stata is fully programmable, and Stata users can even create
their own dialogs and menus. The User menu provides a place for programmers to add their own
menu items. Initially, it contains only some empty submenus. As an example, suppose you wish
to perform a Poisson regression. You could type Stata’s poisson command, or you could select
Statistics > Count outcomes > Poisson regression, which would display this dialog:
This dialog provides access to all the functionality of Stata’s poisson command. Because the
dependent and independent variables must be numeric, you will find that the combobox will display
only numeric variables for choosing. The poisson command has many options that can be accessed
by clicking on the multiple tabs across the top of the dialog. The first time you use the dialog for a
command, it is a good idea to look at the contents of each tab so that you will know all the dialog’s
capabilities.
The dialogs for many commands have the by/if/in and Weights tabs. These provide access to
Stata’s commands and qualifiers for controlling the estimation sample and dealing with weighted data.
See [U] 11 Language syntax for more information on these features of Stata’s language.
The dialogs for most estimation commands have the Maximization tab for setting the maximization
options (see [R] maximize). For example, you can specify the maximum number of iterations for the
optimizer.
Most dialogs in Stata provide the same six buttons you see at the bottom of the poisson dialog
above.
OK issues a Stata command based on how you have filled out the fields in
the dialog and then closes the dialog.
Cancel closes the dialog without doing anything—just as clicking on the

dialog’s close button does.
Submit issues a command just like OK but leaves the dialog on the screen so
that you can make changes and issue another command. This feature is handy
when, for example, you are learning a new command or putting together a
complicated graph.
Help provides access to Stata’s help system. Clicking on this button will
typically take you to the help file for the Stata command associated with the
dialog. Clicking on it here would take you to the poisson help file. The help
file will have tabs above groups of options to show which dialog tab contains
which options.
Reset resets the dialog to its default state. Each time you open a dialog, it
will remember how you last filled it out. If you wish to reset its fields to their
default values at any time, simply click on this button.
Copy Command to Clipboard behaves much like the Submit button, but
rather than issuing a command, it copies the command to the Clipboard. The
command can then be pasted elsewhere (such as in the Do-file Editor).
The command issued by a dialog is submitted just as if you had typed it by hand. You can see
the command in the Results window and in the Review window after it executes. Looking carefully
at the full command will help you learn Stata’s command syntax.
In addition to being able to access the dialogs for Stata commands through Stata’s menus, you
can also invoke them by using two other methods. You may know the name of a Stata command for
which you want to see a dialog, but you might not remember how to navigate to that command in
the menu system. Simply type db commandname to launch the dialog for commandname:

. db poisson

You will also find access to the dialog for a command in that command’s help file; see [GSU] 4 Getting
help for more details.
As you read this manual, we will present examples of Stata commands. You may type those
examples as presented, but you should also experiment with submitting those commands by using
their dialogs. Use the db command described above to quickly launch the dialog for any command
that you see in this manual.
The working directory

If you look at the screenshot on page 23, you will notice the status bar at the base of the main
Stata window that contains the name of the current working directory /home/mydir/data. This path
indicates that /home/mydir/data is the current working directory. The current working directory is
the folder where graphs and datasets will be saved when typing commands such as save filename.
It does not affect the behavior of menu-driven file actions such as File > Save or File > Open....
Once you have started Stata, you can change the current working directory with the cd command.
See [D] cd for full details. Stata always displays the name of the current working directory so that it
is easy to tell where your graphs and datasets will be saved.
3 Using the Viewer
The Viewer in Stata(GUI)

In this chapter, we are going to assume that you are using Stata(GUI) and therefore have access
to Stata’s menus, links, and windows. If you are not using Stata(GUI), please be aware that you
can obtain the same information, but instead of using the menus, links, and windows, you will use
commands at the Stata dot prompt. Throughout the following chapters, we will include the equivalent
commands that the Stata(console) user can use. The remaining manuals in the Stata Documentation
also assume that you are using Stata(GUI).
The Viewer’s purpose

The Viewer is a versatile tool in Stata(GUI). It will be the first place you can turn for help within
Stata, but it is far more than just a help system. You can also use the Viewer to add, delete, and
manage third-party extensions to Stata that are known as user-written programs; to view and print
Stata logs from both your current and your previous Stata sessions; to view and print any other
Stata-formatted (SMCL) or plain-text file; and even to launch your web browser to follow hyperlinks.
This chapter focuses on the general use of the Viewer, its buttons, and a brief summary of the
commands that the Viewer understands. There is more information about using the Viewer to find
help in [GSU] 4 Getting help and for installing user-written commands in [GSU] 19 Updating and
extending Stata—Internet functionality.
To open a new Viewer window, you may either click on the Viewer button, , or select Window
> Viewer > New Viewer. A Viewer opened by these means provides links that allow you to perform
several tasks.
30
[ GSU ] 3 Using the Viewer 31
Viewer buttons
The toolbar of the Viewer has multiple buttons, a command box, and a search box.
Back goes back one step in your viewing trail.
Forward goes forward one step in your viewing trail,

assuming you backtracked.
Refresh refreshes the Viewer, in case you are viewing
something that has changed since you opened the Viewer.
Print prints the contents of the Viewer.
Find opens the find bar at the bottom of the Viewer (see
below).
Search Chooses the scope of help searches in the Viewer.
The Find bar is used to find text within the current Viewer. To reveal the Find bar at the bottom
of the window, click on the Find button (see above):
The Find bar has its own buttons, fields, and checkboxes.
Close closes the Find bar.
Find is the field for entering the search text you would
like to find. You can change the search options by using
the checkboxes.
Next jumps to the next instance of the search text; it
automatically wraps past the end of the Viewer document
if there are no further instances of the search text.
Previous jumps to the previous instance of the search
text; it automatically wraps past the start of the Viewer
document if there are no previous instances of the search
text.
Highlight All highlights other instances of the search
text (in yellow, by default) when this box is checked.
If unchecked, only the current instance of the search text
is highlighted (in black, by default). By default, this box
is checked.
Match Case, when checked, considers uppercase and low-
ercase letters to be different. When this box is checked,
searching for This would not find this. If unchecked,
uppercase and lowercase letters are considered the same,
so searching for This would find this. By default, this
box is unchecked.
32 [ GSU ] 3 Using the Viewer
Viewer’s function
The Viewer is similar to a web browser. It has links (shown in blue text) that you can click on
to see related help topics and to install and manage third-party software. When you move the mouse
pointer over a link, the status bar at the bottom of the Viewer shows the action associated with that
link. If the action of a link is help logistic, clicking on that link will show the help file for the
logistic command in the Viewer. Middle-clicking on a link in a Viewer window (if you do not have
a three-button mouse, then Shift+clicking) will open the link in a new Viewer window. Ctrl +clicking
will open the link in a new tab in the current Viewer window.
You can open a new Viewer by selecting Window > Viewer > New Viewer or by clicking on the
Viewer button on the toolbar. Entering a help command from the Command window will also open
a new Viewer.
To bring a Viewer to the front of all other Viewers, select Window > Viewer and choose a Viewer
from the list there. Selecting Close All Viewers closes all open Viewer windows.
Viewing local text files, including SMCL files

In addition to viewing built-in Stata help files, you can use the Viewer to view Stata Markup
and Control Language (SMCL) files such as those typically produced when logging your work (see
[GSU] 16 Saving and printing results by using logs) as well as plain-text files. To open a file and
view its contents, simply select File > View..., and you will be presented with a dialog:
You may either type in the name of the file that you wish to view and click on OK, or you may
click on the Browse... button to open a standard file dialog that allows you to navigate to the file.
If you currently have a log file open, you may view the log file in the Viewer. This method has
one advantage over scrolling back in the Results window: what you view stays fixed even as output
is added to the Results window. If you wish to view a current log file, select File > Log > View...,
and the usual dialog will appear but with the path and filename of the current log already in the
field. Simply click on OK, and the log will appear in the Viewer. See [GSU] 16 Saving and printing
results by using logs for more details.
Viewing remote files over the Internet

If you want to look at a remote file over the Internet, the process is similar to viewing a local file,
only instead of using the Browse... button, you type the URL of the file that you want to see, such as
http://www.stata.com/man/readme.smcl. You should use the Viewer only to view text or SMCL files.
If you enter the URL of, say, an arbitrary webpage, you will see the HTML source of the page instead
of the usual browser rendering.
[ GSU ] 3 Using the Viewer 33
Navigating within the Viewer

In addition to using the scrollbar to navigate the Viewer window, you also can use the up and
down arrow keys and Page Up and Page Down keys to do the same. Pressing the up or down arrow
key scrolls the window a line at a time. Pressing the Page Up or Page Down key scrolls the window
a screen at a time.
Printing
To print the contents of the Viewer, right-click on the window and select Print.... You may also
select File > Print > Viewer name or click on the arrow of the Print toolbar button to select from a
menu of open windows to print.
Tabs in the Viewer

The Viewer window can have multiple tabs. You may view different files or different views of the
same file in different tabs. Clicking on the Open New Tab button, , will open a new tab in the
current Viewer window.
Right-clicking on the Viewer window

Right-clicking on the Viewer window displays a contextual menu that offers these options:
• Select All to select all text in the Viewer.
• Preferences... to edit the preferences for the Viewer window.
• Print... to print the contents of the Viewer window.
Searching for help in the Viewer

The search box in the Viewer can be used to search documentation. Click on the magnifying glass;
choose Search all, Search documentation and FAQs, or Search net resources; and then type a word
or phrase in the search box and press Enter. For more extensive information about using the Viewer
for help, see [GSU] 4 Getting help.
Commands in the Viewer

Everything that can be done in the Viewer by clicking on links and buttons can also be done by
typing commands in the command box at the top of the window or on the Stata command line. Some
tasks that can be performed in the Viewer are
• obtaining help (see [GSU] 4 Getting help):
Type contents to view the contents of Stata’s help system.
Type commandname to view the help file for a Stata command.
• searching (see [GSU] 4 Getting help):
Type search keyword to search documentation, FAQs, and net resources for a topic.
Type search keyword, local to search only documentation and FAQs for a topic.
Type search keyword, net to search only net resources for a topic.
34 [ GSU ] 3 Using the Viewer
• finding and installing User-written programs (see [GSU] 4 Getting help and [GSU] 19 Updating
and extending Stata—Internet functionality):
Type net from http://www.stata.com/ to find and install Stata Journal, Stata Technical
Bulletin, and user-written programs from the Internet.
Type ado to review user-written programs you have installed.
Type ado uninstall to uninstall user-written programs you have installed on your
computer.
• viewing files in the Viewer:
Type view filename.smcl to view SMCL files.
Type view filename.txt to view text files.
Type view filename.log to view text log files.
• viewing files in the Results window:
Type type filename.smcl in the Command window to view SMCL files in the Results
window.
Type type filename.txt in the Command window to view text files in the Results
window.
Type type filename.log in the Command window to view text log files in the Results
window.
• launching your browser to view an HTML file:
Type browse URL to launch your browser.
• keeping informed:
Type news to see the latest news from http://www.stata.com.
Using the Viewer from the Command window

Typing help commandname in the Command window will bring up a new Viewer showing the
requested help.
4 Getting help
System help
Stata’s help system provides a wealth of information to help you learn and use Stata. To find out
which Stata command will perform the statistical or data management task you would like to do, you
should generally follow these steps:
1. Select Help > Search..., choose Search all, and enter the topic or keywords. This search will
open a new Viewer window containing information about Stata commands, references to articles
in the Stata Journal , links to Frequently Asked Questions (FAQs) on Stata’s website, links to
videos on Stata’s YouTube channel, links to selected external websites, and links to user-written
commands.
2. Read through the results. If you find a useful command, click on the link to the appropriate
command name to open its help file.
3. Read the help file for the command you chose.
4. If you want more in-depth help, click on the link from the name of the command to the PDF
documentation, read it, then come back to Stata.
5. If the first help file you went to is not what you wanted, either click on the Also See button
and choose a link to related help files or click on the Back button to go back to the previous
document and go from there to other help files.
6. With the help file open, click on the Command window and enter the command, or click on
the Dialog button and choose a link to open a dialog for the command.
7. If, at any time, you want to begin again with a new search, enter the new search terms in the
search box of the Viewer window.
8. If you select Search documentation and FAQs, Stata searches its keyword database for official
Stata commands, Stata Journal and STB articles and software, FAQs, and videos. If you select
Search net resources, Stata searches for user-written commands, whether they are from the
Stata Journal, the STB, or elsewhere; see [GSU] 19 Updating and extending Stata—Internet
functionality for more information.
Let’s illustrate the help system with an example. You will get the most benefit from the example
if you work along at your computer.
Suppose that we have been given a dataset about antique cars and that we need to know what
it contains. Though we still have a vague notion of having seen something like this while working
through the example session in [GSU] 1 Introducing Stata—sample session, we do not remember
the proper command.
Start by typing sysuse auto, clear in the Command window to bring the dataset into memory.
(See [GSU] 5 Opening and saving Stata datasets for information on the clear option.)
Following the above approach,
1. select Help > Search....
2. check that the Search all radio button is selected.
3. type dataset contents into the search box and click on OK or press Enter. Before we press
Enter, the window should look like
35
36 [ GSU ] 4 Getting help
4. Stata will now search for “dataset contents” among the Stata commands, the reference manuals,
the Stata Journal, the FAQs on Stata’s website, and user-written commands. Here is the result:
5. upon seeing the results of the search, we see two commands that look promising: codebook
and describe. Because we are interested in the contents of the dataset, we decide to check out
the codebook command. The [D] means that we could look up the codebook command in the
Data Management Reference Manual. The blue codebook link in (help codebook) means
that there is a system help file for the codebook command. This is what we are interested in
right now.
6. click on the blue codebook link. Links can take you to a variety of resources, such as help
for Stata commands, dialogs, and even webpages. Here the link goes to the help file for the
codebook command.
[ GSU ] 4 Getting help 37
7. what is displayed is typical for help for a Stata command. Help files for Stata commands
contain, from top to bottom, these features:
a. The quick access toolbar with three buttons:
i. The Dialog button shows links to any dialogs associated with the command.
ii. The Also See button shows links to related PDF documentation and help files.
iii. The Jump To button shows links to other sections within the current help file.
b. The very first link in the Title section is a link to the manual entry for the command in
the PDF documentation. Clicking on the link will open your PDF viewer and show you
the complete documentation for the command—in this case, codebook.
c. The command’s syntax, that is, rules for constructing a command that Stata will correctly
interpret. The square brackets here indicate that all the arguments to codebook are optional
but that if we wanted to specify them, we could use a varlist, an if qualifier, or an in
qualifier, along with some options. (Options vary greatly from command to command.)
The options are listed directly under the command and are explained in some detail later
in the help file. You will learn more about command syntax in [GSU] 10 Listing data
and basic command syntax.
d. A description of the command. Because “codebook” is the name for big binders containing
hard copy describing each of the elements of a dataset, the description for the codebook
command is justifiably terse.
e. The options that can be used with this command. These are explained in much greater
detail than in the listing of the possible options after the syntax. Here, for example, we can
see that the mv option can look to see if there is a pattern in the missing values—something
important for data cleaning and imputation.
f. Examples of command usage. The codebook examples are real examples that step through
using the command on a dataset either shipped with Stata or loadable within Stata from
the Internet.
g. The information the command stores in the returned results. These results are used
primarily by programmers.
For now, either click on Jump To and choose Examples from the drop-down menu or scroll
down to the examples. It is worth going through the examples as given in the help file. Here is a
screenshot of the top of the examples:
Searching help
Search is designed to help you find information about statistics, graphics, data management, and
programming features in Stata, either as part of the official release or as user-written commands.
When entering topics for the search, use appropriate terms from statistics, etc. For example, you could
enter Mann-Whitney. Multiple topic words are allowed, for example, regression residuals.
When you are using Search, use proper English and proper statistical terminology. If you already
know the name of the Stata command and want to go directly to its help file, select Help > Stata
Command... and type the command name. You can also type the command name in the Search field
at the top of the Viewer and press Enter.
Help distinguishes between topics and Stata commands because some names of Stata commands
are also general topic names. For example, logistic is a Stata command. If you choose Stata
Command... and type logistic, you will go right to the help file for the command. But if you
choose Search... and type logistic, you will get search results listing the many Stata commands
that relate to logistic regression.
Remember that you can search for help from within a Viewer window by typing a command in
the command box of the Viewer or by clicking the magnifying glass button to the left of the search
box, selecting the scope of your search, typing the search criteria in the search box, and pressing
Enter.
Help and search commands

As you might expect, the help system is accessible from the Command window. This feature is
especially convenient when you need help on a particular Stata command. Here is a short listing of
the various commands you can use:
• Typing help commandname is equivalent to selecting Help > Stata Command... and typing
commandname. The help file for the command appears in a new Viewer window.
• Typing search topic in the Command window produces the same output as selecting Help >
Search..., choosing Search all, and typing topic. The output appears in a new Viewer window.
• Typing search topic, local in the Command window produces the same output as selecting
Help > Search..., choosing Search documentation and FAQs, and typing topic. The output
appears in the Results window instead of a Viewer.
• Typing search topic, net in the Command window produces the same output as selecting
Help > Search..., choosing Search net resources, and typing topic. The output appears in the
Results window instead of a Viewer.
See [U] 4 Stata’s help and search facilities and [U] 4.8 search: All the details in the User’s
Guide for more information about these command-language versions of the help system. The search
command, in particular, has a few capabilities (such as author searches) that we have not demonstrated
here.
The Stata reference manuals and User’s Guide

All the Stata reference manuals come as PDF files and are included with the software. The manuals
themselves have many cross-references in the form of clickable links, so you can easily read the
documentation in a nonlinear way.
Many of the links in the help files point to the PDF manuals that came with Stata. It is worth
clicking on these links to read the extensive information found in the manuals. The Stata help system,
though extensive, contains only a fraction of the information found in the manuals.
The Stata reference manuals are each arranged like an encyclopedia, alphabetically, and each has
its own index. The User’s Guide also has an index. The Glossary and Index contains a combined
index for the User’s Guide and all the reference manuals. This combined index is a good place to
start when you are looking for information about a command.
Entries have names like collapse, egen, and summarize, which are generally themselves Stata
commands.
Notations such as [R] ci, [R] regress, and [R] ttest in the Search results and help files are references
to the Base Reference Manual. You may also see things like [P] #delimit, which is a reference to the
Programming Reference Manual, and [U] 9 The Break key, which is a reference to the User’s Guide.
For a complete list of manuals and their shorthand notations, see Cross-referencing the documentation,
which immediately follows the table of contents in this manual.
For advice on how to use the reference manuals, see [GSU] 18 Learning more about Stata, or
see [U] 1.2 The User’s Guide and the Reference manuals.
The Stata Journal and the Stata Technical Bulletin

When searching in Stata, you will often see links to the Stata Journal.
The Stata Journal is a printed and electronic journal, published quarterly, containing articles about
statistics, data analysis, teaching methods, and effective use of Stata’s language. The Journal publishes
peer-reviewed papers together with shorter notes and comments, regular columns, tips, book reviews,
and other material of interest to researchers applying statistics in a variety of disciplines. The Journal
is a publication for all Stata users, both novice and experienced, with different levels of expertise in
statistics, research design, data management, graphics, reporting of results, and Stata, in particular.
See http://www.stata-journal.com for more information. There you may browse the archive, subscribe,
order PDF copies of individual articles, and view at no charge copies of articles older than three years.
The predecessor to the Stata Journal was the STB. Even though the STB is no longer published, past is-
sues contain articles and programs that may interest you. See http://www.stata.com/bookstore/stbj.html
for the table of contents of past issues, and see the STB FAQs at
http://www.stata.com/support/faqs/res/stb.html for detailed information on the STB.
Associated with each issue of both the Stata Journal and the STB are the programs and datasets
described therein. These programs and datasets are made available for download and installation over
the Internet, not only to subscribers but to all Stata users. See [R] net and [R] sj for more information.
Because the Stata Journal and the STB have had several articles about meta-analysis, if you select
Help > Search..., choose Search documentation and FAQs, type meta analysis, and scroll down a
bit, you will see some of these references:
SJ-12-4 refers to volume 12, number 4 of the Stata Journal. This is an example of a Stata Journal
article that describes a new user-written command. The command can be downloaded and installed
to extend the abilities of Stata. See Downloading user-written programs in [GSU] 19 Updating and
extending Stata—Internet functionality for more information.
SJ-11-2 refers to volume 11, number 2 of the Stata Journal. This is an example of a Stata Journal
article that updates the mvmeta user-written command.
Clicking on an SJ link, such as SJ 12(4):605--622, will open a browser and take you to the
Stata Journal website, where you can download abstracts and articles. The Stata Journal website
allows all articles older than three years to be downloaded for free.
Links to other sites where you can freely download programs and datasets for Stata can be found
on the Stata website; see http://www.stata.com/links/. See Downloading user-written programs in
[GSU] 19 Updating and extending Stata—Internet functionality for more details on how to install
this software. Also see [R] ssc for information on a convenient interface to resources available from
the Statistical Software Components (SSC) archive.
We recommend that all users subscribe to the Stata Journal. See [U] 3.5 The Stata Journal for
more information.
Stata videos
Stata has a YouTube channel where you can watch short videos explaining specific topics in Stata,
such as running t tests or fitting regression models. The easiest way to see a list of available videos
is to type help videos in the Command window.
5 Opening and saving Stata datasets
How to load your dataset from disk and save it to disk

Opening and saving datasets in Stata works similarly to those tasks in other computer applications.
There are a few differences, however. First, it is possible to save and open files from within Stata’s
Command window. Second, Stata allows just one dataset to be open and in use at any one time. It is
possible to have many Viewers viewing many files, but only one dataset may be in use at any time.
Keeping this in mind will make Stata’s care in opening new datasets clear. This chapter outlines all
the possible ways to open and save datasets.
A Stata dataset can be opened in a variety of ways, most of which are probably familiar to you
from other applications:
• Double-click on a Stata data file, which is a file whose extension is .dta. Note: The file
extension may not be visible, depending on what options you have set in your operating system.
• Select File > Open... or click on the Open button and navigate to the file.
• Select File > Open Recent > filename.
• Type use filename in the Command window. Stata will look for filename in the current working
directory. If the file is located elsewhere, you will need to give its path. Be aware that if there
is a space anywhere in the path or filename, you will need to put the filename inside quotation
marks. See [U] 11.6 Filenaming conventions.
• Type sysuse filename in the Command window. Stata will look for filename in a series of
directories called the adopath. Typically, this is for finding example datasets installed when
you installed Stata, but it can also be used for easy access to your own datasets. For more
information on the adopath, see [P] sysdir.
• Type webuse filename in the Command window. The webuse command is used to access
datasets used in the Stata manuals; for example, webuse lbw loads the lbw dataset used in the
documentation of the logistic command. For more information, see [D] webuse.
Because Stata has at most one dataset open at a time, opening a dataset will cause Stata to discard
the dataset that is currently in memory. If there have been changes to the data in the currently open
dataset, Stata will refuse to discard the dataset unless you force it to do so. If you open the file
with any method other than the Command window, you will be prompted. If you use the Command
window and the current data have changed, you will get the following error message:

. sysuse auto
no; data in memory would be lost
r(4);

These behaviors protect you from mistakenly losing data.
To save an unnamed dataset (or an old dataset under a new name):
1. select File > Save As...; or
2. type save filename in the Command window.
To save a dataset for use with Stata 11 or Stata 12 (Stata 11 can load Stata 12 datasets),
1. select File > Save As..., and select Stata 12 Data (*.dta) from the list of file types; or
2. type saveold filename in the Command window.
42
[ GSU ] 5 Opening and saving Stata datasets 43
To save a dataset that has been changed (overwriting the original data file),
1. select File > Save;
2. click on the Save button; or
3. type save, replace in the Command window.
Once you overwrite a dataset, there is no way to recover your original dataset. With important datasets,
you may want to either keep a backup copy of your original filename.dta or save your changes to
a dataset under a new name. This is no different from working with a word-processing document,
except that recovering from an inadvertent save of a dataset is nearly impossible.
Important note: Changes you have made to a dataset are not permanent until you save them. You
work with a copy of the dataset in memory, not with the data file itself. This should not be surprising,
because it is the way that you work with almost all applications on your computer.
If you do not want to save your dataset, you can clear the dataset in memory and open a new
dataset by typing use filename, clear.
6 Using the Data Editor
The Data Editor in Stata(GUI)

This chapter discusses the Data Editor for Stata(GUI). Stata(console) users should consult [D] input
to learn how to input data interactively.
The Data Editor gives a spreadsheet-like view of data that are currently in memory. You can use
it to enter new data, edit existing data, and edit attributes of the data in the dataset, such as variable
names, labels, and display formats, as well as value labels.
In addition to the view of the data, there are two windows for manipulating variables and their
properties: the Variables window and the Properties window. These are similar to the same-named
windows in the main Stata window.
Any action you take in the Data Editor results in a command being issued to Stata as though
you had typed it into the Command window. This means that you can keep good records and learn
commands by using the Data Editor.
The Data Editor can be kept open while you work in Stata, giving you a live view of your dataset
as you work. To protect your data from inadvertent changes, the Data Editor has two modes: edit
mode for active editing and browse mode for viewing. In browse mode, editing within the Data Editor
window is disabled. We highly recommend that you use the Data Editor in browse mode and switch
to edit mode only when you want to make changes.
We will be entering and editing data in this chapter, as well as manipulating the variables by using
the Variables and Properties windows, so start the Data Editor in edit mode by clicking on the Data
Editor (Edit) button, .
Note: Stata(console) users, see [D] input to learn how to input data interactively.
Buttons on the Data Editor

The toolbar for the Data Editor has some standard buttons and some buttons we have not yet seen:
Open: Opens a Stata dataset. Stata will warn you if your current dataset has unsaved
changes.
Save: Saves the dataset visible in the Data Editor.
Copy: Copies the current selection to the Clipboard.
Paste: Pastes the contents of the Clipboard. You may paste only if one cell is selected—this
cell will become the upper-left corner of the pasted contents. Warning: This action will
paste over existing data.
Edit Mode: Changes the Data Editor to edit mode.
44
[ GSU ] 6 Using the Data Editor 45
Browse Mode: Changes the Data Editor to browse mode for safely looking at data.
Filter Observations: Filters the observations visible in the Data Editor. This button is useful
for looking at a subset of the current dataset.
Variables: Toggles the visibility of the Variables and Properties windows.
Properties: Toggles the visibility of the Properties window.
Snapshots: Opens the Snapshots window. See Working with snapshots below.
You can move about in the Data Editor by using the typical methods:
• To move to the right, use the Tab key or the right arrow key.
• To move to the left, use Shift+Tab or the left arrow key.
• To move down, use Enter or the down arrow key.
• To move up, use Shift+Enter or the up arrow key.
You can also click within a cell to select it.
Right-clicking within the Data Editor brings up a contextual menu that allows you to manipulate
the data and what you are viewing. Right-clicking on the Data Editor window displays a menu from
which you can do many common tasks:
• Copy to copy data to the Clipboard.
• Paste to paste data from the Clipboard.
• Paste Special... to paste data from the Clipboard with finer control of delimiters, giving a
preview of what will be pasted.
• Select All to select all the data displayed in the Data Editor. This could be different from the
data in the dataset if the data are filtered or some variables are hidden.
• Data which opens a submenu containing
• Add Variable at End of Dataset... to bring up a dialog for creating a new variable.
• Replace Contents of Variable... to bring up a dialog for replacing the values of the
selected variable.
• Sort Data... to sort the dataset by the selected variable.
• Value Labels to access a submenu for managing and displaying value labels.
• Keep Only Selected Data to keep only the selected data in the dataset. All remaining
data will be dropped (removed) from the dataset. As always, this affects only the data in
memory. It will not affect any data on disk.
• Drop Selected Data to drop the selected data. This is only possible if the selection
consists of either entire variables (columns) or observations (rows).
• Convert Variables from String to Numeric... for converting string variables to numeric
variables, which is useful when the string variables contain characters for formatting
numbers instead of just numbers.
• Convert Variables from Numeric to String... for converting numeric variables to strings.
• Encode String Variable to Labeled Numeric... for encoding a string-valued categorical
variable to a numeric variable while still displaying the categories in tables and graphs.
• Decode Labeled Numeric Variable to String... for turning an encoded variable back
into a string variable.
• Hide Selected Variables to hide the selected variables.
• Show Only Selected Variables to hide all but the selected variables.
46 [ GSU ] 6 Using the Data Editor
• Show Entire Dataset to turn off all filters and unhide all variables.
• Preferences... to set the preferences for the Data Editor.
Data entry
Entering data into the Data Editor is similar to entering data into a spreadsheet. One major difference
is that the Data Editor has the concept of observations, which makes the data entry smart. We will
illustrate this with an example. It will be useful for you to follow the example at your computer.
To work along, you will need to start with an empty dataset to work along, so save your dataset if
necessary, and then type clear in the Command window.
Note: As a check to see if your data have changed, type describe, short (or d,s for short).
Stata will tell you if your data have changed.
Suppose that we have the following data, and we want to enter them into Stata:
Make Price MPG Weight Gear Ratio

VW Rabbit 4697 25 1930 3.78
Olds 98 8814 21 4060 2.41
Chev. Monza 3667 2750 2.73
AMC Concord 4099 22 2930 3.58
Datsun 510 5079 24 2280 3.54
5189 20 3280 2.93
Datsun 810 8129 21 2750 3.55
We do not know MPG for the third car or the make of the sixth.
Start by opening the Data Editor in edit mode. You can do this either by clicking on the Data
Editor (Edit) button, , or by typing edit in the Command window. You should be greeted by
a Data Editor with no data displayed. (If you see data, type clear in the Command window.) Stata
shows the active cell by highlighting it and displaying varname[obsnum] next to the input box in
the Cursor Location box. We will see below that we can navigate within a dataset by using this cell
reference. The Data Editor starts, by default, in the first row of the first column. Because there are
no data, there are no variable names, and so Stata shows var1[1] as the active cell.
We can enter these data either by working across the rows (observation by observation) or by
working down the columns (variable by variable). To enter the data observation by observation, press
Tab after entering each value until you have reached the end of the first row. In our case, we would
type VW Rabbit, press Tab, type 4697, press Tab, and continue entering data to complete the first
observation.
After you are finished with the first observation, select the second cell in the first column, either
by clicking within it or by navigating to it. At this point, your screen should look like this:
We can now enter the data for the second observation in the same fashion as the first—with one
nice difference: after we enter the last value in the row, pressing the Tab key will bring us to the
first cell in the third row. This is possible because the number of variables is known after the first
observation has been entered, so Stata knows when it has all the data for an observation.
We can enter the rest of the data by pressing the Tab key between entries, simply skipping over
missing values by tabbing through them.
If we had wanted to enter the data variable by variable, we could have done that by pressing
Enter between each make of car until all seven observations were entered, skipping past the missing
entry by pressing Enter twice. Once the first variable was entered, we would select the first cell in
the second column and enter the price data. We would continue this until we were finished.
Notes on data entry

There are several things to note about data entry and the feedback you get from the Data Editor
as you enter data:
• Stata does not allow blank columns or rows in the middle of your dataset.
Whenever you enter new variables or observations, always begin in the first empty column
or row. If you skip columns or rows, Stata will fill in the intervening columns or rows with
missing values.
• Strings and value labels are color coded.
To help distinguish between the different types of variables in the Data Editor, string values
are displayed in red, value labels (see [GSU] 9 Labeling data) are displayed in blue, and all
other values are displayed in black. You can change the colors for strings and value labels by
right-clicking on the Data Editor window and selecting Preferences....
• A period (.) represents Stata’s system missing numeric value.
Stata has a system missing value, ‘.’, and extended missing values ‘.a’ through ‘.z’. By
default, Stata uses its system missing value.
• The Tab key is smart.

As we saw above, after the first observation has been entered, Stata knows how many variables
you have. So at the end of the second observation (and all subsequent observations), Tab will
automatically take you back to the first column.
• The Cursor Location box both shows location and is used for navigation.
The Cursor Location box gives the location of the current cell. If you see, for example, var3[4],
this means that the current cell is the fourth observation of the variable named var3. You can
navigate to a particular cell by typing the variable name and the observation in the Cursor
Location box. If you wanted the second observation of var1 to be the active cell, typing var1 2
in the Cursor Location box and pressing Enter would take you there.
• Double quotes around text are unnecessary in string variables.
Once Stata knows that a variable is a string variable (it holds text), there is no need to put
quotes around the values, even if the values look like a number. Thus, if you wanted to enter
ZIP codes as text, you would enter the first ZIP code with quotes ("02173"), but the rest would
not need any quotes.
• The arrow keys are context sensitive.
If you select a cell and type new data, using an arrow key will accept the change and move to
a new active cell. If you double-click on a cell, you can edit within the cell contents. In this
case, the right- and left-arrow keys move within the cell’s data.
• You can throw away changes to a cell.
If, while you are entering data in a cell, you decide you would like to cancel the changes, press
the Esc key or click outside the cell.
Renaming and formatting variables

The data have now been entered into Stata, but the variable names leave something to be desired:
they have the default names var1, var2, . . . , var5. We would like to rename the variables so that
they match the column titles from our dataset. We would also like to give the variables descriptions
and change their formatting.
We will step through changing the name, label, and format of the price variable. We will then
add a note to the variable. Start by clicking on the var2 variable in the Variables window. The few
properties associated with var2 are now visible and editable in the Properties window. We may now
systematically change the properties of var2 to our choosing:
1. Double-click on var2 in the Name field to select the old variable name, and type price to
overwrite the name.
2. Click under the new price name in the Label field.
3. Enter a worthwhile label, such as Price in Dollars.
4. Click on the ellipses (. . .) button next to the Format field. The Create Format dialog opens.
5. You can see here that there are many possible formats, most of which are related to time. We
want commas in our numbers, so check the Use commas in numeric output checkbox. When
you are done, click on the OK button.
6. Click on the ellipses (. . . ) button next to the Notes field. A dialog called Notes for price opens.
7. Click on the Add button and type a clever note.
8. When you are done typing, click on the Submit button, and then click on the Close button.
This note is now attached to the price variable.
To edit the properties of another variable, click on the variable in the Variables window. We can name
the first variable make; the third, mpg; the fourth, weight; and the fifth, gear ratio. Just before
you rename var5 to gear ratio, your screen should look like this:
You need to know some rules for variable names:

• Stata is case sensitive.
Make, make, and MAKE are all different names to Stata. If you had named your variables Make,
Price, MPG, etc., then you would have to type them correctly capitalized in the future. Using
all lowercase letters is easier.
• A variable name must be 1–32 characters long.
• The characters can be letters (A–Z, a–z), digits (0–9), or underscores ( ).
• Spaces or other characters are not allowed.
• The first character of a variable name must be a letter or an underscore.
Although you can use an underscore to begin a variable name, it is highly discouraged. Such
names are used for temporary variable names in Stata. You would like your data to be permanent,
so using a temporary name could lead to great frustration.
For more information about variable names and value labels, see [GSU] 9 Labeling data; for display
formats, see [U] 12.5 Formats: Controlling how data are displayed.
Copying and pasting data

You can copy and paste data by using the Data Editor. This is often a simple way to bring data
into Stata from any other applications such as spreadsheets or databases.
1. Select the data that you wish to copy by using one of these means:
• Click once on a variable name or column heading to select an entire column.
• Click once on an observation number or row heading to select the entire row.
• Click and drag the mouse to select a range of cells.
2. Copy the data to the Clipboard by right-clicking within the selected range, and select Copy.
3. Paste the data from the Clipboard by clicking on the top left cell of the area to which you wish
to paste. Then right-click on the same cell, and select Paste.
We will illustrate copying and pasting an observation by making a copy of the first observation
and pasting it at the end of the dataset.
Start by clicking on the observation number of the first observation. Doing so highlights all the
data in the row. Right-click on the same location (there is no need to move the mouse), and select
Copy:
Click on the first cell in the eighth row, right-click while you are still in that cell, and choose
Paste from the resulting menu. You can see that the observation was successfully duplicated.
Notes on copying and pasting

• The above example illustrated copying and pasting within the Data Editor. You can use roughly
the same technique to copy and paste between other applications and Stata and between Stata
and other applications. The easiest way to see if copying and pasting works properly with
another application is to try it. The one requirement for things to work well is that the external
application must copy tables in some delimited form, as do spreadsheet applications, many
database applications, and some word processors. Using Edit > Paste Special... gives some
added flexibility to the formats you can paste into the Data Editor. If a simple paste does not
give you what you expected, you should try Edit > Paste Special.... For more information on
file-based methods for importing data into Stata, see [GSU] 8 Importing data.
• If you are copying and pasting data with value labels, you have a choice. You can copy variables
with value labels as text, using the value labels as the actual values, or you can copy said
variables as their underlying encoded numbers. Copying with the value labels is the default. If
you would like the other choice, right-click in the Data Editor and select Data > Value Labels
> Hide All Value Labels, or select Tools > Value Labels > Hide All Value Labels.
Changing data
As its name suggests, the Data Editor can be used to edit your dataset. As we have seen already, it
can be used to edit the data themselves as well as the description and display options for the variables.
Here is an example for making some changes to the auto dataset, which illustrates both methods
for using the Data Editor and its documentation trail. We will also keep snapshots of the dataset as
we are working so that we can revert to previous versions of the dataset in case we make a mistake.
We would like to investigate the dataset, work with value labels, delete the trunk variable, and
make a new variable showing gas consumption per 100 miles. These tasks will illustrate the basics
of working in the Data Editor.
Start by typing sysuse auto into the Command window. If you worked the previous example,
you will get an error and are told that data in memory would be lost. This is good—Stata is keeping
you from inadvertently throwing away the unsaved changes to your current data as it loads the auto
dataset. If you would like to save the dataset you have been working on, select File > Save and save
the dataset in an appropriate location. Otherwise, type clear in the Command window, and press
Enter to clear out the data, and then load that auto data.
Once the auto dataset is loaded, start the Data Editor.

1. We would like to see which cars have the lowest and highest gas mileages. To do this, right-click
on the column heading of the mpg column. Select Data > Sort Data... from the contextual
menu. A dialog will pop up asking how you want to sort, defaulting to sorting in ascending
order. Click on OK. (Stata worries about sort order because sort order can affect reproducibility
when using resampling techniques. This is a good thing.) You will see that the data have now
been sorted by mpg in ascending order. The lowest-mileage cars are at the top of the screen;
by scrolling to the bottom of the dataset, you can find the highest-mileage cars. You also could
have sorted by selecting Tools > Sort Data... once the mpg variable was selected.
2. We would like to investigate repair records and hence sort by the rep78 variable. (Do this
now.) We see that the Starfire and Firebird both had poor repair records, but we would like to
see the cars with good repair records. We could scroll to the bottom of the dataset, but it will
be faster to use the Cursor Location box: type rep78 74 and press Enter to make rep78[74]
the active cell. We notice that the last five entries for rep78 appear as dots. The dots mean
that these values are missing. A few items of note:
• As we can see from the result of the sort, Stata views missing values as being larger
than all numeric nonmissing values. In technical terms, this means that rep78 >= . is
equivalent to missing(rep78).
• What we do not see here is that Stata has multiple missing-value indicators: . is Stata’s
default or system missing-value indicator, and .a, .b, . . . , .z are Stata’s extended
missing values. Extended missing values are useful for indicating the reason why a value
is unknown.
• The different missing values sort among themselves: . < .a < .b < · · · < .z. See
[U] 12.2.1 Missing values for full details.
3. We would like to make the repair records readable. Click on rep78 in the Variables window.
4. Click on the ellipses (. . . ) button next to the Value Label field in the Properties window. This
opens the Manage Value Labels dialog. We need to define a new value label for the repair
records.
a. Click on the Create Label button. You will see the Create Label dialog.
b. Type a name for the label, say, repairs, in the Label name box.
c. Press the Tab key or click within the Value field.
d. Type 1 for the value, press the Tab key, and type atrocious for the label.
e. Press the Enter key to create the pairing.
f. Repeat steps d and e to make all the pairings: 2 with “bad”, 3 with “OK”, 4 with “good”,
and 5 with “stupendous”.
g. Click on the OK button to finish creating the value label.
h. Click on the disclosure control, , to show the label—you should see this:
If you have something else, you can edit the label by clicking on the Edit Label button.
i. Click on the Close button to close the Manage Value Labels dialog.
Now that the label has been created, attach it to the rep78 variable by clicking on the down
arrow in the Value Label field and selecting the repairs label. You can now see the labels
displayed in place of the values.
5. Suppose that we found the original source of the data in a time capsule, so we could replace
some of the missing values for rep78. We could type the values into cells. We can also assign
the values by right-clicking within a cell with a missing value and choosing a value from Data
> Value Labels > Assign Value from Value Label ‘repairs’. This strategy can be useful when
a value label has many possible values.
6. We would now like to delete the trunk variable. We can do this by right-clicking on the trunk
variable name at the top of the column and selecting the Data > Drop Selected Data menu
item. Because this can lead to data loss, the Data Editor asks whether we would like to drop
the selected variable. Click on the Yes button.
7. To finish up, we would like to create a variable containing the gallons of gasoline per 100
miles driven for each of the cars.
a. Right-click within any cell, and choose the Data > Add Variable at End of Dataset...
menu item to bring up the generate dialog.
b. Type gp100m in the Variable name field.
c. Being sure that the Specify a value or an expression radio button is selected, type 100/mpg
in its field. We could have clicked on the Create... button to open the Expression builder
dialog, but this formula was simple enough to type. (You might want to explore the
Expression builder right now to see what it can do.)
d. Click on OK. You can scroll to the right to see the newly created variable.
Throughout this data editing session, we have been using the Data Editor to manipulate the data.
If you look in the Results window, you will see the commands and their output. You can also see all
the commands generated by the Data Editor in the Review window. If you wanted to save the editing
commands to use again later, you could do the following steps:
1. Click in the Review window on the last command that came from the Data Editor.
2. Scroll up until you find the sort mpg command you ran immediately after opening the Data
Editor, and Shift-click on it.
3. Right-click on one of the highlighted commands.
4. Select Send to Do-file Editor.

This procedure will save all the commands you highlighted into the Do-file Editor. You could then
save them as a do-file, which you could run again later. We will talk more about the Do-file Editor
in [GSU] 13 Using the Do-file Editor—automating Stata. You can find help about do-files in
[U] 16 Do-files.
If you want to save this dataset, save it under a new name by using File > Save As... in the main
Stata window to prevent overwriting the original dataset.
Working with snapshots

The Data Editor allows you to save to disk snapshots of whatever dataset you are working on.
These are temporary copies of the dataset—they will be deleted when you exit Stata, so they need
to be treated as temporary. Still, there are many uses for snapshots, such as
• saving a temporary copy of the data in memory so that another dataset can be opened and
viewed;
• saving stages of work, which can be recovered in case you do something disastrous; and
• saving pieces of datasets while doing analyses.
We will keep using the auto dataset from above; if you are starting here, you can start fresh by
typing sysuse auto in the Command window to open the dataset. (If you get a warning about data
in memory being lost, either use clear or save your data. See [GSU] 5 Opening and saving Stata
datasets for more information.) If we open the Data Editor and click on View > Snapshots..., we see
the following window. If you are starting afresh, you will see numbers rather than labels for rep78.
To begin with, only one button is active in the Snapshots toolbar. Click on the active button—the
Add button, . It brings up a dialog asking for a label, or name, for the snapshot. Give it an
inventive name, such as Start, and press Enter. You can see that a snapshot is now listed in the
Snapshots window, and all the buttons in the toolbar are now active. The following buttons appear
in the Snapshots window:
Add: Save a new snapshot with a timestamp and label.
Remove: Erase a snapshot. This action deletes the temporary snapshot file but does not
affect the data in memory.
Change Label: Edit the label of the selected (highlighted) snapshot.
Restore: Replace the data in memory with the data from the selected snapshot. You will
get a dialog asking you to confirm your action.
You should now try manipulating the dataset by using the tools we have seen. Once you have
done that, create another snapshot, calling it Changed. Open the Snapshots window and restore the
Start snapshot by either double-clicking it or clicking first on it and then on the Restore button to
see where you started. You can then go back to where you were working by restoring your Changed
snapshot.
Snapshots continue to be available either until they are deleted or until you exit Stata. You can thus
use snapshots of one dataset while working on another. You will find your own uses for snapshots—just
take care to save the datasets you want for future use because the snapshots are temporary.
Dates and the Data Editor

The Data Editor has two special tools for working with dates in Stata. To see these in action, we
will need to open another dataset. Either save your dataset or clear it out, and then type sysuse
sp500 in the Command window. Look in the Data Editor to see what you have.
You can see a date variable that has January 2, 2001, as its first day, though it is being displayed
in Stata’s default format for dates.
We will start with formatting:
1. Select the date variable in the Variables window to the right of the data table.
2. In the Properties window, click on the ellipses button to the right of the Format field.
3. The Create Format dialog tells us three pieces of information about the date format:
• These are daily dates. As you can see, Stata understands other types of dates that are
often used in financial data.
• Looking at the bottom of the dialog, you can see that Stata’s default date format is %td.
This means that the variable contains time values that are to be interpreted as daily dates.
• This default format is displayed as, for example, 07apr2009.
4. There are many premade date formats in the pane at the top right of the Create Format dialog.
Click on April 07, 2009. You can see how the format would be specified at the bottom of
the dialog.
5. Click on OK to close the Create Format dialog. You can see that the dates are now displayed
differently.
This is a very simple way to change date formats. For complete information on dates and date formats,
see [D] datetime.
We will now change some of the dates to illustrate how this can be done simply, regardless of
the format in which the dates are displayed. If you look in the upper-right corner of the Data Editor,
you will see the date mask field, which shows DMY. This field affects how dates are entered when
editing data.
By default, the date mask is set to DMY. This means dates can be entered in many different fashions,
as long as the order of the day, month, year is day, month, year. Try the following:
1. Click in the first observation of date so that the Cursor Location shows date[1].
2. Type 18jan2011 and press the Enter key. Stata understands the DMY date mask and knows
enough to enter the new date in the selected cell.
3. Enter 30042012 and press Enter. Stata still understands the date mask, even though there are
no separators.
4. Click within the date mask field, and choose MDY from the drop-down menu.
5. Click on any observation in the date column.
6. Type March 15, 2013 and press Enter. Stata will still understand.
Working in this fashion is the fastest way to edit dates by hand. If you look in the Results window,
you will see why.
We are now finished with this dataset, so type clear and press Enter.
Data Editor advice

As you could see above, a small mistake in the Data Editor could cause large problems in your
dataset. You really must take care in how you edit your data.
• People who care about data integrity know that editors are dangerous—it is easy to accidentally
make changes. Never use the Data Editor in edit mode when you just want to look at your
data. Use the Data Editor in browse mode (or use the browse command).
• If you must edit your data, protect yourself by limiting the dataset’s exposure. For example, if
you need to change rep78 only if it is missing, find a way to look at just the missing values
for rep78 and any other variables needed to make the change. This will make it impossible for
you to change (damage) variables or observations other than those you view. We will explore
this aspect shortly.
• Even with these caveats, Stata’s Data Editor is safer than most because it records commands in
the Results window. Use this feature to log your output and make a permanent record of the
changes. Then you can verify that the changes you made are the changes you wanted to make.
See [GSU] 16 Saving and printing results by using logs for information on creating log files.
Filtering and hiding

We would now like to investigate restricting our view of the data we see in the editor. This feature
is useful for the reasons mentioned above, and as we will see, it helps if we would like to browse
through the data of a large dataset. In any case, we would like to focus on some data, not all the data,
whether we focus on some of the variables, some of the observations, or even just some observations
within some variables. We would also like to change the order of the variables. We will show you
how this is done by using both the graphical interface and commands.
Open the auto dataset by typing sysuse auto. If you get an error message, type clear and try
again. Once you have done that, open the Data Editor.
Suppose that we would like to edit only those observations for which rep78 is missing. We will
need to look at the make of the car so that we know which observations we are working with, but
we do not need to see any other variables. We will work as though we had a very large dataset to
work with.
1. Before we get started, try experimenting with the Variables window.
a. Drag variables up and down the list. Doing so changes the order of the variables’ columns
in the Data Editor. It does not change their order in the dataset itself.
b. Uncheck some of the checkboxes in the first column to hide some of the variables.
c. Type a search criterion in the Filter variables here field. Just like in the Variables window
in the main Stata window, the default is to ignore case and find any variables or variable
labels containing any of the words in the filter. Clicking on the arrow under the magnifying
glass will allow you to change this behavior as well as to add or remove additional columns
containing information about the variables. The filtering of variables in the list affects
what is displayed in the Variables window; it does not affect what variables’ data are
displayed. When you are done, delete your filter text.
2. Right-click on any variable in the Variables window, and select Select All from the contextual
menu.
3. Click on any checkbox to deselect all the variables.
4. Click on the make variable to select it, and deselect all the other variables.
5. Click on the checkbox for make.
6. Click on the checkbox for rep78.
If you look in the Command window, you can see that no commands have been issued, because
hiding the variables does not affect the dataset—it affects only what shows in the Data Editor.
We now have protected ourselves by using only those variables that we need. We should now
reduce our view to only those observations for which rep78 is missing. This is simple.
Click on the Filter Observations button,
1. , in the Data Editor’s toolbar.
2.
Enter missing(rep78) in the Filter by expression field.
Click on the Apply Filter button.
3.
4.
If you are curious, click on the ellipses button. It opens up an Expression builder dialog. This
lists the wide variety of functions available in Stata. See [D] functions.
Now we are focused on the part of the dataset in which we would like to work, and we cannot
destroy or mistakenly alter other data by stray keystrokes in the Data Editor window.
It is worth learning how to hide variables and filter observations in the Data Editor from the
Command window. This can be quite convenient if you are going to restrict your view, as we did
above. To work from the Command window, we must use the edit command together with a varlist
(variable list) along with if and in qualifiers in the Command window. By using a varlist, we
restrict the variables we look at, whereas the if and in qualifiers restrict the observations we see.
([GSU] 10 Listing data and basic command syntax contains many examples of using a command
with a variable list and if and in.) Suppose we want to correct the missing values for rep78. The
minimum amount of data we need to expose are make and rep78. To see this minimal amount of
information and hence to minimize our exposure to making mistakes, we enter the commands

. sysuse auto
. edit make rep78 if missing(rep78)

and we would see the following window:
Once again, we are safe and sound.

Keep this lesson in mind if you edit your data. It is a lesson well learned.
Browse mode
The purpose of using the Data Editor in browse mode is to look at data without altering them by stray
keystrokes. You can start the Data Editor in browse mode by clicking on the Data Editor (Browse)
button, , or by typing browse in the Command window. When you work in browse mode, all
contextual menu items that would let you alter the data, the labels, or any of the display formats
for the variables are disabled. You may view a variable’s properties with the Variable Properties...
menu item, but you may not make any changes. You still can filter observations and hide variables
to get a restricted view because these actions do not change the dataset.
Note: Because you can still use Stata menus not related to the Data Editor and because you can
still type commands in the Commands window, it is possible to change the data even if the Data
Editor is in browse mode. In fact, this means you can watch how your commands affect the dataset.
You are merely restricted from using the Data Editor itself to change the data.
7 Using the Variables Manager
The Variables Manager in Stata(GUI)

This chapter discusses the Variables Manager for Stata(GUI). Stata(console) users should consult
the Data Management Reference Manual for details concerning the commands issued by the Variables
Manager. You open the Variables Manager by selecting Data > Variables Manager or clicking on
the Variables Manager button .
The Variables Manager is a tool for managing properties of variables both individually and in
groups. It can be used to create variable and value labels, rename variables, change display formats,
and manage notes. It has the ability to filter and group variables as well as to create variable lists.
Users will find these features useful for managing large datasets.
Any action you take in the Variables Manager results in a command being issued to Stata as
though you had typed it in the Command window. This means that you can keep good records and
learn commands by using the Variables Manager.
The Variable pane

The left pane of the Variables Manager is called the Variable pane, though it has no explicit title
on the screen. It shows the list of variables in the dataset. This list can be manipulated in a variety
of ways.
• The variables can be filtered by entering text into the filter box in the upper-left corner. This
can be a good way to zoom in on similarly named or labeled variables.
• The list can be sorted by clicking on the column title.
a. If you click on a column title, it will sort in ascending order.
b. A second click on the same column title will change to sorting in descending order.
58
[ GSU ] 7 Using the Variables Manager 59
c. To restore the list to the original sort order, right-click within the variable list, and select
Show Variables in Dataset Order.
The sort order affects only how the data appear in the Variable Managers window—the dataset
itself stays the same.
Right-clicking on the Variable pane

Right-clicking on the Variable pane displays a menu from which you can do many common tasks:
• Keep Only Selected Variables to keep only the selected variables in the dataset and to drop
all the others.
• Drop Selected Variables to drop all the selected variables from the dataset.
• Manage Notes for Selected Variable... to open a window that allows adding and deleting notes
for a single variable. This is disabled if multiple variables are selected.
• Manage Notes for Dataset... to open a window that allows adding and deleting notes for the
dataset as a whole.
• Copy Varlist to copy the names of the selected variables to the Clipboard.
• Select All to select all visible variables. If a variable has become hidden because of the filter,
it will not be selected.
• Send Varlist to Command Window to insert the names of the selected variables in the Command
window. Combined with grouping and sorting, this can be a useful way to create variable lists
in large datasets.
The Variable Properties pane

The Variable Properties pane can be used to manipulate the properties of variables selected in the
Variable pane. With one variable selected, you can manipulate all properties of the variable. With
many variables selected, you can change their formats or types as well as assign value labels all at
once. These fields work in the same fashion as those shown in Renaming and formatting variables in
[GSU] 6 Using the Data Editor. We can also manage the notes Stata allows you to attach to variables
and the dataset—we will show an example below.
Managing notes
Stata allows you to attach notes to both variables and the dataset as a whole. These are simple
text notes that you can use to document whatever you like—the source of the dataset, data collection
quirks associated with a variable, what you need to investigate about a variable, or anything else.
Start by selecting a variable in the Variable pane. We will work with the price variable. Click
on the Manage... button next to the Notes field, and you will see the following dialog appear:
60 [ GSU ] 7 Using the Variables Manager
We will add a few notes:

1. Click on the Add button to add a note.
2. Type TS - started working. TS with a trailing space inserts a timestamp in the note.
3. Add two more notes. We added two notes about prices:
It is worth experimenting with adding, deleting, and editing notes. Notes can be an invaluable
memory aid when working on projects that last a long time. Anytime you manipulate notes in the
Notes Manager, you create Stata commands.
8 Importing data
Copying and pasting in Stata(GUI)

One of the easiest ways to get data into Stata is often overlooked: you can copy data from most
applications that understand the concept of a table and then paste the data into the Data Editor. This
approach works for all spreadsheet applications, many database applications, some word-processing
applications, and even some webpages. Just copy the full range of data, paste it into the Data Editor,
and everything will probably work well. You can even copy a text file that has the pieces of data
separated by commas and then paste it into the Data Editor.
Suppose that your friend has a small dataset about some very old cars.
VW Rabbit,4697,25,1930,3.78
Olds 98,8814,21,4060,2.41
Chev. Monza,3667,,2750,2.73
,4099,22,2930,3.58
Datsun 510,5079,24,2280,3.54
Buick Regal,5189,20,3280,2.93
Datsun 810,8129,,2750,3.55
You would like to put these data into Stata. Doing so is easier than you think:
1. Clear out your current dataset by typing clear.
2. Copy the data from the PDF documentation the way you would copy anything from any document.
(For best results, use Adobe Reader.)
3. Open the Data Editor in edit mode.
4. Select Edit > Paste Special....
5. Stata sees that the column delimiters are commas and shows how the data would look.
6. Click on the OK button.
You can see that Stata has imported the data nicely.
Later in this chapter, we would like to bring these data into Stata without copying and pasting, so
we would like to save them as a text file. Go back to the main Stata window, and click on the Do-file
Editor button, , to open a new Do-file Editor window. Paste the data in the Do-file Editor, then
click on the Save button. Navigate to your working directory, and save the file as a few cars.csv.
If you do not know what your working directory is, look in the status bar at the bottom of the main
Stata window.
Be careful if you are copying data from a spreadsheet because spreadsheets can contain special
formatting that ruins its rectangular form. Be sure that your spreadsheet does not contain blank rows,
blank columns, repeated headers, or merged cells because these can cause trouble. As long as your
spreadsheet looks like a table, you will be fine.
Commands for importing data

Copying and pasting is a great way to bring data into Stata, but if you need a clear audit trail for
your data, you will need another way to bring data into Stata. The rest of this chapter will explain
how to do this. You will also learn methods that lend themselves better to repetitive tasks and methods
for importing data from a wide variety of sources.
61
62 [ GSU ] 8 Importing data
Stata has various commands for importing data. The three main commands for reading non–Stata
datasets in plain text (ASCII) are
• import delimited, which is made for reading text files created by spreadsheet or database
programs or, more generally, for reading text files with clearly defined column delimiters such
as commas, tabs, semicolons, or spaces;
• infile, which is made for reading simple data that are separated by spaces or rigidly formatted
data aligned in columns; and
• infix, which is made for data aligned in columns but possibly split across rows.
Stata has other commands that can read other types of files and can even get data from external
databases without the need for an interim file:
• The import excel command can read Microsoft Excel files directly, either as an .xls or as
an .xlsx file.
• The import sasxport command can read any SAS XPORT file, so data can be transferred from
SAS to Stata in this fashion.
• The odbc command can be used to pull data directly from any data sources for which you
have ODBC (Open Database Connectivity) drivers.
• The xmluse command can read some XML (Extensible Markup Language) files (most notably,
Microsoft Excel’s SpreadsheetML).
Each command expects the file that it is reading to be in a specific format. This chapter will
explain some of those formats and give some examples. For the full description, consult the Data
Management Reference Manual.
The import delimited command

The import delimited command was specially developed to read in text (ASCII) files that were
created by spreadsheet or database programs because these are common formats for sharing datasets
on the Internet. All spreadsheet programs and most database applications have an option to save the
dataset as a text (ASCII) file with the columns delimited with either tab characters or commas. Some
of these programs also save the column titles (variable names, in Stata) in the text file.
To read in such a file, you have only to type import delimited filename, where filename is the
name of the text file. The import delimited command will figure out what the delimiter character
is (tab or comma) and what type of data is in each column. As always, if filename contains spaces,
put double quotes around the filename, and include the path if filename is not in the current working
directory.
By default, the import delimited command understands files that use the tab or comma as the
column delimiter automatically. If you have a file that uses another character as the delimiter, use
import delimited’s delimiters() option.
Earlier in this chapter, you saved a file called a few cars.csv in Copying and pasting in
Stata(GUI). These data correspond to the make, price, MPG, weight, and gear ratio of a few very old
cars. The variable names are not in the file (so import delimited will assign its own names), and
the fields are separated by commas. Clear out any existing data, then use import delimited to read
the data in this file. Because there are spaces in the filename, it must be enclosed in double quotes.

. clear
. import delimited "a few cars.csv"

[ GSU ] 8 Importing data 63
You can look at the data in the Data Editor, and it will look just like the earlier result from copying
and pasting. We will now list the data so that we can see them in the manual. The separator(0)
option suppresses the horizontal separator line that is drawn after every fifth observation by default.

. list, separator(0)
v1 v2 v3 v4 v5
1. VW Rabbit 4697 25 1930 3.78

2. Olds 98 8814 21 4060 2.41
3. Chev. Monza 3667 . 2750 2.73
4. 4099 22 2930 3.58
5. Datsun 510 5079 24 2280 3.54
6. Buick Regal 5189 20 3280 2.93
7. Datsun 810 8129 . 2750 3.55

If you want to specify better variable names, you can include the desired names in the command.
When you specify variable names, you must also use the using keyword before the file name.

. import delimited make price mpg weight gear_ratio using "a few cars.csv"
make price mpg weight gear_r~o
1. VW Rabbit 4697 25 1930 3.78

2. Olds 98 8814 21 4060 2.41
3. Chev. Monza 3667 . 2750 2.73
4. 4099 22 2930 3.58
5. Datsun 510 5079 24 2280 3.54
6. Buick Regal 5189 20 3280 2.93
7. Datsun 810 8129 . 2750 3.55

As a side note about displaying data, Stata listed gear ratio as gear r~o in the output from
list. gear r~o is a unique abbreviation for the variable gear ratio. Stata displays the abbreviated
variable name when variable names are longer than eight characters.
To prevent Stata from abbreviating gear ratio, you could specify the abbreviate(10) option:

. list, separator(0) abbreviate(10)
make price mpg weight gear_ratio
1. VW Rabbit 4697 25 1930 3.78

2. Olds 98 8814 21 4060 2.41
3. Chev. Monza 3667 . 2750 2.73
4. 4099 22 2930 3.58
5. Datsun 510 5079 24 2280 3.54
6. Buick Regal 5189 20 3280 2.93
7. Datsun 810 8129 . 2750 3.55

64 [ GSU ] 8 Importing data
For more information on the ~ abbreviation and on list, see [GSU] 10 Listing data and basic
command syntax.
We will use this dataset again in the next chapter, so we would like to save it. Type save afewcars,
and press Enter in the Command window to save the dataset.
For this simple example, you could have copied the contents of the file and pasted it into the Data
Editor by using Paste Special... and choosing comma as the delimiter.
For text files that have no nice delimiters or for which observations could be spread out across
many lines, Stata has two more commands: infile and infix. See [D] import for more information
about how to read in such files.
Importing files from other software

Stata has some more specialized methods for reading data that were created by other applications
and stored in their proprietary formats.
The import excel command is made for reading files created by Microsoft Excel. See import
excel in [D] import excel for full details.
The import sasxport command can read and create SAS XPORT Transport files. See [D] import
sasxport for full details.
If you have software that supports ODBC, you can read data by using the odbc command without
the need to create interim files. See [D] odbc for full details. The FAQ for setting up ODBC is also
helpful; read it at http://www.stata.com/support/faqs/data/odbcmu.html.
If you would like to move data by using XML, Stata has the xmluse and xmlsave commands
available. See xmluse and xmlsave in [D] xmlsave for full details.
Here is a brief summary of the choices:
• If you have a table, you could try copying it and pasting it into the Data Editor.
• If you have a Microsoft Excel .xls or .xlsx file, use import excel.
• If you have a file exported from a spreadsheet or database application to a tab-delimited or CSV
file, use import delimited.
• If you have a fixed-format file, either use infile with a dictionary or use infix.
• If you have a SAS XPORT file, use import sasxport.
• If you have a database accessible with ODBC, use odbc.
• If you have an XML file, use xmluse.
• Finally, you can purchase a transfer program that will convert the other software’s data file
format to Stata’s data file format. See [U] 21.4 Transfer programs.
9 Labeling data
Making data readable

This chapter discusses, in brief, labeling of the dataset, variables, and values. Such labeling is critical
to careful use of data. Labeling variables with descriptive names clarifies their meanings. Labeling
values of numerical categorical variables ensures that the real-world meanings of the encodings are
not forgotten. These points are crucial when sharing data with others, including your future self.
Labels are also used in the output of most Stata commands, so proper labeling of the dataset will
produce much more readable results. We will work through an example of properly labeling a dataset,
its variables, and the values of one encoded variable.
The dataset structure: The describe command

At the end of The import delimited command in [GSU] 8 Importing data, we saved a dataset
called afewcars.dta. We will put this dataset into a shape that a colleague would understand. Let’s
see what it contains.

. use afewcars
make price mpg weight gear_r~o
1. VW Rabbit 4697 25 1930 3.78

2. Olds 98 8814 21 4060 2.41
3. Chev. Monza 3667 . 2750 2.73
4. 4099 22 2930 3.58
5. Datsun 510 5079 24 2280 3.54
6. Buick Regal 5189 20 3280 2.93
7. Datsun 810 8129 . 2750 3.55

The data allow us to make some guesses at the values in the dataset, but, for example, we do not
know the units in which the price or weight is measured, and the term “mpg” could be confusing for
people outside the United States. Perhaps we can learn something from the description of the dataset.
Stata has the aptly named describe command for this purpose (as we saw in [GSU] 1 Introducing
Stata—sample session).
65
66 [ GSU ] 9 Labeling data

. describe
Contains data from afewcars.dta
obs: 7
vars: 5 4 Feb 2013 23:36
size: 238

make str18 %18s

price float %9.0g
mpg float %9.0g
weight float %9.0g
gear_ratio float %9.0g
Sorted by:

Though there is precious little information that could help us as a researcher, we can glean some
information here about how Stata thinks of the data from the first three columns of the output.
1. The variable name is the name we use to tell Stata about a variable.
2. The storage type (otherwise known as the data type) is the way in which Stata stores the data in
a variable. There are six different storage types, each having its own memory requirement:
a. For integers:
byte for integers between −127 and 100 (using 1 byte of memory per observation)
int for integers between −32,767 and 32,740 (using 2 bytes of memory per observation)
long for integers between −2,147,483,647 and 2,147,483,620 (using 4 bytes of memory
per observation)
b. For real numbers:
float for real numbers with 8.5 digits of precision (using 4 bytes of memory per
observation)
double for real numbers with 16.5 digits of precision (using 8 bytes of memory per
observation)
c. For strings (text) between 1 and 2,045 characters (using 1 byte of memory per observation per
character):
str1 for one-character-long strings
str2 for two-character-long strings
str3 for three-character-long strings
...
str2045 for 2,045-character-long strings
d. Stata also has a strL storage type for strings of arbitrary length up to 2,000,000,000 characters.
strLs can also hold binary data, often referred to as BLOBs, or binary large objects, in databases.
We will not illustrate these here.
Storage types affect both the precision of computations and the size of datasets. A quick guide to
storage types is available at help datatypes or in [D] data types.
3. The display format controls how the variable is displayed; see [U] 12.5 Formats: Controlling
how data are displayed. By default, Stata sets it to something reasonable given the storage type.
We would like to make this dataset into something containing all the information we need.
[ GSU ] 9 Labeling data 67
To see what a well-labeled dataset looks like, we can look at a dataset stored at the Stata Press
repository. We need not load the data (and disturb what we are doing); we do not even need a copy of the
dataset on our machine. (You will learn more about Stata’s Internet capabilities in [GSU] 19 Updating
and extending Stata—Internet functionality.) All we need to do is direct describe to look at the
proper file by using the command describe using filename.

. describe using http://www.stata-press.com/data/r13/auto
Contains data 1978 Automobile Data
obs: 74 13 Apr 2013 17:45
vars: 12
size: 3,478

make str18 %-18s Make and Model

price int %8.0gc Price
mpg int %8.0g Mileage (mpg)
rep78 int %8.0g Repair Record 1978
headroom float %6.1f Headroom (in.)
trunk int %8.0g Trunk space (cu. ft.)
weight int %8.0gc Weight (lbs.)
length int %8.0g Length (in.)
turn int %8.0g Turn Circle (ft.)
displacement int %8.0g Displacement (cu. in.)
gear_ratio float %6.2f Gear Ratio
foreign byte %8.0g origin Car type
Sorted by: foreign

This output is much more informative. There are three locations where labels are attached that help
explain what the dataset contains:
1. In the first line, 1978 Automobile Data is the data label. It gives information about the contents
of the dataset. Data can be labeled by selecting Data > Data utilities > Label utilities > Label
dataset, or by using the label data command.
2. There is a variable label attached to each variable. Variable labels are how we would refer to
the variable in normal, everyday conversation. Here they also contain information about the units
of the variables. Variables can be labeled by selecting the variable in the Variables window and
editing the Label field in the Properties window. When doing this in the main window, be sure that
the Properties window is unlocked. You can also change a variable label by using the Variables
Manager or by using the label variable command.
3. The foreign variable has an attached value label. Value labels allow numeric variables such
as foreign to have words associated with numeric codes. The describe output tells you that
the numeric variable foreign has value label origin associated with it. Although not revealed
by describe, the variable foreign takes on the values 0 and 1, and the value label origin
associates 0 with Domestic and 1 with Foreign. If you browse the data (see [GSU] 6 Using the
Data Editor), foreign appears to contain the values “Domestic” and “Foreign”. The values in a
variable are labeled in two stages. The value label must first be defined. This can be done in the
Data Editor, or in the Variables Manager, or by selecting Data > Data utilities > Label utilities
> Manage value labels or by typing the label define command. After the labels have been
defined, they must be attached to the proper variables, either by selecting Data > Data utilities
> Label utilities > Assign value label to variables or by using the label values command.
Note: It is not necessary for the value label to have a name different from that of the variable.
You could just as easily have used a value label named foreign.
Labeling datasets and variables

We will now load the afewcars.dta dataset and give it proper labels. We will do this with
the Command window to illustrate that it is simple to do in this fashion. Earlier in Renaming and
formatting variables in [GSU] 6 Using the Data Editor, we used the Data Editor to achieve a similar
purpose. If you use the Data Editor for the material here, you will end up with the same commands
in your log; we would like to illustrate a way to work directly with commands.

. use afewcars
. describe
obs: 7
vars: 5 4 Feb 2013 23:36
size: 238

make str18 %18s

price float %9.0g
mpg float %9.0g
weight float %9.0g
gear_ratio float %9.0g
Sorted by:
. label data "A few 1978 cars"
. label variable make "Make and Model"
. label variable price "Price (USD)"
. label variable mpg "Mileage (mile per gallon)"
. label variable weight "Vehicle weight (lbs.)"
. label variable gear_ratio "Gear Ratio"
. describe
obs: 7 A few 1978 cars
vars: 5 4 Feb 2013 23:36
size: 238

make str18 %18s Make and Model

price float %9.0g Price (USD)
mpg float %9.0g Mileage (mile per gallon)
weight float %9.0g Vehicle weight (lbs.)
gear_ratio float %9.0g Gear Ratio
Sorted by:
. save afewcars2
file afewcars2.dta saved

[ GSU ] 9 Labeling data 69
Warning: When you change or define labels on a dataset in memory, it is worth saving the dataset
right away. Because the actual data in the dataset did not change, Stata will not prevent you from
exiting or loading a new dataset later, and you could lose your labels.
Labeling values of variables

We will now add a new indicator variable to the dataset that is 0 if the car was made in the United
States and 1 if it was made in another country. Open up the Data Editor and use your previously
gained knowledge to add a foreign variable whose values match what is shown in this listing:

make price mpg weight gear_r~o foreign
1. VW Rabbit 4697 25 1930 3.78 1

2. Olds 98 8814 21 4060 2.41 0
3. Chev. Monza 3667 . 2750 2.73 0
4. 4099 22 2930 3.58 0
5. Datsun 510 5079 24 2280 3.54 1
6. Buick Regal 5189 20 3280 2.93 0
7. Datsun 810 8129 . 2750 3.55 1

You can create this new variable in the Data Editor if you would like to work along. (See [GSU] 6 Using
the Data Editor for help with the Data Editor.) Though the definitions of the categories “0” and “1”
are clear in this context, it still would be worthwhile to give the values explicit labels because it will
make output clear to people who are not so familiar with antique automobiles. This is done with a
value label.
We saw an example of creating and attaching a value label by using the point-and-click interface
available in the Data Editor in Changing data in [GSU] 6 Using the Data Editor. Here we will do it
directly from the Command window.

. label define origin 0 "domestic" 1 "foreign"
. label values foreign origin
. describe
Contains data from afewcars2.dta
obs: 7 A few 1978 cars
vars: 6 4 Feb 2013 23:36
size: 245

make str18 %18s Make and Model

price float %9.0g Price (USD)
mpg float %9.0g Mileage (mile per gallon)
weight float %9.0g Vehicle weight (lbs.)
gear_ratio float %9.0g Gear Ratio
foreign byte %8.0g origin
Sorted by:
Note: dataset has changed since last saved
. save afewcarslab
file afewcarslab.dta saved

From this example, we can see that a value label is defined via
label define labelname # "contents" # "contents" . . .
It can then be attached to a variable via
label values variablename labelname
Once again, we need to save the dataset to be sure that we do not mistakenly lose the labels later.
We saved this under a new filename because we have cleaned it up, and we would like to use it in
the next chapter.
If you had wanted to define the value labels by using a point-and-click interface, you could do this
with the Properties window in either the Main window or the Data Editor or by using the Variables
Manager. See [GSU] 7 Using the Variables Manager for more information.
There is more to value labels than what was covered here; see [U] 12.6.3 Value labels for a
complete treatment.
You may also add notes to your data and your variables. This feature was previously discussed
in Renaming and formatting variables in [GSU] 6 Using the Data Editor and Managing notes in
[GSU] 7 Using the Variables Manager. You can learn more about notes by typing help notes, or
you can get the full story in [D] notes.
10 Listing data and basic command syntax
Command syntax
This chapter gives a basic lesson on Stata’s command syntax while showing how to control the
appearance of a data list.
As we have seen throughout this manual, you have a choice between using menus and dialogs
and using the Command window. Although many find the menus more natural and the Command
window baffling at first, some practice makes working with the Command window often much faster
than using menus and dialogs. The Command window can become a faster way of working because
of the clean and regular syntax of Stata commands. We will cover enough to get you started; help
language has more information and examples, and [U] 11 Language syntax has all the details.
The syntax for the list command can be seen by typing help list:

list varlist if in , options
Here is how to read this syntax:
• Anything inside square brackets is optional. For the list command,
a. varlist is optional. A varlist is a list of variable names.
b. if is optional. The if qualifier restricts the command to run only on those observations for
which the qualifier is true. We saw examples of this in [GSU] 6 Using the Data Editor.
c. in is optional. The in qualifier restricts the command to run on particular observation
numbers.
d. , and options are optional. options are separated from the rest of the command by a
comma.
• Optional pieces do not preclude one another unless explicitly stated. For the list command,
it is possible to use a varlist with if and in.
• If a part of a word is underlined, the underlined part is the minimum abbreviation. Any
abbreviation at least this long is acceptable.
a. The l in list is underlined, so l, li, and lis are all equivalent to list.
• Anything not inside square brackets is required. For the list command, only the command
itself is required.
Keeping these rules in mind, let’s investigate how list behaves when called with different arguments.
We will be using the dataset afewcarslab.dta from the end of the previous chapter.
list with a variable list

Variable lists (or varlists) can be specified in a variety of ways, all designed to save typing and
encourage good variable names.
• The varlist is optional for list. This means that if no variables are specified, it is equivalent to
specifying all variables. Another way to think of it is that the default behavior of the command
is to run on all variables unless restricted by a varlist.
• You can list a subset of variables explicitly, as in list make mpg price.
• There are also many shorthand notations:
m* means all variables starting with m.
price-weight means all variables from price through weight in the dataset order.
ma?e means all variables starting with ma, followed by any character, and ending in e.
71
72 [ GSU ] 10 Listing data and basic command syntax
• You can list a variable by using an abbreviation unique to that variable, as in list gear r~o.
If the abbreviation is not unique, Stata returns an error message.

. list
1. VW Rabbit 4697 25 1930 3.78 foreign

2. Olds 98 8814 21 4060 2.41 domestic
3. Chev. Monza 3667 . 2750 2.73 domestic
4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign
6. Buick Regal 5189 20 3280 2.93 domestic

7. Datsun 810 8129 . 2750 3.55 foreign
. l make mpg price
make mpg price
1. VW Rabbit 25 4697
2. Olds 98 21 8814
3. Chev. Monza . 3667
4. 22 4099
5. Datsun 510 24 5079
6. Buick Regal 20 5189

7. Datsun 810 . 8129
. list m*
make mpg
1. VW Rabbit 25
2. Olds 98 21
3. Chev. Monza .
4. 22
5. Datsun 510 24
6. Buick Regal 20
7. Datsun 810 .
. li price-weight
price mpg weight
1. 4697 25 1930
2. 8814 21 4060
3. 3667 . 2750
4. 4099 22 2930
5. 5079 24 2280
6. 5189 20 3280
7. 8129 . 2750

[ GSU ] 10 Listing data and basic command syntax 73

. list ma?e
make
1. VW Rabbit
2. Olds 98
3. Chev. Monza
4.
5. Datsun 510
6. Buick Regal
7. Datsun 810
. l gear_r~o
gear_r~o
1. 3.78
2. 2.41
3. 2.73
4. 3.58
5. 3.54
6. 2.93
7. 3.55

list with if
The if qualifier uses a logical expression to determine which observations to use. If the expression
is true, the observation is used in the command; otherwise, it is skipped. The operators whose results
are either true or false are
< less than

<= less than or equal
== equal
> greater than
>= greater than or equal
!= not equal
& and
| or
! not (logical negation; ~ can also be used)
() parentheses are for grouping to specify order of evaluation
In the logical expressions, & is evaluated before | (similar to multiplication before addition in
arithmetic). You can use this in your expressions, but it is often better to use parentheses to ensure
that the expressions are evaluated in the proper order. See [U] 13.2 Operators for complete details.

. list

2. Olds 98 8814 21 4060 2.41 domestic
4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign

7. Datsun 810 8129 . 2750 3.55 foreign
. list if mpg > 22

5. Datsun 510 5079 24 2280 3.54 foreign
7. Datsun 810 8129 . 2750 3.55 foreign
. list if (mpg > 22) & !missing(mpg)

5. Datsun 510 5079 24 2280 3.54 foreign
. list make mpg price gear if (mpg > 22) | (price > 8000 & gear < 3.5)
make mpg price gear_r~o
1. VW Rabbit 25 4697 3.78

2. Olds 98 21 8814 2.41
3. Chev. Monza . 3667 2.73
5. Datsun 510 24 5079 3.54
7. Datsun 810 . 8129 3.55
. list make mpg if mpg <= 22 in 2/4
make mpg
2. Olds 98 21
4. 22

In the listings above, we see more examples of Stata treating missing numerical values as large values,
as well as the care that should be taken when the if qualifier is applied to a variable with missing
values. See [GSU] 6 Using the Data Editor.
list with if, common mistakes

Here is a series of listings with common errors and their corrections. See if you can find the errors
before reading the correct entry.

. list

2. Olds 98 8814 21 4060 2.41 domestic
4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign

7. Datsun 810 8129 . 2750 3.55 foreign
. list if mpg=21
=exp not allowed
r(101);

The error arises because “equal” is expressed by ==, not by =. Corrected, it becomes

. list if mpg==21
2. Olds 98 8814 21 4060 2.41 domestic

Other common errors with logic:

. list if mpg==21 if weight > 4000
invalid syntax
r(198);
. list if mpg==21 and weight > 4000
invalid ’and’
r(198);

Joint tests are specified with &, not with the word and or multiple ifs. The if qualifier should be
if mpg==21 & weight>4000, not if mpg==21 if weight>4000. Here is its correction:

. list if mpg==21 & weight > 4000
2. Olds 98 8814 21 4060 2.41 domestic

A problem with string variables:

. list if make==Datsun 510
Datsun not found
r(111);

Strings must be in double quotes, as in make=="Datsun 510". Without the quotes, Stata thinks that
Datsun is a variable that it cannot find. Here is the correction:

. list if make=="Datsun 510"
5. Datsun 510 5079 24 2280 3.54 foreign

Confusing value labels with strings:

. list if foreign=="domestic"
type mismatch
r(109);

Value labels look like strings, but the underlying variable is numeric. Variable foreign takes on values
0 and 1 but has the value label that attaches 0 to “domestic” and 1 to “foreign” (see [GSU] 9 Labeling
data). To see the underlying numeric values of variables with labeled values, use the label list
command (see [D] label), or investigate the variable with codebook varname. We can correct the
error here by looking for observations where foreign==0.
There is a second construction that also allows the use of the value label directly.

. list if foreign==0
2. Olds 98 8814 21 4060 2.41 domestic

4. 4099 22 2930 3.58 domestic
. list if foreign=="domestic":origin
2. Olds 98 8814 21 4060 2.41 domestic

4. 4099 22 2930 3.58 domestic

list with in
The in qualifier uses a numlist to give a range of observations that should be listed. numlists
have the form of one number or first/last. Positive numbers count from the beginning of the dataset.
Negative numbers count from the end of the dataset. Here are some examples:

. list

2. Olds 98 8814 21 4060 2.41 domestic
4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign

7. Datsun 810 8129 . 2750 3.55 foreign
. list in 1
. list in -1
7. Datsun 810 8129 . 2750 3.55 foreign
. list in 2/4
2. Olds 98 8814 21 4060 2.41 domestic

4. 4099 22 2930 3.58 domestic
. list in -3/-2
5. Datsun 510 5079 24 2280 3.54 foreign


Controlling the list output

The fine control over list output is exercised by specifying one or more options. You can use
sepby() to separate observations by variable. abbreviate() specifies the minimum number of
characters to abbreviate a variable name in the output. divider draws a vertical line between the
variables in the list.

. sort foreign
. list ma p g f, sepby(foreign)
make price gear_r~o foreign
1. Olds 98 8814 2.41 domestic

2. Chev. Monza 3667 2.73 domestic
3. Buick Regal 5189 2.93 domestic
4. 4099 3.58 domestic
5. Datsun 510 5079 3.54 foreign

6. VW Rabbit 4697 3.78 foreign
7. Datsun 810 8129 3.55 foreign
. list make weight gear, abbreviate(10)
make weight gear_ratio
1. Olds 98 4060 2.41

2. Chev. Monza 2750 2.73
3. Buick Regal 3280 2.93
4. 2930 3.58
5. Datsun 510 2280 3.54
6. VW Rabbit 1930 3.78

7. Datsun 810 2750 3.55
. list, divider
1. Olds 98 8814 21 4060 2.41 domestic

4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign

7. Datsun 810 8129 . 2750 3.55 foreign

The separator() option draws a horizontal line at specified intervals. When not specified, it defaults
to a value of 5.

1. Olds 98 8814 21 4060 2.41 domestic

4. 4099 22 2930 3.58 domestic

5. Datsun 510 5079 24 2280 3.54 foreign
7. Datsun 810 8129 . 2750 3.55 foreign

More
When you see a more prompt at the bottom of the Results window, it means that there is more
information to be displayed. This happens, for example, when you are listing many observations.

. list make mpg
make mpg
1. Linc. Continental 12
2. Linc. Mark V 12
3. Cad. Deville 14
4. Cad. Eldorado 14
5. Linc. Versailles 14
6. Merc. Cougar 14
7. Merc. XR-7 14
8. Peugeot 604 14
9. Buick Electra 15
10. Merc. Marquis 15
11. Buick Riviera 16

12. Chev. Impala 16
13. Dodge Magnum 16
14. Olds Toronado 16
15. AMC Pacer 17
16. Audi 5000 17

17. Dodge St. Regis 17
18. Volvo 260 17
19. Buick LeSabre 18
20. Dodge Diplomat 18
more

If you want to see the next screen of text, you have a few options: press any key, such as the Spacebar;
click on the More button, ; or click on the blue more at the bottom of the Results window.
To see just the next line of text, press Enter.
Break
If you want to interrupt a Stata command, click on the Break button, . If you see a more
prompt at the bottom of the Results window and wish to interrupt it, click on the Break button or
press q.

. list make mpg
make mpg
1. Linc. Continental 12
2. Linc. Mark V 12
3. Cad. Deville 14
4. Cad. Eldorado 14
5. Linc. Versailles 14
6. Merc. Cougar 14
7. Merc. XR-7 14
8. Peugeot 604 14
9. Buick Electra 15
10. Merc. Marquis 15
11. Buick Riviera 16

12. Chev. Impala 16
13. Dodge Magnum 16
14. Olds Toronado 16
15. AMC Pacer 17
16. Audi 5000 17

17. Dodge St. Regis 17
18. Volvo 260 17
19. Buick LeSabre 18
20. Dodge Diplomat 18
break
r(1);

It is always safe to click on the Break button. After you click on Break, the state of the system is
the same as if you had never issued the original command.
11 Creating new variables
generate and replace

This chapter shows the basics of creating and modifying variables in Stata. We saw how to work
with the Data Editor in [GSU] 6 Using the Data Editor—this chapter shows how we would do this
from the Command window. The two primary commands used for this are
• generate for creating new variables. It has a minimum abbreviation of g.
• replace for replacing the values of an existing variable. It may not be abbreviated because it
alters existing data and hence can be considered dangerous.
The most basic form for creating new variables is generate newvar = exp, where exp is any kind
of expression. Of course, both generate and replace can be used with if and in qualifiers. An
expression is a formula made up of constants, existing variables, operators, and functions. Some
examples of expressions (using variables from the auto dataset) would be 2 + price, weight^2 or
sqrt(gear ratio).
The operators defined in Stata are given in the table below:
Relational
Arithmetic Logical (numeric and string)
+ addition ! not > greater than
- subtraction | or < less than
* multiplication & and >= > or equal
/ division <= < or equal
^ power == equal
!= not equal
+ string concatenation
Stata has many mathematical, statistical, string, date, time-series, and programming functions. See
help functions for the basics, and see [D] functions for a complete list and full details of all the
built-in functions.
You can use menus and dialogs to create new variables and modify existing variables by selecting
menu items from the Data > Create or change data menu. This feature can be handy for finding
functions quickly. However, we will use the Command window for the examples in this chapter
because we would like to illustrate simple usage and some pitfalls.
Stata has some utility commands for creating new variables:
• The egen command is useful for working across groups of variables or within groups of
observations. See [D] egen for more information.
• The encode command turns categorical string variables into encoded numeric variables, while
its counterpart decode reverses this operation. See [D] encode for more information.
• The destring command turns string variables that should be numeric, such as numbers with
currency symbols, into numbers. To go from numbers to strings, the tostring command is
useful. See [D] destring for more information.
We will focus our efforts on generate and replace.
81
82 [ GSU ] 11 Creating new variables
generate
There are some details you should know about the generate command:
• The basic form of the generate command is generate newvar = exp, where newvar is a
new variable name and exp is any valid expression. You will get an error message if you try
to generate a variable that already exists.
• An algebraic calculation using a missing value yields a missing value, as does division by zero,
the square root of a negative number, or any other computation which is impossible.
• If missing values are generated, the number of missing values in newvar is always reported. If
Stata says nothing about missing values, then no missing values were generated.
• You can use generate to set the storage type of the new variable as it is generated. You might
want to create an indicator (0/1) variable as a byte, for example, because it saves 3 bytes per
observation over using the default storage type of float.
Below are some examples of creating new variables from the afewcarslab dataset, which we
created in Labeling values of variables in [GSU] 9 Labeling data. (To work along, start by opening
the auto dataset with sysuse auto. We are using a smaller dataset to make shorter listings.) The
last example shows a way to generate an indicator variable for cars weighing more than 3,000 pounds.
Logical expressions in Stata result in 1 for “true” and 0 for “false”. The if qualifier is used to ensure
that the computations are done only for observations where weight is not missing.
[ GSU ] 11 Creating new variables 83

. use afewcarslab
(A few 1978 cars)
. list make mpg weight
make mpg weight
1. VW Rabbit 25 1930
2. Olds 98 21 4060
3. Chev. Monza . 2750
4. 22 2930
5. Datsun 510 24 2280
6. Buick Regal 20 3280

7. Datsun 810 . 2750
. * changing MPG to liters per 100km

. generate lphk = 3.7854 * (100 / 1.6093) / mpg
(2 missing values generated)
. label var lphk "Liters per 100km"
. * getting logarithms of price
. g lnprice = ln(price)
. * making an indicator of hugeness
. gen byte huge = weight >= 3000 if !missing(weight)
. l make mpg weight lphk lnprice huge
make mpg weight lphk lnprice huge
1. VW Rabbit 25 1930 9.408812 8.454679 0

2. Olds 98 21 4060 11.20097 9.084097 1
3. Chev. Monza . 2750 . 8.207129 0
4. 22 2930 10.69183 8.318499 0
5. Datsun 510 24 2280 9.800845 8.532869 0
6. Buick Regal 20 3280 11.76101 8.554296 1

7. Datsun 810 . 2750 . 9.003193 0

replace
Whereas generate is used to create new variables, replace is the command used for existing
variables. Stata uses two different commands to prevent you from accidentally modifying your data.
The replace command cannot be abbreviated. Stata generally requires you to spell out completely
any command that can alter your existing data.

. list make weight
make weight
1. VW Rabbit 1930
2. Olds 98 4060
3. Chev. Monza 2750
4. 2930
5. Datsun 510 2280
6. Buick Regal 3280

7. Datsun 810 2750
. * will give an error because weight already exists

. gen weight = weight/1000
weight already defined
r(110);
. * will replace weight in lbs by weight in 1000s of lbs
. replace weight = weight/1000
(7 real changes made)
. list make weight
make weight
1. VW Rabbit 1.93
2. Olds 98 4.06
3. Chev. Monza 2.75
4. 2.93
5. Datsun 510 2.28
6. Buick Regal 3.28

7. Datsun 810 2.75

Suppose that you want to create a new variable, predprice, which will be the predicted price of the
cars in the following year. You estimate that domestic cars will increase in price by 5% and foreign
cars, by 10%.
One way to create the variable would be to first use generate to compute the predicted domestic
car prices. Then use replace to change the missing values for the foreign cars to their proper values.

. gen predprice = 1.05*price if foreign==0
. replace predprice = 1.10*price if foreign==1
. list make foreign price predprice, nolabel
make foreign price predpr~e
1. VW Rabbit 1 4697 5166.7

2. Olds 98 0 8814 9254.7
3. Chev. Monza 0 3667 3850.35
4. 0 4099 4303.95
5. Datsun 510 1 5079 5586.9
6. Buick Regal 0 5189 5448.45

7. Datsun 810 1 8129 8941.9

Of course, because foreign is an indicator variable, we could generate the predicted variable with
one command:

. gen predprice2 = (1.05 + 0.05*foreign)*price
. list make foreign price predprice predprice2, nolabel
make foreign price predpr~e predpr~2
1. VW Rabbit 1 4697 5166.7 5166.7

2. Olds 98 0 8814 9254.7 9254.7
3. Chev. Monza 0 3667 3850.35 3850.35
4. 0 4099 4303.95 4303.95
5. Datsun 510 1 5079 5586.9 5586.9
6. Buick Regal 0 5189 5448.45 5448.45

7. Datsun 810 1 8129 8941.9 8941.9

generate with string variables

Stata is smart. When you generate a variable and the expression evaluates to a string, Stata creates
a string variable with a storage type as long as necessary, and no longer than that. where is a str1
in the following example:

. list make foreign
make foreign
1. VW Rabbit foreign
2. Olds 98 domestic
3. Chev. Monza domestic
4. domestic
5. Datsun 510 foreign
6. Buick Regal domestic

7. Datsun 810 foreign
. gen where = "D" if foreign=="domestic":origin

. replace where = "F" if foreign=="foreign":origin
. list make foreign where
make foreign where
1. VW Rabbit foreign F
2. Olds 98 domestic D
3. Chev. Monza domestic D
4. domestic D
5. Datsun 510 foreign F
6. Buick Regal domestic D

7. Datsun 810 foreign F
. describe where
where str1 %9s

Stata has some useful tools for working with string variables. Here we split the make variable into
make and model and then create a variable that has the model together with where the model was
manufactured:

. gen model = substr(make, strpos(make," ")+1, .)
(1 missing value generated)
. gen modelwhere = model + " " + where
. list make where model modelwhere
make where model modelw~e
1. VW Rabbit F Rabbit Rabbit F

2. Olds 98 D 98 98 D
3. Chev. Monza D Monza Monza D
4. D D
5. Datsun 510 F 510 510 F
6. Buick Regal D Regal Regal D

7. Datsun 810 F 810 810 F

There are a few things to note about how these commands work:
1. strpos(s1 ,s2 ) produces an integer equal to the first position in the string s1 at which the
string s2 is found or 0 if it is not found. In this example, strpos(make," ") finds the position
of the first space in each observation of make.
2. substr(s,start,len) produces a string of length len beginning at character start of string
s. If c1 = ., the result is the string from character start to the end of string s.
3. Putting 1 and 2 together: substr(s,strpos(s," ")+1,.) will always give the string s with
its first word removed. Because make contains both the make and the model of each car, and
make never contains a space in this dataset, we have found each car’s model.
4. The operator “+”, when applied to string variables, will concatenate the strings (that is, join
them together). The expression "this" + "that" results in the string "thisthat". When the
variable modelwhere was generated, a space (" ") was added between the two strings.
5. The missing value for a string is nothing special—it is simply the empty string "". Thus the
value of modelwhere for the car with no make or model is " D" (note the leading space).
12 Deleting variables and observations
clear, drop, and keep

In this chapter, we will present the tools for paring observations and variables from a dataset. We
saw how to do this using the Data Editor in [GSU] 6 Using the Data Editor; this chapter presents
the methods for doing so from the Command window.
There are three main commands for removing data and other Stata objects, such as value labels,
from memory: clear, drop, and keep. Remember that they affect only what is in memory. None
of these commands alters anything that has been saved to disk.
clear and drop all

Suppose that you are working on an analysis or a simulation and that you need to clear out Stata’s
memory so that you can impute different values or simulate a new dataset. You are not interested in
saving any of the changes you have made to the dataset in memory—you would just like to have
an empty dataset. What you do depends on how much you want to clear out: at any time, you can
have not only data but also metadata such as value labels, stored results from previous commands,
and stored matrices. The clear command will let you carefully clear out data or other objects; we
are interested only in simple usage here. For more information, see help clear and [D] clear.
If you type the command clear into the Command window, it will remove all variables and value
labels. In basic usage, this is typically enough. It has the nice property that it does not remove any
stored results, so you can load a new dataset and predict values by using stored estimation results from
a model fit on a previous dataset. See help postest and [U] 20 Estimation and postestimation
commands for more information.
If you want to be sure that everything is cleared out, use the command clear all. This command
will clear Stata’s memory of data and all auxiliary objects so that you can start with a clean slate.
The first time you use clear all while you have a graph or dialog open, you may be surprised
when that graph or dialog closes; this is necessary so that Stata can free all memory being used.
If you want to get rid of just the data and nothing else, you can use the command drop all.
drop
The drop command is used to remove variables or observations from the dataset in memory.
• If you want to drop variables, use drop varlist.
• If you want to drop observations, use drop with an if or an in qualifier or both.
88
[ GSU ] 12 Deleting variables and observations 89
We will use the afewcarslab dataset to illustrate drop:

. use afewcarslab
(A few 1978 cars)
. list

2. Olds 98 8814 21 4060 2.41 domestic
4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign

7. Datsun 810 8129 . 2750 3.55 foreign
. drop in 1/3
(3 observations deleted)
. list
1. 4099 22 2930 3.58 domestic

2. Datsun 510 5079 24 2280 3.54 foreign
4. Datsun 810 8129 . 2750 3.55 foreign
. drop if mpg > 21

. list
. drop gear_ratio
. list
make price mpg weight foreign
1. Buick Regal 5189 20 3280 domestic
. drop m*
. list
price weight foreign
1. 5189 3280 domestic

These changes are only to the data in memory. If you want to make the changes permanent, you
need to save the dataset.
90 [ GSU ] 12 Deleting variables and observations
keep
keep tells Stata to drop all variables except those specified explicitly or through the use of an if or
in expression. Just like drop, keep can be used with a varlist or with qualifiers but not with both at
once. We use a clear command at the start of this example so that we can reload the afewcarslab
dataset:

. clear
. use afewcarslab
(A few 1978 cars)
. list

2. Olds 98 8814 21 4060 2.41 domestic
4. 4099 22 2930 3.58 domestic
5. Datsun 510 5079 24 2280 3.54 foreign

7. Datsun 810 8129 . 2750 3.55 foreign
. keep in 4/7
. list
1. 4099 22 2930 3.58 domestic

2. Datsun 510 5079 24 2280 3.54 foreign
4. Datsun 810 8129 . 2750 3.55 foreign
. keep if mpg <= 21

. list
. keep m*
. list
make mpg
1. Buick Regal 20

13 Using the Do-file Editor—automating Stata
The Do-file Editor in Stata(GUI)

Stata comes with an integrated text editor called the Do-file Editor, which can be used for many
tasks. It gets its name from the term do-file, which is a file containing a list of commands for Stata
to run (called a batch file or a script in other settings). See [U] 16 Do-files for more information.
Although the Do-file Editor has advanced features that can help in writing such files, it can also be
used to build up a series of commands that can then be submitted to Stata all at once. This feature
can be handy when writing a loop to process multiple variables in a similar fashion or when doing
complex, repetitive tasks interactively.
To get the most from this chapter, you should work through it at your computer. Start by opening
the do-file editor, either by clicking on the Do-file Editor button, , or by typing doedit in the
Command window and pressing Enter.
The Do-file Editor toolbar

The Do-file Editor has 15 buttons. Many of the buttons share a similar purpose with their look-alikes
in the main Stata toolbar.
If you ever forget what a button does, hover the mouse pointer over a button, and a tooltip will
appear.
New: Open a new do-file in a new tab in the Do-file Editor.
Open: Open a do-file from disk in a new tab in the Do-file Editor.
Save: Save the current do-file to disk.
Print: Print the contents of the Do-file Editor.
Find: Open the Find/Replace dialog for finding and replacing text.
Cut: Cut the selected text and put it in the Clipboard.
Copy: Copy the selected text to the Clipboard.
Paste: Paste the text from the Clipboard into the current document.
Undo: Undo the last change.
91
92 [ GSU ] 13 Using the Do-file Editor—automating Stata
Redo: Undo the last undo.
Toggle Bookmark: Turn on or off the bookmark on the current line. Bookmarks are a
way to move quickly within the do-file. They are quite useful in long do-files or when
debugging.
Previous Bookmark: Go to the previous bookmark (if any).
Next Bookmark: Go to the next bookmark (if any).
Show File in Viewer: Show the contents of the do-file in a Viewer window. This is
worthwhile when editing files that contain SMCL tags, such as log files or help files.
Execute (do): Run the commands in the do-file, showing all commands and their output.
If text is highlighted, the button will run only the selected lines, showing all output. We
will refer to this as the Do button.
Using the Do-file Editor

Suppose that we would like to analyze fuel usage for 1978 automobiles in a manner similar to
what we did in [GSU] 1 Introducing Stata—sample session. We know that we will be issuing many
commands to Stata during our analysis and that we want to be able to reproduce our work later
without having to type each command again.
We can do this easily in Stata: simply save a text file containing the commands. When that is
done, we can tell Stata to run the file and execute each command in sequence. Such a file is known
as a Stata do-file; see [U] 16 Do-files.
To analyze fuel usage of 1978 automobiles, we would like to create a new variable containing
gallons per mile. We would like to see how that variable changes in relation to vehicle weight for
both domestic and imported cars. Performing a regression with our new variable would be a good
first step.
To get started, click on the Do-file Editor button to open the Do-file Editor. After the Do-file
Editor opens, type the commands below into the Do-file Editor. Purposely misspell the name of the
foreign variable on the fifth line. (We are intentionally making some common mistakes and then
pointing you to the solutions. This will save you time later.)
* an example do-file
sysuse auto
generate gp100m = 100/mpg
label var gp100m "Gallons per 100 miles"
regress gp100m weight foreing
[ GSU ] 13 Using the Do-file Editor—automating Stata 93
Here is what your Do-file Editor should look like now:
You will notice that the color of the text changes as you type. The different colors are examples
of the Do-file Editor’s syntax highlighting. The colors and text properties of the syntax elements can
be changed by right-clicking in the Do-file Editor, selecting Preferences... and then clicking on the
Syntax Highlighting tab in the resulting window.
Click on the Do button, , to execute the commands. Stata executes the commands in sequence,
and the results appear in the Results window:

. do /tmp/SD00001.000000
. * an example do-file
. sysuse auto
. label var gp100m "Gallons per 100 miles"
. regress gp100m weight foreing
variable foreing not found
r(111);
.
end of do-file

The do "/tmp/. . . " command is how Stata executes the commands in the Do-file Editor. Stata
saves the commands to a temporary file and issues the do command to execute them. Everything
worked as planned until Stata saw the misspelled variable. The first three commands were executed,
but an error was produced on the fourth. Stata does not know of a variable named foreing. We need
to go back to the Do-file Editor and change the misspelled variable name to foreign in the last line:
We click on the Do button again. Alas, Stata now fails on the first line—it will not overwrite the
dataset in memory that we changed.

. do /tmp/SD00001.000000
. sysuse auto
no; data in memory would be lost
r(4);
.
end of do-file

We now have a choice for what we should do:
• We can put a clear command in our do-file as the very first command. This automatically
clears out Stata’s memory before the do-file tries to load the auto dataset. This is convenient but
dangerous because it defeats Stata’s protection against throwing away changes without warning.
• We can type a clear command in the Command window to manually clear the dataset and
then process the do-file again. This process can be aggravating when building a complicated
do-file.
Here is some advice: Automatically clear Stata’s memory while debugging the do-file. Once the
do-file is in its final form, decide the context in which it will be used. If it will be used in a highly
automated environment (such as when certifying), the do-file should still automatically clear Stata’s
memory. If it will be used rarely, do not clear Stata’s memory. This decision will save much heartache.
We will add a clear option to the sysuse command to automatically clear the dataset in Stata’s
memory before the do-file runs:
The do-file now runs well, as clicking on the Do button shows:

. do /tmp/SD00001.000000
. sysuse auto, clear
. label var gp100m "Gallons per 100 miles"
. regress gp100m weight foreign
F( 2, 71) = 113.97
Model 91.1761694 2 45.5880847 Prob > F = 0.0000
Residual 28.4000913 71 .400001287 R-squared = 0.7625
Total 119.576261 73 1.63803097 Root MSE = .63246
gp100m Coef. Std. Err. t P>|t| [95% Conf. Interval]
weight .0016254 .0001183 13.74 0.000 .0013896 .0018612

foreign .6220535 .1997381 3.11 0.003 .2237871 1.02032
_cons -.0734839 .4019932 -0.18 0.855 -.8750354 .7280677
.
end of do-file

You might want to select File > Save As... to save this do-file from the Do-file Editor. Later, you
could select File > Open to open it and then add more commands as you move forward with your
analysis. By saving the commands of your analysis in a do-file as you go, you do not have to worry
about retyping them with each new Stata session. Think hard about removing the clear option from
the first command.
After you have saved your do-file, you can execute the commands it contains by typing do filename,
where the filename is the name of your do-file.
The File menu

The File menu of the Do-file Editor includes standard features found in most text editors. You
may choose any of these menu items: create a New > Do-file, Open an existing file, Save the current
file, save the current file under a new name with Save As..., or Print... the current file. There are
also buttons on the Do-file Editor’s toolbar that correspond to these features.
You can also select Insert File... to insert the contents of another file at the current cursor position
in the Do-file Editor.
Finally, you can create a New > Project... to keep track of collections of files used in a project.
These can be do-files, data files, graph files, or any other files you like. For more information on the
Project Manager, see [P] Project Manager.
The Edit menu

The Edit menu of the Do-file Editor includes the standard Undo, Redo, Cut, Copy, Paste, Delete,
and Find capabilities. There are also buttons on the Do-file Editor’s toolbar for easy access to these
capabilities. There are several other Edit menu features that you might find useful:
• You may select the current line with Select Line.
• You may delete the current line with Delete Line.
• Find > Go To Line... will allow you to jump to a specific line number. The line numbers are
displayed at the left of the Do-file Editor window.
• Advanced leads to a submenu with some programmer’s friends:
– Shift Right indents the selection by one tab.
– Shift Left unindents the selection by one tab.
– Make Selection Uppercase converts the selection to all capital letters.
– Make Selection Lowercase converts the selection to all lowercase letters.
– Convert Line Endings to Mac OS X/Unix Format (\n) converts the line endings for the
current file to Mac OS X/Unix format.
– Convert Line Endings to Windows Format (\r\n) converts the line endings for the
current file to Windows format.
Matching and balancing of parentheses ( ), braces { }, and brackets [ ] are also available from the
Edit menu. When you select Edit > Find > Match Brace, the Do-file Editor looks at the character
immediately to the left and right of the cursor. If either is one of the characters that the editor can
match, the editor will find the matching character and place the cursor immediately in front of it. If
there is no match, the cursor will not move.
When you select Edit > Find > Balance Braces, the Do-file Editor looks to the left and right
of the current cursor position or selection and creates a selection that includes the narrowest level
of matching characters. If you select Balance Braces again, the editor will expand the selection to
include the next level of matching characters. If there is no match, the cursor will not move. Balancing
braces is useful for working with complicated expressions or blocks of code defined by loops or if
commands. See [P] foreach, [P] forvalues, [P] while, and [P] if for more information.
Balance Braces is easier to explain with an example. Type (now (is the) time) in the Do-file
Editor. Place the cursor between the words is and the. Select Edit > Find > Balance Braces. The
Do-file Editor will select (is the). If you select Balance Braces again, the Do-file Editor will select
(now (is the) time).
Editing tip: You can click on the left margin near a line number to select the entire line and the
end-of-line characters. Doing so makes it easy to delete lines or cut lines and paste them elsewhere.
You can click and drag within the line-number column to select a range of complete lines.
The View menu

The View menu of the Do-File Editor allows you to zoom in and out or display special characters
such as tabs and line endings.
The Tools menu

You have already learned about the Do button. Selecting Tools > Execute (do) is equivalent to
clicking on the Execute (do) button.
Selecting Tools > Execute (do) to Bottom will send all the commands from the current line
through the end of the contents of the Do-file Editor to the Command window. This method is a
quick way to run a part of a do-file.
Do is equivalent to Stata’s do command; see [U] 16 Do-files for a complete discussion.
You can also preview files in the Viewer by selecting Tools > Show File in Viewer or by clicking
on the Show File in Viewer button, . This feature is useful when working with files that use
Stata’s SMCL tags, such as when writing help files or editing log files.
Saving interactive commands from Stata as a do-file

While working interactively with Stata, you might decide that you would like to rerun the last
several commands that you typed interactively. From the Review window, you can send highlighted
commands or even the entire contents to the Do-file Editor. You can also save commands as a do-file
and open that file in the Do-file Editor. You can copy a command from a dialog (rather than submit
it) and paste it into the Do-file Editor. See [GSU] 6 Using the Data Editor for details. Also see
[R] log for information on the cmdlog command, which allows you to log all commands that you
type in Stata to a do-file.
Projects
For advanced users managing many files as part of a project, Stata has a Project Manager that
uses the Do-file Editor. For more information on the Project Manager, see [P] Project Manager.
14 Graphing data
Working with graphs

Stata has a rich system for graphical representation of data. The main command for creating graphs
is unsurprisingly named Graph. Behind this plain name is a wealth of tools. In this chapter, we will
make one simple graph to point out the basics of the Graph window. See the [G] Stata Graphics
Reference Manual for more information about all aspects of working with graphs.
A simple graph example

In the sample session of [GSU] 1 Introducing Stata—sample session, we made a scatterplot,
added a fitted regression line, and made a grid of scatterplots to allow comparisons across groups.
Here, using the auto dataset, we make a simple box plot that shows the displacements of the cars’
engines and how they compare across repair records within the place of manufacture of the cars.
Start by loading the dataset by typing sysuse auto in the Command window and pressing Enter.
We select Graphics > Box plot, choose or type displacement in the Variables field on the Main
tab, click on the Categories tab, check the Group 1 checkbox and enter rep78 for the first grouping
variable, and check the Group 2 checkbox and enter foreign for the second grouping variable.
Finally, we click on the Submit button so that we could easily make changes to the graph if need
be. After we look at the graph, we realize that we forgot the title. We close the Graph window, click
on the Titles tab of the graph box dialog, type the title Displacement across Repairs within
Origin, and click on the Submit button again.
The Graph window comes up, showing us our nicely titled graph:
98
[ GSU ] 14 Graphing data 99
Graph window
When the Graph window comes up, it shows our graph in a window with a toolbar. The first four
buttons are familiar to us from other Stata windows: Open, Save, Print, and Copy. The next two
buttons are new:
Rename Graph: This button allows the graph to be renamed. Why would you do this?
If you would like to have multiple graphs open at once, the graphs need to be named.
So you can click on the Rename button to give a graph a name. This graph will then
remain open when you create your next graph.
Graph Editor: Stata has a Graph Editor that allows you to manipulate and edit your
graph. This feature will be introduced in the next chapter.
The inactive buttons to the right of the Graph Editor button are used by the Graph Editor, so
their meanings will become clear in the next chapter.
We decide that we like this graph and would like to save it. We can save it either by clicking on
the Save button and choosing a name and a location or by right-clicking on the Graph window itself
and selecting Save As....
Saving and printing graphs

You can save a graph once it is displayed by right-clicking on its window and selecting Save As....
You can print a graph by right-clicking on its window and selecting Print.... You can also use the
File menu to save or print a graph. We recommend that you always right-click on a graph to save
or print it to ensure that the correct graph is selected.
Right-clicking on the Graph window

Right-clicking on the Graph window displays a menu from which you can select the following:
• Save As... to save the graph to disk.
• Copy to copy the graph to the Clipboard.
• Start Graph Editor to start the Graph Editor.
• Preferences... to edit the preferences for graphs.
• Print... to print the graph.
The Graph button

The Graph button, , is located on the main window’s toolbar. The button has two parts, an
icon and an arrow. Clicking on the icon brings the topmost Graph window to the front of all other
windows. Clicking on the arrow displays a menu of open graphs. Selecting a graph from the menu
brings that graph to the front of all other windows. If you close the Graph window, you can reopen
it only by reissuing a Stata command that draws a new graph.
15 Editing graphs
The Graph Editor

With Stata’s Graph Editor, you can change almost anything on your graph; you can add text, lines,
arrows, and markers wherever you like.
We will first make a graph to edit and will then point out the tools in the Graph Editor. Start by
opening the auto dataset: sysuse auto. Here is the command that we will use to make the graph:

. scatter mpg weight, name(mygraph) title(Mileage vs. Vehicle Weight)

Start the Editor by right-clicking on your graph and selecting Start Graph Editor. Click once on
the title of the graph. Here is a picture of the Graph Editor with its elements labeled.
Select any of the tools along the left of the Graph Editor window to edit the graph. The Pointer
(Select Tool), , is selected by default.
You can change the properties of objects or drag them to new locations by using the Pointer. As
you select objects with the Pointer, a Contextual Toolbar will appear just above the graph. In the
above example, the title of the graph is selected, so the Contextual Toolbar has controls that are
relevant for editing titles. You can use any of the controls on the Contextual Toolbar to immediately
100
[ GSU ] 15 Editing graphs 101
change the most important properties of the selected object. Right-click on an object to access more
properties and operations. Hold the Shift key when dragging objects to constrain the movement to
horizontal or vertical directions.
Add text, lines, or markers (with optional labels) to your graph by using the three Add... tools—
, , and . Lines can be changed to arrows by using the Contextual Toolbar. If you do
not like the default properties, simply change their settings in the Contextual Toolbar before adding
the text, line, or marker. The new settings will then be applied to all added objects, even in future
Stata sessions.
Do not be afraid to try things. If you do not like a result, change it back by using the same tool
or by clicking on the Undo button, , in the Standard Toolbar for the Graph Editor (below the
main menu). Edit > Undo in the main menu does the same thing.
Remember to reselect the Pointer tool when you want to drag objects or change their properties.
You can move objects on the graph and have the rest of the objects adjust their position to
accommodate the move with the Grid Edit tool, . With this tool, you are repositioning objects
in the underlying grid that holds the objects in the graph. Some graphs, for example, by graphs, are
composed of nested grids. You can reposition objects only within the grid that contains them; they
cannot be moved to other grids.
You can also select objects in the Object Browser along the right of the graph. This window shows
a hierarchical listing of the objects in the graph. Clicking or right-clicking on an object in the Object
Browser is the same as clicking or right-clicking on the object in the graph.
The Graph Editor has the ability to record your actions and play them back on later graphs. When
you click on the Record button, , every editing action you take, including undos and redos, is
recorded. If you would like to do some editing that is not recorded, you can click on the Pause button,
. You can click on the Pause button again to resume recording. When you are done with your
recording, click on the Record button. You will be prompted to save your recording. Any recording
you save is available from the Play Recording button, , and may be applied to future graphs.
You can even play a recording in any Stata graph command by using the play option. See Graph
Recorder in [G-1] graph editor for more information.
Stop the editor by selecting File > Stop Graph Editor from the main menu or by clicking on the
Graph Editor button. When you stop the Graph Editor, you will be prompted to save your graph if
you have made any changes. If you do not save your graph, your changes will not be lost, but you
will risk losing them if you create a new graph in the same Graph window. You must stop the Editor
if you would like to work on other tasks in Stata.
Here are a few of the things that you can do with the Editor:
• Add annotations using lines, arrows, and text.
• Add or remove grid lines or reference lines.
• Add or modify titles, captions, and notes.
• Change scatterplots to line plots, connected plots, areas, bars, spikes, or drop lines—and, of
course, vice versa.
• Change the size, color, margin, and other properties of your graph’s titles (or any other text on
the graph).
• Move your legend to another side of the graph, or even place it in the plot region.
• Change the aspect ratio of your graph.
• Stack the bars on a bar graph or turn them into percentages.
102 [ GSU ] 15 Editing graphs
• Rotate or change the angle of axis labels.

• Add custom ticks and labels to the axes.
• Change the rule for the number and spacing of ticks and labels on an axis.
• Emphasize a point on the graph, whether marker, bar, spike, or other plot, by making it a
custom color, size, or symbol.
• Change the text or properties of a marker label.
Because you can edit every property of every object on the graph, you can change almost anything
about your graph. To learn more, see [G-1] graph editor or type help graph editor.
16 Saving and printing results by using logs
Using logs in Stata

When you work on an analysis, it is worthwhile to behave like a bench scientist and keep a
lab notebook of your actions so that your work can be easily replicated. Everyone has a feeling of
complete omniscience while working intensely—this feeling is wonderful but fleeting. The next day,
the exact small details needed for perfect duplication have become obscure. Stata has a lab notebook
at hand: the log file.
A log file is simply a record of your Results window. It records all commands and all textual
output as it happens. Thus it keeps your lab notebook for you as you work. Because it writes the
file to disk while it writes the Results window, it also protects you from disastrous failures, be they
power failures or computer crashes. We recommend that you start a log file whenever you begin any
serious work in Stata.
Logging output
All the output that appears in the Results window can be captured in a log file. Stata can save the
file in one of two different formats. By default, Stata will save the file in its Stata Markup and Control
Language (SMCL) format, which preserves all the formatting and links from the Results window.
You can open these results in the Viewer, and they will behave as though they were in the Results
window. If you would rather have plain-text files without any formatting, you can save the file as
a plain log file. We recommend using the SMCL format because SMCL files can be translated into a
variety of formats readable by applications other than Stata with the File > Log > Translate... menu
(see [R] translate).
To start a log file, click on the Log button, . This will open a standard file dialog that allows
you to specify a directory and filename for your log. If you do not specify a file extension, the
extension .smcl will be added to the filename. If you specify a file that already exists, you will be
asked whether you want to append the new log to the file or overwrite the file with the new log.
103
104 [ GSU ] 16 Saving and printing results by using logs
Here is an example of a short session:

name: <unnamed>
log: /home/mydir/data/base.smcl
log type: smcl
opened on: 4 Feb 2013, 23:36:17
. sysuse auto
. by foreign, sort: summarize price mpg

price 52 6072.423 3097.104 3291 15906

mpg 52 19.82692 4.743297 12 34

price 22 6384.682 2621.915 3748 12990

mpg 22 24.77273 6.611187 14 41
. * be sure to include the above stats in report!
. * now for something completely different
. corr price mpg
(obs=74)
price mpg
price 1.0000
mpg -0.4686 1.0000
. log close
name: <unnamed>
log: /home/mydir/data/base.smcl
log type: smcl
closed on: 4 Feb 2013, 23:36:17

There are a few items of interest.
• The header showing the log file’s location, type, and starting timestamp is part of the log file.
This feature helps when working with multiple log files.
• The two lines starting with asterisks (*) are comments. Stata ignores the text following the
asterisk, so you may type any comment you would like, with any special characters you would
like. Commenting is a good way to document your thought process and to mark sections of
the log for later use.
• In this example, the log file was closed by using the log close command. Doing so is not
strictly necessary because log files are automatically closed when you exit Stata.
Stata allows multiple log files to be open at once only if the log files are named. For details on
this topic, see help log.
[ GSU ] 16 Saving and printing results by using logs 105
Working with logs

Log files are best viewed using Stata’s Viewer. Select File > Log > View.... If there is a log file
open (as shown by the status bar), it will be the default log file to view; otherwise, you need to either
type the name of the log file into the dialog or click on the Browse... button to find the file with a
standard file dialog.
Once you are in the Viewer window, everything behaves as expected: you can copy text and paste
between the Viewer and anything else that uses text, such as word processors or text editors. You can
even paste into the Command window or the Do-file Editor, but you should take care to copy only
commands, not their output. It is okay to copy the prompt (“.”) at the start of the echoed command
because Stata is smart enough to ignore it in the Command window. When working with a word
processor, what you paste will be unformatted text; it will look best if you use a fixed-width font,
like Courier, to display it.
Viewing your current log file is a good way to keep a reminder of something you have already
done or a view of a previous result. The Viewer window takes a snapshot of your log file and hence
will not scroll as you keep working in Stata. If you need to see more recent results in the Viewer,
click on the Refresh button.
For more detailed information about logs, see [U] 15 Saving and printing output—log files and
[R] log. For more information about the Viewer, see [GSU] 3 Using the Viewer.
Printing logs
To print a standard SMCL log file, you need to have the log file open in a Viewer window. Once
the log file is in the Viewer, you can click on the Print button, right-click on the Viewer window,
and select Print..., or select File > Print. A Print dialog will appear.
• You can fill in none, any, or all the items Header, Name, and Project. You can check or uncheck
options to Print Line #’s, Print Header, and Print Logo. These items are saved and will appear
again in the print sheet Print dialog (in this and in future Stata sessions).
• You can set margins and page size from the Print dialog. Stata will choose a font size that it thinks
is appropriate for your printer.
You could also use the translate command to generate a PostScript or PDF version of the log
file. See [R] translate for more information.
If your log file is a plain-text file (.log instead of .smcl), you can open it in a text editor, such
as Emacs or vi, in the Do-file Editor or in your favorite word processor. You can then edit the log
file—add headings, comments, etc.—format it, and print it. If you bring the log file into a word
processor, it will be displayed and printed with its default font. The log file will not be easily readable
when printed in a proportionally spaced font (for example, ). It will look much better printed in a
fixed-width font (for example, Courier New).
Rerunning commands as do-files

Stata also can log just the commands from a session without recording the output. This feature is
a convenient way to make a do-file interactively. Such a file is called a cmdlog file by Stata. You
can start a cmdlog file by typing
cmdlog using filename.do
and you can close the cmdlog file by typing
106 [ GSU ] 16 Saving and printing results by using logs
cmdlog close
Here, for example, is what a cmdlog of the previous session would look like. It contains only
commands and comments and hence could be used as a do-file.

sysuse auto
by foreign, sort: summarize price mpg
* be sure to include the above stats in report!
* now for something completely different
corr price mpg

If you start working and then wish you had started a cmdlog file, you can save yourself heartache
by saving the contents of the Review window. The Review window stores the last 5,000 commands
you have typed. Simply right-click on the Review window and select Save All... from the menu.
This will work best if you first filter out all the commands which resulted in errors as was shown in
The Review window in [GSU] 2 The Stata user interface. If you would like to move the commands
directly to the Do-file Editor, select Send to Do-file Editor. You may find this method a more
convenient way to create a text file containing only the commands that you typed during your session.
See [GSU] 13 Using the Do-file Editor—automating Stata, [U] 16 Do-files, and [U] 15 Saving
and printing output—log files for more information.
17 Setting font and window preferences
Changing and saving fonts and sizes and positions of your windows
You may find that you would like to change the fonts and display style of Stata’s windows,
depending on your monitor resolution and personal preferences. At the same time, there could be
requirements for font usage, say, when you submit graphs to journals. Stata accommodates both of
these by allowing sets of preferences for how windows are displayed.
We will first cover what can be changed in each window and then talk about what you can manage
with your preferences.
Graph window
The preferences for the Graph window can be changed by right-clicking on the Graph window
and choosing Preferences... from the contextual menu. The settings can then be set for how graphs
are displayed in Stata. The settings that should be used when printing can be set using the Printer
item.
The Graph preferences allow different schemes that control the look of graphs. These schemes
provide a quick way to optimize graphs for printing or to display on a screen. There are even schemes
defined for The Economist and the Stata Journal so that you can get the details for these publications
right without much fuss. Changing the scheme does not change the current graph—it applies the
settings to future graphs.
All other windows

You can change the display font and font size for most types of windows in Stata.
If fonts and font sizes for a window can be changed, they can be changed by right-clicking
on the window and selecting Preferences... from the contextual menu. Doing so will bring up the
Preferences dialog, from which you can pick the font and size of your choice. You should take care
to choose a fixed-width font for the Results, Viewer, Data Editor, and Do-file Editor windows. You
are not prevented from choosing other fonts, but if you do choose a proportional-width font, output
and numbers will not align as they should.
Changing color schemes

The Results and Viewer windows have color schemes that control the display of input, text,
results, errors, links, and highlighted text. Each has its color scheme set in the same fashion: you can
right-click on the window and select or design your own color scheme. The default setting for both
the Results window and the Viewer is the built-in Standard scheme, which uses a white background
and dark text. There are six other built-in schemes and three settings for custom schemes. The settings
for the Viewer affect all Viewer windows at once.
107
108 [ GSU ] 17 Setting font and window preferences
Managing multiple sets of preferences

Stata’s preferences are automatically saved when you exit Stata, and they are reloaded when Stata
is launched. However, sometimes you may wish to rearrange Stata’s windows and then revert to your
preferred arrangement of windows. You can do this by saving your preferences to a file and loading
them later. Any changes you make to Stata’s preferences after loading a preferences file do not affect
the file; the file remains untouched unless you specifically overwrite it.
To manage preferences, open the Edit > Preferences > Manage Preferences menu, and do any
of the following:
• Select Open Preferences... to open a saved preference file.
• Select Save Preferences... to save the current window arrangement and preferences to disk.
By default, these are saved in your .user prefs folder in your home directory. If you save
your preferences to this default folder, they will appear in the Stata > Preferences > Manage
Preferences menu the next time you view it.
• Select Factory Settings to restore all preferences to their original settings.
Closing and opening windows

You can close the Viewer, Graph, Do-file Editor, and Data Editor windows. If you want to open
a closed window, open the Window menu and select the desired window. You can cannot close the
Command window or the Results window.
18 Learning more about Stata
Where to go from here

You now know plenty enough to use Stata. There is still much, much more to learn, because Stata
is a rich environment for doing statistical analysis and data management. What should you do to
learn more?
• Get an interesting dataset and play with Stata.
a. Use the menus and dialog system to experiment with commands. Notice what commands
show up in the Results window. You will find that Stata’s simple and consistent command
syntax will make the commands easy to read so that you will know what you have done
and easy to remember so that typing some commands will be faster than using menus.
b. Play with graphs and the Graph Editor.
• If you venture into the Command window, you will find that many things will go faster. You
will also find that it is possible to make mistakes where you cannot understand why Stata is
balking.
a. Try help commandname or Help > Stata Command... and entering the command name.
b. Look at the command syntax and the examples in the help file, and compare them
with what you typed. Compare them closely: small typographical errors make commands
impossible for Stata to parse.
• Explore Stata by selecting Help > Search.... You will uncover many statistical routines that
could be of great use.
• Look through the Combined subject table of contents in the Glossary and Index.
• Read and work your way through the User’s Guide. It is designed to be read from cover to
cover, and it contains most of the information you need to become an expert Stata user. It is
well worth reading. If you are not this ambitious and instead prefer to sample the User’s Guide
and the references, there is some advice later in this chapter for you.
• Browse through the reference manuals to read about statistical methods you like to use, making
use of the links to jump to other topics. The reference manuals are not meant to be read from
cover to cover—they are meant to be referred to as you would an encyclopedia. You can find
the datasets used in the examples in the manuals by selecting File > Example Datasets... and
then clicking on Stata 13 manual datasets. Doing so will enable you to work through the
examples quickly.
• Stata has much information, including answers to frequently asked questions (FAQs), at
http://www.stata.com/support/faqs/.
• There are many useful links to Stata resources at http://www.stata.com/links/. Be sure to look
at these materials because many outstanding resources about Stata are listed here.
• Join Statalist, a listserver devoted to discussion of Stata and statistics.
• Read the official Stata blog Not Elsewhere Classified to read articles written by people at Stata
about all things Stata. You can find the Stata blog at http://blog.stata.com.
• Visit Stata on Facebook at http://facebook.com/statacorp, join Stata on Google+ at
https://plus.google.com/+stata/posts, and follow Stata on Twitter at http://twitter.com/stata to
keep up with Stata.
• Subscribe to the Stata Journal, which contains reviewed papers, regular columns, book reviews,
and other material of interest to researchers applying statistics in a variety of disciplines. Visit
http://www.stata-journal.com.
109
110 [ GSU ] 18 Learning more about Stata
• Many supplementary books about Stata are available. Visit the Stata bookstore at
http://www.stata.com/bookstore/.
• Take a Stata NetCourse R
. NetCourse 101 is an excellent choice for learning about Stata. See
http://www.stata.com/netcourse/ for course information and schedules.
• Attend a public training course taught by StataCorp at third-party sites. Visit
http://www.stata.com/training/public for course information and schedules.
• Watch Stata videos at http://www.youtube.com/user/statacorp.
Suggested reading from the User’s Guide and reference manuals

The User’s Guide is designed to be read from cover to cover. The reference manuals are designed
as references to be sampled when necessary.
Ideally, after reading this Getting Started manual, you should read the User’s Guide from cover
to cover, but you probably want to become at least somewhat proficient in Stata right away. Here is
a suggested reading list of sections from the User’s Guide and the reference manuals to help you on
your way to becoming a Stata expert.
This list covers fundamental features and points you to some less obvious features that you might
otherwise overlook.
Basic elements of Stata
[U] 11 Language syntax
[U] 12 Data
[U] 13 Functions and expressions
Data management
[U] 6 Managing memory
[U] 21 Entering and importing data
[D] import — Overview of importing data into Stata
[D] append — Append datasets
[D] merge — Merge datasets
[D] compress — Compress data in memory
Graphics
[G] Stata Graphics Reference Manual
Useful features that you might overlook

[U] 28 Using the Internet to keep up to date
[U] 16 Do-files
[U] 19 Immediate commands
[U] 23 Working with strings
[U] 24 Working with dates and times
[U] 25 Working with categorical data and factor variables
[U] 13.5 Accessing coefficients and standard errors
[U] 13.6 Accessing results from Stata commands
[U] 26 Overview of Stata estimation commands
[U] 20 Estimation and postestimation commands
[R] estimates — Save and manipulate estimation results
[ GSU ] 18 Learning more about Stata 111
Basic statistics
[R] anova — Analysis of variance and covariance
[R] ci — Confidence intervals for means, proportions, and counts
[R] correlate — Correlations (covariances) of variables or coefficients
[D] egen — Extensions to generate
[R] regress — Linear regression
[R] predict — Obtain predictions, residuals, etc., after estimation
[R] regress postestimation — Postestimation tools for regress
[R] test — Test linear hypotheses after estimation
[R] summarize — Summary statistics
[R] table — Flexible table of summary statistics
[R] tabulate oneway — One-way table of frequencies
[R] tabulate twoway — Two-way table of frequencies
[R] ttest — t tests (mean-comparison tests)
Matrices
[U] 14 Matrix expressions
[U] 18.5 Scalars and matrices
[M] Mata Reference Manual
Programming
[U] 16 Do-files
[U] 17 Ado-files
[U] 18 Programming Stata
[R] ml — Maximum likelihood estimation
[P] Stata Programming Reference Manual
[M] Mata Reference Manual
System values
[R] set — Overview of system parameters
[P] creturn — Return c-class values
Internet resources
The Stata website (http://www.stata.com) is a good place to get more information about Stata.
You will find answers to FAQs, ways to interact with other users, official Stata updates, and other
useful information. You can also subscribe to Statalist, a listserver devoted to discussion of Stata and
statistics.
You will also find information on Stata NetCourses R
, which are interactive courses offered over
the Internet that vary in length from a few weeks to eight weeks. Stata also offers in-person training
sessions. Visit the Stata website for more information.
At the website is the Stata Bookstore, which contains books that we feel may be of interest to
Stata users. Each book has a brief description written by a member of our technical staff explaining
why we think this book may be of interest.
We suggest that you take a quick look at the Stata website now. You can register your copy of
Stata online and request a free subscription to the Stata News.
112 [ GSU ] 18 Learning more about Stata
Visit http://www.stata-press.com for information on books, manuals, and journals published by

Stata Press. The datasets used in examples in the Stata manuals are available from the Stata Press
website.
Also visit http://www.stata-journal.com to read about the Stata Journal, a quarterly publication
containing articles about statistics, data analysis, teaching methods, and effective use of Stata’s
language.
Visit Stata’s official blog at http://blog.stata.com for news and advice related to the use of Stata.
The articles appearing in the blog are individually signed and are written by the same people who
develop, support, and sell Stata. The Stata Blog also has links to other blogs about Stata, written by
Stata users around the world.
Follow Stata on Facebook at http://facebook.com/statacorp, Twitter at http://twitter.com/stata,
and Google+ at https://plus.google.com/+stata/posts. These are good ways to stay up-to-the-minute
with the latest Stata information. Watch short example videos of using Stata on YouTube at
http://www.youtube.com/user/statacorp.
See [GSU] 19 Updating and extending Stata—Internet functionality for details on accessing
official Stata updates and free additions to Stata on the Stata website.
19 Updating and extending Stata—Internet functionality
Internet functionality in Stata

Stata works well with the Internet. Stata can use datasets and view remote help files as though
they were on your computer. Stata also can keep itself up to date (with your permission, of course).
Finally, you can install user-written commands, which are commands that extend Stata’s functionality.
These are commands that have been presented in the Stata Journal (SJ) or the Stata Technical Bulletin
(STB) or have simply been written and shared by the greater Stata community.
This chapter will show you how you can expand Stata’s horizons.
Using files from the Internet

Stata understands URLs as though they were local file locations. If you know of a file on the web
that you would like to use, be it a dataset, a graph, or a do-file, you can easily open it in Stata. Here
is a small example.
There are many datasets at http://www.stata-press.com/data/. Suppose that you would like to use
the census12 dataset used in [U] 11 Language syntax and that you know that its location is
http://www.stata-press.com/data/r13/census12.dta. Because you know that the command for opening
a dataset is use, you could type the following:

. use http://www.stata-press.com/data/r13/census12.dta
(1980 Census data by state)
. describe
Contains data from http://www.stata-press.com/data/r13/census12.dta
obs: 50 1980 Census data by state
vars: 7 6 Apr 2013 15:43
size: 1,950

state str14 %14s State

state2 str2 %-2s Two-letter state abbreviation
region str7 %9s Census region
pop long %10.0g Population
median_age float %9.2f Median age
marriage_rate float %9.0g
divorce_rate float %9.0g
Sorted by:

This functionality is everywhere in Stata. Any command that reads a file with a filename in its syntax
can use a web address as easily as a file that is stored on your computer.
This example used the HTTP protocol for retrieving the file. Stata also understands the HTTPS and
FTP protocols.
113
114 [ GSU ] 19 Updating and extending Stata—Internet functionality
Official Stata updates

By official Stata, we mean the pieces of Stata that are provided and supported by StataCorp. The
other and equally important pieces are the user-written additions published in the SJ, distributed over
Statalist, or distributed in other ways.
Stata can fetch both official updates and user-written programs from the Internet. Let’s start with
the official updates. StataCorp often releases updates to official Stata. These updates add new features
and, sometimes, fix bugs.
For you to install updates, you need to be running as superuser. You should exit all instances of
Stata, and then restart Stata by typing sudo xstata-mp, sudo xstata-se, sudo xstata, or sudo
xstata-sm, depending on the flavor of Stata you use.
To check whether there are any official Stata updates, either click on Help > Check for Updates
or type update query in the Command window. Regardless of which choice you make, Stata goes
to check for official updates. After it checks, it will show you your update status. If your copy of
Stata is already up to date you will be told. If your copy of Stata needs updating, you will be told,
and a link, Install available updates, will show up in your Results window. You can click on
this link or type update all and press Enter. In either case, Stata will download what is needed to
bring your copy of Stata up to date. Stata will need to restart after being updated, so it gives you a
chance to postpone the update in case there was something (such as saving the command history)
you wanted to do in the current session.
Troubleshooting note: If you do not have write permission for /usr/local/stata13, you cannot
install official updates in this way. You may still download the official updates, but you will need
to use the command-line version of update; see [U] 28 Using the Internet to keep up to date for
instructions.
Finding user-written programs by keyword

Stata has a built-in utility created specifically to search the Internet for user-written Stata programs.
You can access it by selecting Help > Search..., choosing Search net resources, and entering a
keyword in the field. Choosing Help > SJ and User-written Programs yields more specific choices
for searching. The utility searches all user-written programs on the Internet, including the entire
collection of SJ and STB programs. The results are displayed in the Viewer, and you can click to go
to any of the matches found.
For the syntax on how to use the equivalent search keywords, net command, see [R] search.
[ GSU ] 19 Updating and extending Stata—Internet functionality 115
Downloading user-written programs

Downloading user-written programs is easy. Start by selecting Help > SJ and User-written
Programs:
As the Viewer says, try Search... first.

Suppose that you were interested in finding more information or some user-written programs
involving cubic splines. You select Help > Search..., select Search all, type cubic spline in the
search box, and click on the OK button.
The first entry points to the built-in Stata command mkspline. You investigate this command and
find it interesting. You see that the next two entries point to some built-in routines in Mata. You
follow these links because Mata is not only intriguing but also fast. You see that the next link points
to an FAQ on UCLA’s website. The next two links point to articles in the SJ. Finally, you decide to
check the second of these links. It points to an article in the SJ, volume 12, number 3 (third quarter,
2012). You should click on the sg151 2 link, because it will go to the programs associated with this
article.
You will see that the package has three help files for three new commands. Click the
sg151 2/bspline.sthlp link to see if the bspline command looks interesting. If you decide
that you would like to install the command, click the Back button and click on the link click here
to install. If you decide that you would like to use some of the ancillary files—files that typically
help explain the workings of the command, you could download those, too. You do not need to
worry—doing so will not interfere in any way with your copy of Stata. We will show you how to
safely uninstall these programs shortly. That is all there is to installing a user-written package.
Now suppose that you decide that you would like to uninstall the package. Doing so is simple
enough: select Help > SJ and User-written Programs, and click on the List link. You should see
the following:
If you click on the one-line description of the program, you will see the full description of what
has been installed. Here is what you would see if you scroll to the bottom, with a different install
date, of course:
You can uninstall materials by clicking on click here to uninstall when you are looking at
the package description. Try it.
For information on downloading user-written programs by using the net command, see [R] net.
A Troubleshooting Stata
Contents
A.1 If Stata(GUI) and Stata(console) do not start . . . . . . . . . . . . . . . . . . . . . . . . . 120
A.2 If Stata(console) starts but Stata(GUI) does not . . . . . . . . . . . . . . . . . . . . . . . 121
A.3 Troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
A.1 If Stata(GUI) and Stata(console) do not start

If you have attempted to invoke Stata(GUI) by typing xstata, xstata-se, or xstata-mp at the
Unix prompt and it has failed, attempt to invoke Stata(console) by typing stata, stata-se, or
stata-mp at the Unix prompt. If Stata(console) fails, continue here. If Stata(console) starts without
problems, see the next section of this chapter.
You tried to start Stata and it refused; Stata or your operating system presented a message explaining
that something is wrong. Here are the possibilities:
cannot find Stata directory
Stata first checks in /usr/local/stata13 and then checks in /usr/local/stata to find the
license file. If Stata does not find the license in either of these locations, it looks in every directory
in the Unix path. If you receive this message, most likely the directory where Stata is installed is
not in your path. You need to add this directory to your path.
Cannot find license file
This message means just what it says; nothing is too seriously wrong. Stata simply could not find
the license file it was looking for. The two most common reasons for this are that you did not
complete the installation process or Stata is not installed where it should be.
Did you enter the codes printed on your paper license to unlock Stata? If not, go back and complete
the initialization procedure.
If you have unlocked Stata, perhaps it is not in your path or for some reason the license file is
not in the Stata directory.
Error opening or reading the file
Something is distinctly wrong for purely technical reasons. Stata found the file that it was looking
for, but either the operating system refused to let Stata open it or there was an I/O error.
The stata.lic file could have incorrect permissions. Verify that stata.lic is in the directory
where Stata is installed, likely /usr/local/stata13 and that everybody has been granted read
permission. To change the permissions, become superuser by logging in as root, using su, or
sudo, and type chmod a+r /usr/local/stata13/stata.lic.
About the only other way this situation could arise would be a hard-disk error. Stata technical
support will be able to help you diagnose the problem; see [U] 3.9 Technical support.
License not applicable
Stata has determined that you have a valid Stata license, but the license does not apply to the
version of Stata that you are trying to run.
120
[ GSU ] A Troubleshooting Stata 121
The most common reason for this message is that you have a license for Stata/IC but you are
trying to run Stata/SE or Stata/MP, or you have a license for Small Stata but you are trying to run
Stata/IC, Stata/SE, or Stata/MP. If any of these is the case, reinstall Stata, making sure to choose
the appropriate flavor.
Other messages
The other messages indicate that Stata thinks you are attempting to do something that you are
not licensed to do. Most commonly, you are attempting to run Stata over a network when you
do not have a network license, but there are many other alternatives. There are two possibilities:
either you really are attempting to do something that you are not licensed to do or Stata is wrong.
In either case, you are going to have to contact us. Your license can be upgraded, or if Stata is
wrong, we can provide codes to make Stata stop thinking that you are violating the license; see
[U] 3.9 Technical support.
A.2 If Stata(console) starts but Stata(GUI) does not

Trouble with libraries
Stata, like many other programs designed for Unix machines, needs certain system libraries to run.
Most of the standard library routines that Stata needs are included in the Stata binary. However,
Stata does rely on a few external libraries. For example, Stata assumes that your system will have
the standard C library available. Stata(GUI) assumes that you have the X Windows libraries as
well. These libraries are often located in different places on different implementations of Unix.
For example, under Linux, the standard C libraries can be found in /lib, whereas the X Windows
libraries are in /usr/X11R6/lib; under Solaris, the standard libraries are in /usr/lib, whereas
X libraries are in /usr/openwin/lib. The operating system needs to know where to find the
libraries that Stata needs to run. The Unix environment variable LD LIBRARY PATH tells the
operating system where to find libraries. If you get an error message that says something like
ld.so.1: xstata: fatal: some library.so.#: can’t open file
the likely reason is that the operating system cannot find the necessary libraries. Stata does not
rely on any non-standard libraries; you can rest assured that the libraries you need are on your
system. You should look for the library in question on your system and make sure the environment
variable LD LIBRARY PATH includes the path to the directory where the library in question is
located. Your system administrator may be able to help with this task.
Setting the DISPLAY environment variable
Sometimes when executing Stata in a networked environment, Stata(GUI) will produce the error
message
You need X Windows for this version of Stata.
This means that Stata has not found the DISPLAY environment variable. You need to set the
DISPLAY variable to be the screen on which you want Stata(GUI) to appear. For example, in csh,
type setenv DISPLAY machine:0.0.
xhost permissions
Another related error message can arise with Stata(GUI). When Stata is being run in a networked
environment, the computer on which Stata(GUI) is actually executing (the x-client in X Windows
parlance) may not have permission to draw on the screen of x-server, the computer on which you
have asked Stata to draw. Then you may see the following:
Xlib: connection to machine name:0.0 refused by server
Xlib: Client is not authorized to connect to Server
xhost: unable to open display
122 [ GSU ] A Troubleshooting Stata
On the machine on which you want to display Stata(GUI), type

% xhost +client machine
This will give the client permission to draw on the server’s screen.
Getting more help
If you continue to experience problems invoking Stata(GUI), please see the Unix FAQs on our
website at http://www.stata.com/support/faqs/unix/, or contact Stata Technical Support.
A.3 Troubleshooting tips

If you had trouble with the installation of Stata, it could be because you have a recent copy of
Unix that will not allow you to run applications from a DVD drive. Type df -l in your Unix terminal
to see what local devices are mounted; one should look like the Stata DVD. For example, you could
see something like
$ df -l
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda6 23054660 5528268 16336380 26% /
/dev/hdc 274158 274158 0 100% /media/Stata
/dev/hdc is the device name, whereas the /media/Stata is the mount point.
If you see something indicating that the Stata DVD is successfully mounted, you need to see if you
are being prevented from running applications directly from the DVD. Type mount to get information
about any mounted file systems. Somewhere on the list, you should see information about your DVD.
Continuing with the above example, you should see your device name and mount point in the output:
$ mount
output omitted
/dev/hdc on /media/Stata type iso9660 (ro,noexec,nosuid,nodev,uid=220) [STATA]
If you see the term noexec appear, you are not allowed to run applications from a DVD. Your best
course of action is to copy everything from the Stata DVD to a temporary directory and run the
installation from there. Substitute your mount point for /media/Stata below.
$ mkdir /tmp/statainstall
$ cp -r /media/Stata /tmp/statainstall
$ mkdir /usr/local/stata13
$ cd /usr/local/stata13
$ sudo /tmp/statainstall/Stata/install
After you have Stata running and initialized, you can delete the temporary directory
/tmp/statainstall.
If you are still having problems installing or if you have any other troubles, please see the Unix
FAQs on our website at http://www.stata.com/support/faqs/unix/. If this does not help, contact Stata
Technical Support. Please gather all the information you can about your system, including your
computer model and the type and version of Unix that you are using. Finally, we need your Stata
serial number and the revision date of your version of Stata. Include them if you email, and know
them if you call. You can obtain them by typing the about command in Stata’s Command window.
about lets you know everything about your copy of Stata, including the version and the date it was
produced.
B Advanced Stata usage
Contents
B.1 Executing commands every time Stata is started . . . . . . . . . . . . . . . . . . . . . . 123
B.2 Advanced starting of Stata for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
B.3 Stata batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
B.4 Using X Windows remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
B.5 Summary of environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
B.6 Memory size considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
B.1 Executing commands every time Stata is started

Stata looks for the file profile.do when it is invoked and, if it finds it, executes the commands
in it. Stata looks for profile.do first in the directory where Stata is installed, then in the current
directory, then along your path, and finally along the ado-path (see [P] sysdir). We recommend that
you put profile.do in your bin directory $HOME/bin.
Say that every time you start Stata, you would like to start a dated log for the session. In
$HOME/bin, create the file profile.do containing this rather odd-looking command (the command
will be explained at the end of this session):
log using ‘: display %tCCCYY-NN-DD-HH-MM-SS ///
Clock("‘c(current_date)’ ‘c(current_time)’","DMYhms")’, ///
name(default_log_file)
When you invoke Stata, the usual opening appears but with the following additional command,
which will be executed:
running /home/mydir/bin/profile.do ...
How does the command work? Let’s work from the inside out:
• c(current date) and c(current time) are local system macros containing the current
date and current time. See [P] creturn for more information.
• The left (‘) and right (’) quotes around the local macros expand them. See [P] macro for a
full explanation.
• The Clock() function uses the resulting date string and the date mask "DMYhms" to create a
datetime number Stata understands. See [D] datetime.
• The format %tCCCYY-NN-DD-HH-MM-SS formats this number in year-month-day-hour-minute-
second form because this will make the files sort nicely. See [D] datetime display formats for
the details.
• The odd-looking ‘: display ...’ allows the formatted date to be used directly in the command
as the file name. This is the advanced concept of an in-line expansion of an extended macro
function. You can see more in [P] macro.
• The log using command starts a log file, such as shown in [GSU] 16 Saving and printing
results by using logs.
• The name option gives the log file the internal name default log file so that it will not
likely conflict with other log files. See [R] log for details.
• Finally, the /// notations are continuation comments so that the three separate lines are
interpreted as a single command. See [P] comments for more about comments.
123
124 [ GSU ] B Advanced Stata usage
There are many advanced Stata programming concepts in this one single command!
profile.do is treated just as any other do-file once it is executed; results are just the same as if
you had started Stata and then typed run profile.do. The only special thing about profile.do
is that Stata looks for it and runs it automatically.
System administrators might also find sysprofile.do useful. This file is handled in the same
way as profile.do, except that Stata first looks for sysprofile.do. If that file is found, Stata
will execute any commands it contains. After that, Stata will look for profile.do and, if that file
is found, execute the commands in it.
One example of how sysprofile.do might be useful would be when system administrators want
to change the path to one of Stata’s system directories. Here sysprofile.do could be created to
contain the command
sysdir set SITE "/opt/stata/ado"
See [U] 16 Do-files for an explanation of do-files. They are nothing more than ASCII text files
containing sequences of commands for Stata to execute.
B.2 Advanced starting of Stata for Unix

The syntax of the command to start Stata(GUI) is

xstata -option -option . . . stata command
The syntax of the command to start Stata(console) is

stata -option -option . . . stata command
If you have Stata/SE, the commands are xstata-se and stata-se. If you have Stata/MP, the
commands are xstata-mp and stata-mp.
The allowable options are
Option Result
-b set background (batch) mode and log in ASCII text (console only)
-h display usage diagram
-q suppress logo and initialization messages
-s set background (batch) mode and log in SMCL (console only)
Typing stata -h does not start Stata, but just shows the syntax diagram for invoking Stata.
The -q option starts Stata, but it suppresses all the initialization messages, including the Stata
logo.
The -b and -s options specify batch mode; see [GSU] B.3 Stata batch mode.
[ GSU ] B Advanced Stata usage 125
B.3 Stata batch mode

Suppose you had a do-file named bigjob.do. If you want to use Stata in batch mode, we suggest
using Stata(console). Typing
% stata -b do bigjob
tells Stata to execute the commands in bigjob.do, suppress all screen output, and route the output
to bigjob.log in the same directory.
% stata -s do bigjob
to bigjob.smcl in the same directory.
You can also run the above examples in the background by typing
% stata -b do bigjob &
% stata -s do bigjob &
You may also use redirection, but this is not recommended:

% stata < bigjob.do > bigjob.log &
Warning: Redirection will not work if your do-file contains either the #delimit commands or comment
delimiters (/* and */, //, or ///). It also cannot create SMCL output. Hence, we recommend using
options directly: stata -s do bigjob & or stata -b do bigjob &.
Note: Stata runs profile.do before doing bigjob.do, just as it would if you were working
interactively.
B.4 Using X Windows remotely

Suppose that you are sitting in front of a computer named local and that you wish to run Stata
on a computer named neighbor.
1. Tell X Windows on local to allow neighbor to use its display by typing xhost +neighbor.
2. Be sure that you have set X Windows’ DISPLAY environment variable on neighbor to contain
local:0.0. X requires this. Important: this variable must be set on neighbor.
Having done this, Stata should work:
local% xhost +neighbor
local% ssh neighbor
neighbor% setenv DISPLAY local:0.0
neighbor% xstata
At this point, either Stata launches, or you see

Xlib: connection to "local:0.0" refused by server
Xlib: Client is not authorized to connect to Server
Here you will have to get help from your network administrator. Proper authorizations have not been
given, and these problems have nothing to do with Stata.
To make this process simpler, you may also be able to use the -X flag when invoking ssh:
local% ssh -X neighbor
neighbor% xstata
Whether this works depends on your Unix installations. The first series of commands should always
work.
126 [ GSU ] B Advanced Stata usage
B.5 Summary of environment variables
Environment variable Description

HOME User’s home directory. Default is the directory specified in /etc/passwd.
PATH Unix executable search path.
SHELL What to execute when users try to shell out of Stata. Default is /bin/sh.
S ADO Sets Stata’s ado-path.
STATATERM Used only if you want to use a different termcap or terminfo entry
from what is in your TERM environment variable.
STATATMP Sets Stata’s temporary directory. Default is /tmp.
STATA PREF DIR Location Stata checks for preferences. If not set, Stata will use
a subdirectory of $HOME/.stata13/. If you use Stata(console),
preferences will be saved in $HOME/.stata13/console/. If you use
Stata(GUI), preferences will stored in a subdirectory based on your
DISPLAY environment variable, such as $HOME/.stata13/:0.0/.
B.6 Memory size considerations

Beginning with Stata 12, memory management in Stata became automatic—there is no longer any
requirement to manually request memory for Stata when you know you will be using a large dataset.
For details on efficiency tweaks needed by a very few Stata users, look at [D] memory.
C Stata manual pages for Unix
Contents
conren — Set the color, etc., of Stata(console) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
stata — Stata invocation command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
127
Title
conren — Set the color, etc., of Stata(console)
Syntax
High-level commands
conren
conren style #
conren ul #
conren test
conren clear
Low-level commands
set conren
set conren clear

set conren sf | bf | it result | txt | text | input | error |

link | hilite char char . . .

set conren ulon | uloff char char . . .

set conren reset char char . . .

set conren off char char . . .
where char is

any character | < # >
Note
This command concerns Stata for Unix only and, in particular, the Stata you launch by typing stata
or stata-se, not xstata or xstata-se, also known as Stata(console) or the non-GUI version of
Stata.
Description
conren and set conren may improve display of the output on your screen. Some terminals, for
instance, can display colors, but Stata may not know that your terminal has that capability. Some
terminals have multiple intensities or boldfaces. Some terminals can underline. The high-level conren
command lets you set a display style and/or underlining scheme from among a selection of predefined
settings.
128
conren — Set the color, etc., of Stata(console) 129
conren style followed by a scheme number sets color and font codes on the basis of the
underlying scheme.
conren ul followed by an underlining scheme number sets the codes that allow underlining.
conren with no arguments displays a message explaining the command and telling the range of
style and underlining scheme numbers available.
conren test displays three columns of output in sf (standard face) font, bf (boldface) font, and
it (italics) font, showing the assignment of colors with and without underlining.
conren clear clears all the currently defined display style and underlining definitions.
The low-level set conren command lets you view and set specific display and underlining codes.
set conren displays a list of the currently defined display codes.
set conren clear clears all codes.
set conren followed by a font type (bf, sf, or it), a display context (result, text, input,
error, link, or hilite) and a series of space-separated characters sets the code for the specified
font type and display context. If the font type is omitted, the code is set to the same specified
code for all three font types.
set conren ulon and set conren uloff set the codes for turning underlining on and off.
set conren reset sets the code that will turn off all display and underlining codes.
set conren off sets the code used by Stata when it exits and returns control back to the operating
system.
When Stata launches, it is as if you have typed

. conren clear
which is equivalent to the low-level command

. set conren clear
meaning that Stata is to assume that your monitor cannot display different colors, intensities, or
underlining. Stata makes this assumption because, were Stata to assume otherwise and your terminal
could not provide the capability, the result could look really bad. Thus, a few minutes of playing
around can be well worth the effort, and you do not have to be a computer expert to do set these
codes. You cannot hurt anything permanently by typing the wrong command.
The next-to-worst thing that can happen is that Stata’s output will look so bad that you cannot
even read it, and then just exit Stata. Stata will be fine the next time you launch it.
The worst thing that can happen is that your window/screen/terminal will look so garbled that you
will have to close it and open a new one (or, if it really is a separate terminal, turn it off and turn it
back on).
Once you are happy with your settings, you can put the set conren commands in your profile.do
so that they are executed at the start of every Stata session.
130 conren — Set the color, etc., of Stata(console)
Finding a color scheme

First, let’s try various color schemes. What will work and look good depends on your termi-
nal/monitor and whether you are using a white or black background. (We really prefer a black
background for Stata, and if you are using a white background, we recommend that you try black
someday. We prefer a black background for Stata because, by default, it uses green and yellow for
most output, and these colors do not show up well on a light-colored background. Switching the
background color, however, is something that you will have to take up with Unix, not Stata.)
First, type the following:
. conren
Doing so first tells you the number of possible display schemes and underlining schemes available.
There are a few underlining schemes and many more display schemes. Some of these schemes were
designed with black backgrounds in mind, whereas others were designed for white backgrounds. We
suggest that you first select a display style scheme, and then after finding the scheme you like, explore
the possible underlining schemes.
You would type
. conren style 1
to try display style scheme 1. conren style and conren ul automatically run conren test so
that you can see the result on your screen. If the result is obviously bad, move on and try another
scheme. If the resulting color scheme might be reasonable, try out Stata and see what you think.
Try several commands, and look at a few help files to see if the selected display style scheme is
appropriate. You can always return to the default with
. conren clear
which may be hard if you cannot even see what you are typing. Remember, if things are really bad,
just type exit and then restart Stata.
Try all the prerecorded schemes to determine which one you like best.
Can your terminal underline?

Type conren test to look at the various output types. Is the word underlined truly
underlined — with the underlining on the same line and actually touching the characters — or is
it instead more crudely rendered with a string of dashes underneath, on a second line?
If the word underlined truly is underlined, skip this section; evidently Stata has already figured
out that your terminal can underline and is doing that.
Sometimes, Stata cannot figure that out for itself. Let’s see if you can underline. Type
. conren ul 1
Now look at the output from conren test again. Is underlined underlined or just a mess? If it is
a mess, you can remove the underlining codes (while leaving the display style codes untouched) by
typing
. conren ul 0
You can now try the other available underlining schemes to see if they work any better for you.
conren — Set the color, etc., of Stata(console) 131
If you had success

So, let’s say that you discovered that what works best for you is
. conren style 4
. conren ul 1
and you just had no success with boldface at all. The next time you enter Stata, if you want the
prettier look, you will have to type those two commands. To avoid having to do that, create a file
profile.do and put those two lines in that file. Actually, we suggest that you put the lines in the
file as
quietly conren style 4
quietly conren ul 1
because, if you also use Stata in batch mode, using the quietly option will prevent odd messages
from appearing when Stata starts.
If you did not have success

Well, now you really need to be technical. It is possible to make Stata’s output look prettier if
you know the escape sequences to cause special effects on your terminal.
Pretend that the codes for your terminal to turn underlining on and off were Esc-[4m and Esc-[24m.
You could tell Stata that by typing
. set conren ulon <27> [ 4 m
. set conren uloff <27> [ 2 4 m
Escape has the decimal code 27, and you can type decimal codes by enclosing them in less-than
and greater-than signs. You can just type regular characters. Remember, however, that you must type
at least one space between each pair of characters.
All the features can be set in this way. If you type
. set conren
Stata will report what is currently set.
Also see
[P] smcl — Stata Markup and Control Language
Title
stata — Stata invocation command
Syntax

xstata-mp -option -option . . . stata command

xstata-se -option -option . . . stata command

xstata -option -option . . . stata command

stata-mp -option -option . . . stata command

stata-se -option -option . . . stata command

stata -option -option . . . stata command
where the options are

-h display usage diagram
-q suppress logo and initialization messages
-s set background (batch) mode and log in SMCL (console only)
-b set background (batch) mode and log in ASCII text (console only)
Description
xstata-mp starts the GUI version of Stata/MP. xstata-se starts the GUI version of Stata/SE.
xstata starts the GUI version of Stata/IC.
stata-mp starts the console version of Stata/MP. stata-se starts the console version of Stata/SE.
stata starts the console version of Stata/IC.
Remarks and examples

Here are the explanations for the startup options:
Typing stata -h does not enter Stata, but instead shows the syntax diagram for invoking Stata.
The -q option suppresses all the initialization messages, including the Stata logo, when Stata is
invoked.
The -s and -b options are for users who do not wish to run Stata interactively. Typing
% stata -s do bigjob
to bigjob.smcl. Typing
% stata -b do bigjob
132
stata — Stata invocation command 133
to bigjob.log.
You may also use redirection (but it is not recommended):
% stata < bigjob.do > bigjob.log &
Warning: redirection will not work if your do-file contains either the #delimit commands or comment
delimiters (/* and */, //, or ///). It also cannot create SMCL output. Hence, we recommend using
options directly: stata -s do bigjob & or stata -b do bigjob &.
If you do use the first method, bear in mind that Stata automatically begins a log. If the stata com-
mand is of the form

do | run path filename .suffix
the output is routed to filename.smcl in the current directory if you typed -s and to filename.log in
the current directory if you typed -b. Otherwise, the output is routed to stata.smcl or stata.log.
In either case, if the log file already exists, it is silently erased before starting.
Whether you use options or redirection, whenever Stata is running without a terminal, it sets
c(mode) to contain batch. If Stata is running in interactive mode, c(mode) is set to be empty. See
[P] creturn.
Technical note
Many users log in to Unix computers from Windows or Mac computers. If you are one of these
users, there are several third-party packages that allow you to display X Windows graphics on Windows
or Mac computers.
Subject index commands,
compared with menus, 21
This is the subject index for the Getting Started with learning, 29, 109–111
Stata for Unix manual. Readers may also want to consult comments, see log files, commenting
the combined subject index (and the combined author conren command, 128–131
index) in the Glossary and Index. contextual menu, 23
Graph window, 99
A Review window, 25
Variables window, 26–27
ado command, 33 Viewer window, 33
arithmetic operators, see operators, arithmetic copying,
data, see data, copying
B graphs, see graphs, copying
text, see text, copying
batch mode, 125 correlate command, 14
blog, see Stata blog creating variables, see variables, creating
Break, 80
button, 24
browse command, 2, 6, 7, 57
D
button, data,
Break, 24, 80 copying, 49, 61
Clear more condition, 24, 79 tips, 50
Data Editor (Browse), 2, 24, 45 entering, 46–50
Data Editor (Edit), 24, 44, 46 graphing, 15–20
Do, 92, also see button, Execute (do) importing, see importing data
Do-file Editor, 24, 92 labeling, 65–70
Execute (do), 93, 97 listing, 71–80
Execute Quietly (run), 97 pasting, 49, 61
Graph, 16, 24 sorting, 51
Graph Editor, 99 strings, 48
Log, 22, 24, 103 Data Editor, 2–3, 44–57
Open, 24 attach value labels, 52
Print, 24 browse mode, 57
Properties, 45 toolbar button, 24
Reset, 18 cell navigation, 48
Run, see button, Execute Quietly (run) color coding, 2, 47
Save, 24 contextual menus, 45
Show File in Viewer, 97 create value labels, 51
Variables, 45 creating variables, 52
Variables Manager, 24 cursor location box, 46–48, 51
Viewer, 24, 30 date
by() option, 13, 17 editing, 54–55
by prefix, 12, 14, 21 formats, 54–55
by/if/in tab, 7, 12, 14, 28 mask, 55
edit mode toolbar button, 24
edit within cell, 48
C
empty columns, 47
cd command, 29 empty rows, 47
clear command, 88 enter data by column, 47
clear more condition, see more condition, clear enter data by row, 46
cmdlog command, 105 entering data, 46–50
codebook command, 4–6, 36 filtering, 9, 56
command history, 25 fonts, 107
command syntax, 21–22 hiding variables, 56
Command window, 23, 25 limiting exposure, 55–57
movement, 45–46
135
136 Subject index
Data Editor, continued Do-file Editor, continued

opening, 46 inserting a file, 96
reordering variables, 56 matching parentheses, 96
right-clicking, 45 next bookmark, 92
snapshots, 53–54 previous bookmark, 92
sorting, 45, 51 select entire line, 96
tips, 55, 64 syntax highlighting, 93
toolbar, 44 toggle bookmark, 92
Tools menu, 50–57 toolbar button, 24
value labels, 51 Tools menu, 97
when to browse, 55 Execute (do), 97
data management, 2–8 Execute Quietly (run), 97
data type, see variables, data type Show File in Viewer, 97
dataset, 4 View menu, 97
changing, 50–57 drop command, 88–89
notes, 3 dropping variables, see variables, dropping
opening, 42 dummy variable, see indicator variable
saving, 42
saving in old format, 42
structure, 2, 3
E
dates, editing, see Data Editor, date editing edit command, 56
db command, 29 editing data, see Data Editor
decode command, 81 editing dates, see Data Editor, date editing
deleting variables, see variables, dropping editing do-file, see Do-file Editor
describe command, 3, 65–70 egen command, 81
with short option, 46 encode command, 81
descriptive statistics, 8–15 environment variables, 126
destring command, 81 equality, 11–12, 75
dialogs, 27–29 examples,
accessing from Command window, 29 dialogs, 4, 5, 7, 8, 10–16, 18, 28, 98
Cancel button, 29 graphs, 15–20, 98, 100
Copy button, 29 help, 35–38
Help button, 29 if qualifier, 6, 7, 11, 56–57, 73–76, 89–90
OK button, 28 in qualifier, 77
Reset button, 29 menus, 1, 3–5, 7, 8, 10–16, 18, 28–29, 98
saving commands, 97 varlist, 56, 71–73
Submit button, 29 excel, import subcommand, 62, 64
Variables field, 5, 7 exp, see expressions
directory, working, see working directory expressions, 73, 81
disclosure control, 27
display format, see variables, display format
displaying graphs, see graphs, schemes
F
Do, Facebook, 109, 112
button, see button, Do filenames, quotes, 42
menu item, 97 fitted values, see predict command
do-file, 92–95, 97, 105–106, 123 fonts,
editing, see Do-file Editor changing in graphs, see graphs, schemes
tips, 94 changing in one graph, see Graph Editor
troubleshooting, 93–95 changing in windows, see preferences, font
Do-file Editor, 91–97 preferences, see preferences, font
balancing braces, 96 functions, 81
buttons, 91–92
changing case, 96
editing help files, 97 G
editing tools, 96 generate command, 17, 18, 20, 82–87
fonts, 107 tips, 85
getting Review window contents, 26 troubleshooting, 84
Subject index 137
generating variables, see variables, creating import excel command, 62, 64

Google+, 109 import sasxport command, 62, 64
Graph Editor, 100–102 importing data, 61–64
abilities, 101 comma-delimited, 62
closing, see Graph Editor, stopping copying and pasting, 61, 64
contextual toolbar, 100–101 fixed-format data, 64
experimentation, 101 paste special, 50
Grid Edit tool, 101 spreadsheet, 50, 62, 64
Object Browser, 101 tab-delimited, 62
recording, 101 tips, 64
starting, 100 importing data,
stopping, 101 importing data
tools, 101 ODBC, see ODBC
Undo button, 101 SAS, see SAS
graph setup, see graphs, schemes in qualifier, 21, 71, 77, 88
Graph window, 16, 99 in qualifier
contextual menu, 99 examples, see examples, in qualifier
right-clicking, 99–100 indicator variable, 6, 17, 85
toolbar button, 24 generating, 82
Graphical User Interface, see GUI infile command, 62, 64
graphs, infix command, 62, 64
copying, 99 Internet, 113–119
editing, see Graph Editor installing programs, see programs, downloading and
overlaid, 18–20 installing
printing, 20, 99 resources, 109–112
renaming, 99 searching, 114–116
right-clicking, 99 using remote files, 113
saving, 99
schemes, 107
K
subgraphs, 16
graphs, keep command, 88, 90
examples, see examples, graphs
GUI, 23–41, 44–57, 61, 91–102, 107–108, 113–119,
125 L
label command, 67
H label data command, 67
label define command, 68, 70
help command, 39 label values command, 67, 70
help for command, 33 label variable command, 20, 67
help system, 35–41 labels,
FAQs, 35 data, 3, 67–69
links, 36 value, 3–5, 10, 12, 67, 69–70
menu, 35 confusing with string variable, 76
search dialog, 35 why needed, 6
searching, 35–41, 114–116 variable, 4, 5, 67–69
tips, 38 line, twoway subcommand, 19
videos, 35, 41 linear regression, see regression, linear
hypothesis testing, 13–14 list command, 7, 63, 71–80
listing data, see data, listing
I loading data, see dataset, opening
Log button, 24
identifier variable, 5 log command, 103–105
if qualifier, 6, 7, 11–12, 21, 71, 73–76, 83, 88 log files, 22, 103–106
troubleshooting, 75–76 appending, 103
if qualifier commenting, 104
examples, see examples, if qualifier contents, 104
import delimited command, 62–64 keeping just commands, 105
138 Subject index
log files, continued P

multiple open at once, 104
overwriting, 103 pasting,
plain text, 103, 105 data, see data, pasting
printing, 105 text, see text, pasting
rerunning commands, 105–106 PATH, 126
SMCL, 103, 105 PDF, 105
starting, 103 PDF documentation, 35, 37, 39
tips, 105 poisson command, 28
translating formats, 103, 105 postestimation commands, 18
types, 105 precision, 66
viewing, 105 predict command, 18
logical preferences, 107–108
expression, 73–75 Clipboard, 107
operators, see operators, logical font, 107–108
Graph window, 107
loading, 108
M managing, 108
saving, 108
median, 9 window, 107–108
memory, 6, 42, 66, 126 prefix command, 12, 21
allocation, 126 printing, 24
menus, 27 contents of Viewer, 33
compared with commands, 21 graphs, 99
examples, see examples, menus output, 105
missing() function, 7, 57, 74 toolbar button, 24
missing values, 3, 4, 7, 10, 47, 51, 73–74, 82–83, 87 profile.do, 123
extended, 51 Progect Manager, 97
more condition, 3, 5, 24, 79 programs,
downloading and installing, 114–117
N uninstalling, 117
Project Manager, 96
net command, 33 projects, 97
NetCourses, 110 Properties window, 2, 23, 48
Not Elsewhere Classified, see Stata blog hiding, 27
notes, revealing, 27
managing, 59–60
timestamps, 60
numlist, 77 R
reading list, see Stata reading list
O recording sessions, see log files
reference manuals, 39
observations, 2 regress command, 18, 21
ODBC, 64 regression,
odbc command, 62, 64 linear, 17–21, 95
one-way table, see table, one-way Poisson, 28
open, 44 relational operators, see operators, relational
Open toolbar button, 24 replace command, 81–85
opening a dataset, see dataset, opening Results window, 1, 16, 23, 25
operators, color scheme, 107
arithmetic, 81 fonts, 107
logical, 73, 75, 81 searching, 25
relational, 73, 81 Review window, 2, 23, 25–26
string, 87 contextual menu, 25
options, 8, 21, 37, 71, 77 filtering, 25
output, printing and saving, see log files hiding errors, 25
Subject index 139
Review window, continued Stata Journal, 35–36, 40–41, 109, 112, 113
reusing commands, 25, 52–53 Stata News, 111
right-click, 25, 106 Stata Technical Bulletin, 40–41, 113
saving contents, 26 Stata(GUI), see GUI
sending contents to Do-file Editor, 26 stata-mp command, 132
tip, 106 stata-se command, 132
Run button, see button, Run status bar, 29
STB, see Stata Technical Bulletin
storage type, see variables, data type
S string variable, see variables, string
sample session, 1–22 strings, 86–87
SAS, 62, 64 quoting, 76
sasxport, import subcommand, 62, 64 strpos() function, 87
save command, 29, 42–43 substr() function, 87
Save toolbar button, 24 summarize command, 4, 8, 11–12, 21
saveold command, 42 syntax, 37, 71–78
saving abbreviations, 71
data, see dataset, saving diagram, 21
output, see log files list command, 71
scatter, twoway subcommand, 15–17, 19 syntax note, 2, 5, 7–14, 16–17, 21
search command, 33, 39 sysprofile.do, 124
searching help system, see help system, searching sysuse command, 1
Show File in Viewer button, see button, Show File in
Viewer
SMCL, 32, 92, 97, 103
T
Stata table,
batch mode, 125, 132–133 one-way, 10, 13
blog, 109, 112 two-way, 11
bookstore, 110 tabulate command, 10–13
command line options, 132 text,
console, 1, 113, 128–131 copying, 91
datasets available, 109, 113 pasting, 91
executing commands at startup, 123 text variables, see variables, string
FAQs, 109 toolbar, main, 24
Graph Editor, see Graph Editor tooltip, 24
learning more, 109–112 tostring command, 81
Markup and Control Language, see SMCL training, see Stata training
NetCourses, 110, 111 troubleshooting, 120–122
output, 1 installation, 122
Press, 111 updates, see updates, troubleshooting
public training courses, 110 X windows, 121–122
reading list, 110–111 ttest command, 13
starting, 132 Twitter, 109, 112
starting remotely, 125 twoway line command, 19
starts with an error, see troubleshooting twoway scatter command, 15–17, 19
startup options, 124 two-way table, see table, two-way
Statalist, 109 type command, 33
training, 110, 111
troubleshooting, see troubleshooting
updating, see updates U
user interface, see GUI update command, 33
videos, 41, 110 updates, 33, 114
won’t start, see troubleshooting troubleshooting, 114
working directory, see working directory use command, 42
stata command, 132 User’s Guide, 109
140 Subject index
V Viewer, continued
links
value labels, creating and managing, 51 clicking, 32
variables, 2 middle-clicking, 32
allowable names, 49 Shift+clicking, 32
creating, 52, 81–87 log files, 105
data type, 4–6, 66, 82 navigating, 33
display format, 4, 66 new window, 32
dropping, 27, 59, 88–89 opening, 30
formatting, 48 preferences, 33
generating, see variables, creating printing, 33
keeping, 26, 59 printing log files, 105
missing values, see missing values right-clicking, 33
name, 4, 66 selecting one Viewer, 32
abbreviating, 63, 71–73 tabs, 33
auto-completion, 25 toolbar button, 24, 30
naming, 48 viewing
renaming, 48 current log, 32
storage type, see variables, data type logs, 32
string, 4, 5, 86–87 remote files, 32
confusing with value labels, 76 text files, 32
text, see variables, string
Variables Manager, 58–60
contextual menus, 59 W
creating varlists, 59
windows, 23
dropping variables, 59
closing, 108
filtering variables, 58
cycle, 23
keeping variables, 59
opening, 108
notes, 59–60
revealing, 23
restore sort order, 59
working directory, 29
right-clicking, 59
toolbar button, 24
Variable pane, 58–59 X
Variable Properties pane, 59
X Windows, 16, 125
Variables window, 2, 18, 23, 26–27
X windows
clicking, 26
troubleshooting, see troubleshooting, X windows
contextual menu, 26–27
XML, 64
filtering, 26
xmluse command, 62, 64
hiding, 27
xstata command, 132
revealing, 27
xstata-mp command, 132
varlist, 5, 21, 71, 88
xstata-se command, 132
varlist
examples, see examples, varlist
videos, see Stata videos Y
view command, 33
Viewer, 30–34 YouTube videos, see Stata videos
Also see button, 37
buttons, 31
color scheme, 107
commands, 33
contextual menu, 33
Dialog button, 37
Find bar, 31
fonts, 107
Jump To button, 37

Getting Started With Stata: For Unix Release 13

Uploaded by

Copyright:

Available Formats

Getting Started With Stata: For Unix Release 13

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Getting Started With Stata: For Unix Release 13

Uploaded by

Copyright:

Available Formats

GETTING STARTED WITH STATA

A Stata Press Publication

The suggested citation for this software is

1 Introducing Stata—sample session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

[GSM] Getting Started with Stata for Mac

[M ] Mata Reference Manual

Using this manual

Stata’s two interfaces

Simple data management

storage display value

make str18 %-18s Make and Model

Sorted by: foreign

trunk 74 13.75676 4.277404 5 23

gear_ratio 74 3.014865 .4562871 2.19 3.89

make Make and Model

type: string (str18), but longest is str17

foreign Car type

type: numeric (byte)

rep78 Repair Record 1978

type: numeric (int)

Domestic 52 70.27 70.27

mpg 52 19.82692 4.743297 12 34

mpg 22 24.77273 6.611187 14 41

-> foreign = Domestic

mpg 52 19.82692 4.743297 12 34

-> foreign = Foreign

mpg 22 24.77273 6.611187 14 41

Domestic 19.826923 4.7432972 52

Total 21.297297 5.7855032 74

A simple hypothesis test

Domestic 52 19.82692 .657777 4.743297 18.50638 21.14747

combined 74 21.2973 .6725511 5.785503 19.9569 22.63769

diff -4.945804 1.362162 -7.661225 -2.230384

diff = mean(Domestic) - mean(Foreign) t = -3.6308

Descriptive statistics—correlation matrices

-> foreign = Domestic

-> foreign = Foreign

2,000 3,000 4,000 5,000

The command and the associated graph are

2,000 3,000 4,000 5,000

2,000 3,000 4,000 5,000

Model fitting: Linear regression

mpg = β0 + β1 weight + β2 weight2 + β3 foreign + 

mpg Coef. Std. Err. t P>|t| [95% Conf. Interval]

weight -.0165729 .0039692 -4.18 0.000 -.0244892 -.0086567

−0.0165729 weight + 1.59 × 10−6 wtsq − 2.2035 foreign + 56.53884

3. Create the graph for mpg versus weight:

2,000 3,000 4,000 5,000 2,000 3,000 4,000 5,000

2,000 3,000 4,000 5,000

2,000 3,000 4,000 5,000

gp100m Coef. Std. Err. t P>|t| [95% Conf. Interval]

weight .0016254 .0001183 13.74 0.000 .0013896 .0018612

Commands versus menus

Some general rules:

command by itself is valid: summarize

Keeping track of your work

Save saves the Stata dataset currently in memory to disk.

The Command window

The Results window

mpg = β0 + β1 weight + β2 weight2 + β3 foreign +