@alias prompt = sansserif
-@include doc/tut.texi
+@include tut.texi
@node Using PSPP
-@chapter Using PSPP
+@chapter Using @pspp{}
-PSPP is a tool for the statistical analysis of sampled data.
+@pspp{} is a tool for the statistical analysis of sampled data.
You can use it to discover patterns in the data,
to explain differences in one subset of data in terms of another subset
and to find out
whether certain beliefs about the data are justified.
This chapter does not attempt to introduce the theory behind the
statistical analysis,
-but it shows how such analysis can be performed using PSPP.
+but it shows how such analysis can be performed using @pspp{}.
-For the purposes of this tutorial, it is assumed that you are using PSPP in its
+For the purposes of this tutorial, it is assumed that you are using @pspp{} in its
interactive mode from the command line.
However, the example commands can also be typed into a file and executed in
a post-hoc mode by typing @samp{pspp @var{filename}} at a shell prompt,
executed.
Whichever method you choose, the syntax is identical.
-When using the interactive method, PSPP tells you that it's waiting for your
+When using the interactive method, @pspp{} tells you that it's waiting for your
data with a string like @prompt{PSPP>} or @prompt{data>}.
In the examples of this chapter, whenever you see text like this, it
-indicates the prompt displayed by PSPP, @emph{not} something that you
+indicates the prompt displayed by @pspp{}, @emph{not} something that you
should type.
Throughout this chapter reference is made to a number of sample data files.
So that you can try the examples for yourself,
-you should have received these files along with your copy of PSPP.
+you should have received these files along with your copy of @pspp{}.@c
@footnote{These files contain purely fictitious data. They should not be used
for research purposes.}
@note{Normally these files are installed in the directory
@section Preparation of Data Files
-Before analysis can commence, the data must be loaded into PSPP and
-arranged such that both PSPP and humans can understand what
+Before analysis can commence, the data must be loaded into @pspp{} and
+arranged such that both @pspp{} and humans can understand what
the data represents.
There are two aspects of data:
@item
The words @samp{data list list} are an example of the @cmd{DATA LIST}
command. @xref{DATA LIST}.
-It tells PSPP to prepare for reading data.
+It tells @pspp{} to prepare for reading data.
The word @samp{list} intentionally appears twice.
The first occurrence is part of the @cmd{DATA LIST} call,
whilst the second
-tells PSPP that the data is to be read as free format data with
+tells @pspp{} that the data is to be read as free format data with
one record per line.
@item
@item
-Normally, PSPP displays the prompt @prompt{PSPP>} whenever it's
+Normally, @pspp{} displays the prompt @prompt{PSPP>} whenever it's
expecting a command.
However, when it's expecting data, the prompt changes to @prompt{data>}
so that you know to enter data and not a command.
@item
At the end of every command there is a terminating @samp{.} which tells
-PSPP that the end of a command has been encountered.
+@pspp{} that the end of a command has been encountered.
You should not enter @samp{.} when data is expected (@i{ie.} when
the @prompt{data>} prompt is current) since it is appropriate only for
terminating commands.
For full details refer to @pxref{DATA LIST}.
@node Reading data from a pre-prepared PSPP file
-@subsection Reading data from a pre-prepared PSPP file
+@subsection Reading data from a pre-prepared @pspp{} file
@cindex system files
@vindex GET
-When working with other PSPP users, or users of other software which
-uses the PSPP data format, you may be given the data in
-a pre-prepared PSPP file.
+When working with other @pspp{} users, or users of other software which
+uses the @pspp{} data format, you may be given the data in
+a pre-prepared @pspp{} file.
Such files contain not only the data, but the variable definitions,
along with their formats, labels and other meta-data.
Conventionally, these files (sometimes called ``system'' files)
@node Saving data to a PSPP file.
-@subsection Saving data to a PSPP file.
+@subsection Saving data to a @pspp{} file.
@cindex saving
@vindex SAVE
If you want to save your data, along with the variable definitions so
-that you or other PSPP users can use it later, you can do this with
+that you or other @pspp{} users can use it later, you can do this with
the @cmd{SAVE} command.
The following syntax will save the existing data and variables to a
@cindex errors, in data
Data from real sources is rarely error free.
-PSPP has a number of procedures which can be used to help
+@pspp{} has a number of procedures which can be used to help
identify data which might be incorrect.
The @cmd{DESCRIPTIVES} command (@pxref{DESCRIPTIVES}) is used to generate
If possible, suspect data should be checked and re-measured.
However, this may not always be feasible, in which case the researcher may
decide to disregard these values.
-PSPP has a feature whereby data can assume the special value `SYSMIS', and
+@pspp{} has a feature whereby data can assume the special value `SYSMIS', and
will be disregarded in future analysis. @xref{Missing Observations}.
You can set the two suspect values to the `SYSMIS' value using the @cmd{RECODE}
command.
@example
-PSPP> recode height (179 = SYSMIS).
-PSPP> recode weight (LOWEST THRU 0 = SYSMIS).
+@pspp{}> recode height (179 = SYSMIS).
+@pspp{}> recode weight (LOWEST THRU 0 = SYSMIS).
@end example
@noindent
The first command says that for any observation which has a
The sample file @file{hotel.sav} comprises data gathered from a
customer satisfaction survey of clients at a particular hotel.
In @ref{reliability}, this file is loaded for analysis.
-The line @code{display dictionary.} tells PSPP to display the
+The line @code{display dictionary.} tells @pspp{} to display the
variables and associated data.
The output from this command has been omitted from the example for the sake of clarity, but
you will notice that each of the variables
One would therefore expect the values of these variables (after recoding)
to closely follow one another, and we can test that with the @cmd{RELIABILITY}
command (@pxref{RELIABILITY}).
-@ref{reliability} shows a PSPP session where the user (after recoding
+@ref{reliability} shows a @pspp{} session where the user (after recoding
negatively scaled variables) requests reliability statistics for
@var{v1}, @var{v3} and @var{v5}.
1.2 RELIABILITY. Reliability Statistics
#================#==========#
-#Cronbach's Alpha#N of items#
+#Cronbach's Alpha#N of Items#
#================#==========#
# .86# 3#
#================#==========#
or
whether the mean of a dataset significantly differs from a particular
value.
-This section presents just some of the possible tests that PSPP offers.
+This section presents just some of the possible tests that @pspp{} offers.
The researcher starts by making a @dfn{null hypothesis}.
Often this is a hypothesis which he suspects to be false.
For example, if he suspects that @var{A} is greater than @var{B} he will
-state the null hypothesis as @math{ @var{A} = @var{B}}.
-@footnote{This example assumes that is it already proven that @var{B} is
+state the null hypothesis as @math{ @var{A} = @var{B}}.@c
+@footnote{This example assumes that it is already proven that @var{B} is
not greater than @var{A}.}
The @dfn{p-value} is a recurring concept in hypothesis testing.
If the variances are equal, then a more powerful form of the T-test can be used.
However if it is unsafe to assume equal variances,
then an alternative calculation is necessary.
-PSPP performs both calculations.
+@pspp{} performs both calculations.
For the @var{height} variable, the output shows the significance of the
Levene test to be 0.33 which means there is a
projects / pspp / blobdiff