projects
/
pspp
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
feddb0d
)
Fix minor typos in documentation
author
John Darrington
<john@darrington.wattle.id.au>
Fri, 9 Jan 2015 08:50:42 +0000
(09:50 +0100)
committer
John Darrington
<john@darrington.wattle.id.au>
Fri, 9 Jan 2015 08:55:49 +0000
(09:55 +0100)
doc/statistics.texi
patch
|
blob
|
history
diff --git
a/doc/statistics.texi
b/doc/statistics.texi
index f17a9ece9cfe00e7e1c160ab26497ff647b605b9..789e37bc9591a9f56bb09361c6a4ddc1fb0160ce 100644
(file)
--- a/
doc/statistics.texi
+++ b/
doc/statistics.texi
@@
-255,7
+255,7
@@
factors which tell @pspp{} how to break down the analysis for each
dependent variable.
Following the dependent variables, factors may be specified.
dependent variable.
Following the dependent variables, factors may be specified.
-The factors (if desired) should be prece
e
ded by a single @subcmd{BY} keyword.
+The factors (if desired) should be preceded by a single @subcmd{BY} keyword.
The format for each factor is
@display
@var{factorvar} [BY @var{subfactorvar}].
The format for each factor is
@display
@var{factorvar} [BY @var{subfactorvar}].
@@
-318,10
+318,10
@@
If the @subcmd{/COMPARE} subcommand is omitted, then @pspp{} behaves as if
The @subcmd{ID} subcommand is relevant only if @subcmd{/PLOT=BOXPLOT} or
@subcmd{/STATISTICS=EXTREME} has been given.
The @subcmd{ID} subcommand is relevant only if @subcmd{/PLOT=BOXPLOT} or
@subcmd{/STATISTICS=EXTREME} has been given.
-If given, it shoul
e
provide the name of a variable which is to be used
+If given, it shoul
d
provide the name of a variable which is to be used
to labels extreme values and outliers.
Numeric or string variables are permissible.
to labels extreme values and outliers.
Numeric or string variables are permissible.
-If the @subcmd{ID} subcommand is not given, then the casenumber will be used for
+If the @subcmd{ID} subcommand is not given, then the case
number will be used for
labelling.
The @subcmd{CINTERVAL} subcommand specifies the confidence interval to use in
labelling.
The @subcmd{CINTERVAL} subcommand specifies the confidence interval to use in
@@
-415,15
+415,16
@@
GRAPH
/SCATTERPLOT = @var{height} WITH @var{weight} BY @var{gender}.
@end example
/SCATTERPLOT = @var{height} WITH @var{weight} BY @var{gender}.
@end example
-This example will produce a scatterplot where
height is plotted versus weight
. Depending
-on the value of the
gender
variable, the colour of the datapoint is different. With
-this plot it is possible to analyze gender differences for
height vs. weight
relation.
+This example will produce a scatterplot where
@var{height} is plotted versus @var{weight}
. Depending
+on the value of the
@var{gender}
variable, the colour of the datapoint is different. With
+this plot it is possible to analyze gender differences for
@var{height} vs.@: @var{weight}
relation.
@cindex histogram
The subcommand @subcmd{HISTOGRAM} produces a histogram. Only one variable is allowed for
@cindex histogram
The subcommand @subcmd{HISTOGRAM} produces a histogram. Only one variable is allowed for
-the histogram plot. For an alternative method to produce histograms @pxref{EXAMINE}. The
-following example produces a histogram plot for variable weigth.
+the histogram plot.
+For an alternative method to produce histograms @pxref{EXAMINE}. The
+following example produces a histogram plot for the variable @var{weight}.
@example
GRAPH
@example
GRAPH
@@
-1137,7
+1138,7
@@
outside the specified range are excluded from the analysis.
The @subcmd{/EXPECTED} subcommand specifies the expected values of each
category.
There must be exactly one non-zero expected value, for each observed
The @subcmd{/EXPECTED} subcommand specifies the expected values of each
category.
There must be exactly one non-zero expected value, for each observed
-category, or the @subcmd{EQUAL} keywor
k
must be specified.
+category, or the @subcmd{EQUAL} keywor
d
must be specified.
You may use the notation @subcmd{@var{n}*@var{f}} to specify @var{n}
consecutive expected categories all taking a frequency of @var{f}.
The frequencies given are proportions, not absolute frequencies. The
You may use the notation @subcmd{@var{n}*@var{f}} to specify @var{n}
consecutive expected categories all taking a frequency of @var{f}.
The frequencies given are proportions, not absolute frequencies. The
@@
-1388,7
+1389,7
@@
of variable preceding @code{WITH} against variable following
The @subcmd{/WILCOXON} subcommand tests for differences between medians of the
variables listed.
The test does not make any assumptions about the variances of the samples.
The @subcmd{/WILCOXON} subcommand tests for differences between medians of the
variables listed.
The test does not make any assumptions about the variances of the samples.
-It does however assume that the distribution is symetrical.
+It does however assume that the distribution is sym
m
etrical.
If the @subcmd{WITH} keyword is omitted, then tests for all
combinations of the listed variables are performed.
If the @subcmd{WITH} keyword is omitted, then tests for all
combinations of the listed variables are performed.
@@
-1552,7
+1553,7
@@
The list of variables must be followed by the @subcmd{BY} keyword and
the name of the independent (or factor) variable.
You can use the @subcmd{STATISTICS} subcommand to tell @pspp{} to display
the name of the independent (or factor) variable.
You can use the @subcmd{STATISTICS} subcommand to tell @pspp{} to display
-ancill
i
ary information. The options accepted are:
+ancillary information. The options accepted are:
@itemize
@item DESCRIPTIVES
Displays descriptive statistics about the groups factored by the independent
@itemize
@item DESCRIPTIVES
Displays descriptive statistics about the groups factored by the independent
@@
-1724,7
+1725,7
@@
RELIABILITY
@end display
@cindex Cronbach's Alpha
@end display
@cindex Cronbach's Alpha
-The @cmd{RELIABILTY} command performs reliability analysis on the data.
+The @cmd{RELIABIL
I
TY} command performs reliability analysis on the data.
The @subcmd{VARIABLES} subcommand is required. It determines the set of variables
upon which analysis is to be performed.
The @subcmd{VARIABLES} subcommand is required. It determines the set of variables
upon which analysis is to be performed.