1 PSPP is a program for statistical analysis of sampled data. It
2 interprets commands in the SPSS language and produces tabular output
3 in ASCII, PostScript, or HTML format.
5 PSPP development is ongoing. It already supports a large subset of
6 SPSS's transformation language. Its statistical procedure support is
7 currently limited, but growing.
9 Instructions for installation are in INSTALL. Before you install
10 PSPP, you will need to install certain prerequisites:
12 * An ANSI C compiler and tool chain.
14 * The GNU Scientific Library (libgsl), version 1.6 or later,
15 including libgslcblas included with GSL.
17 * Perl, version 5.005_03 or later. (Perl is required during build
18 but not after installation.)
20 * pkg-config (only if you need to regenerate configure after
21 modifying configure.ac).
23 * Optional: libncurses. Without it, PSPP will assume it is
24 running in an 80x25 terminal.
26 * Optional: libreadline and libhistory. Without them, interactive
27 command editing and history features will be disabled.
29 * Optional: libplot (from GNU plotutils). Without it,
30 graphing features will not work. If you do not have it
31 installed, you must run `configure' with --without-libplot.
33 * Optional: GTK+ version 2.6.0 or later, plus libglade 2.0 or
34 later. Without them, the GUI will not be built. If you do not
35 have these installed, you must run `configure' with
38 * Optional: Texinfo 4.7 or later, if you want to build the
39 documentation in PostScript or PDF format.
41 For information on differences from previous versions, please see file
42 NEWS. Full documentation on PSPP's language can be found in the doc/
45 Source code for the latest release of PSPP is available at
46 ftp://ftp.gnu.org/pub/gnu/pspp/. Older versions may be obtained from
47 ftp://alpha.gnu.org/gnu/pspp/. Development sources are available from
48 CVS at http://savannah.gnu.org/projects/pspp
50 Questions and comments about using PSPP may be sent to pspp-users@gnu.org.
51 Bug reports may be filed at http://savannah.gnu.org/bugs/?group=pspp
52 or emailed to bug-gnu-pspp@gnu.org. (We prefer the web-based system
53 because it makes it more difficult for us to lose track of bugs.)
55 The long term goals for PSPP are ambitious. We wish to provide the
56 following support to users:
58 * All of the SPSS transformation language. PSPP already
59 supports a large subset of it.
61 * All the statistical procedures that someone is willing to
62 implement, whether they exist in SPSS or not. Currently,
63 statistical support is limited, but growing.
65 * Compatibility with SPSS syntax, including compatibility with
66 known bugs and warts, where it makes sense. We also provide
67 an "enhanced" mode in certain cases where PSPP can output
68 better results that may surprise SPSS users.
70 * Friendly textual and graphical interfaces. PSPP does not do
71 a good job of this yet.
73 * Attractive output, including graphs, in a variety of human-
74 and machine-readable formats. PSPP currently produces
75 output in ASCII, PostScript, and HTML formats. We will
76 enhance PSPP's output formatting in the future.
78 * Good documentation. Currently the PSPP manual describes its
79 language completely, but we would like to add information on
80 how to select statistical procedures and interpret their
83 * Efficient support for very large data sets. For procedures
84 where it is practical, we wish to efficiently support data
85 sets many times larger than physical memory. The framework
86 for this feature is already in place, but it has not been
87 tuned or extensively tested.
89 Over the long term, we also wish to provide support to developers who
90 wish to extend PSPP with new statistical procedures, by supplying the
93 * Easy-to-use support for parsing language syntax. Currently,
94 parsing is done by writing "recursive descent" code by hand,
95 with some support for automated parsing of the most common
96 constructs. We wish to improve the situation by supplying a
97 more complete and flexible parser generator.
99 * Easy-to-use support for producing attractive output.
100 Currently, output is done by writing code to explicitly fill
101 in table cells with data. We should be able to supply a
102 more convenient interface that also allows for providing
103 machine-readable output.
105 * Eventually, a plug-in interface for procedures. Over the
106 short term, the interface between the PSPP core and
107 statistical procedures is evolving quickly enough that a
108 plug-in model does not make sense. Over the long term, it
109 may make sense to introduce plug-ins.