RESEARCH GUIDE
Choosing Statistical Software for Research
Method Fit, Data Size and Reproducibility
Choosing statistical software for research starts from the method and the data and not from the brand: the right platform fits the models your question needs, copes with the size of your data, matches what your field and collaborators use and lets another person reproduce the result. The sections below take those four tests in turn.
Software choice is a methodological decision as well as a practical one, because the platform determines which models are available as tested routines, how an analysis is documented and who can verify it. Standard analyses such as group comparisons, regression, factor analysis and survival models can be run in more than one platform, so the choice usually turns on the less common requirement: a specialized model, a very large dataset, a field or regulatory convention, a collaborator’s files or the need to rerun the analysis from a script. OnlineSPSS, a specialist statistical consultancy for academic, clinical and professional research, helps researchers match the platform to the planned models, sets analyses up so they can be rerun from syntax or scripts and can check key estimates in a second platform; every platform covered is listed on the Software page, and the research decisions remain the researcher’s.
RESEARCH SITUATIONS
Six Research Situations and What Usually Decides
The same method can be run in several programs, so the situation around the project, and not the method alone, usually settles which program is practical.
Thesis in a Teaching Department Supervisors can check only work they can open, so the program the department teaches and supports, such as IBM SPSS, often decides before methods do.
Laboratory Experiments Small designed experiments need planned comparisons, curve fitting and publication graphs, so the program the lab already shares files in, such as GraphPad Prism, usually decides.
Clinical or Sponsor-Funded Studies Protocols, sponsors and reviewers may name the environment, so documented versions, validated procedures and a full record of every step decide, as in SAS.
Economics and Policy Panel Data Panel and survey estimators, clustered standard errors and the field's replication norms point to tested routines for those models, as in Stata or R.
Large or Linked Data Data that exceed memory or arrive as linked files make hardware and scripted processing the deciding factors, which can point to Python or a database before modeling begins.
A New or Specialized Model When a model exists only in a few packages, such as a growth mixture model or a recent estimator, the available tested routine decides, as with Mplus or R packages.
WORKING STYLES
Menus, Commands or Code: Three Ways of Working
Three working styles explain most differences between programs, and each row shows where they usually differ and not a ranking; for named programs side by side, see Statistical Analysis Tools Compared.
| Feature | Menu-driven packages | Command-driven packages | Programming languages |
|---|---|---|---|
| How an analysis is run | Dialogs choose the procedure and its options | Typed commands, run singly or from a file | Scripts that combine functions and packages |
| Record kept | Saved syntax, or steps documented by hand | Do-files or programs, plus output logs | Scripts that rerun from raw data to tables |
| Starting effort | Often the lowest to begin | Moderate, with compact syntax to learn | Highest at the start, lower on each repeat |
| Access to newer methods | Mainly through vendor releases and modules | Official updates plus user-written commands | Often earliest, through packages of varying maturity |
| Who can check the work | Colleagues holding the same program and edition | Colleagues holding the license and the files | Anyone with the language, package versions and script |
| Typical risk | Unrecorded clicks that cannot be repeated | Silent defaults and version-specific commands | Package updates or unvetted code changing results |
KEY PLANNING DECISIONS
Questions That Decide the Platform
These six questions are asked in order, and the earlier ones usually narrow the field so far that the later ones decide between two options and not eleven.
Does a Tested Routine Exist? Name the model first, because some models are implemented in only a few platforms or in a few well-tested packages, and the available routine decides what can be fitted.
How Large Are the Data? Check whether the data fit comfortably in the memory of the machine in use, since very large datasets may need other tools or a database, which depends on the hardware and version.
What Does Your Field Expect? Look at the journals, funders or regulators in your area, because some settings expect analysis programs in a particular language or the use of a documented, validated environment.
Who Must Open the Files? List supervisors, coauthors and reviewers who will inspect the work, and weigh which formats they can open and which versions of the software they hold.
Must the Analysis Be Rerun? Decide whether a script or syntax file is required, since a record of every step lets anyone reproduce the tables, and steps taken only through menus must be documented separately.
What Will You Keep Using? Consider access after the project, such as a license tied to an institution, and the time you can spend learning a new tool against the value of the result.
COMMON ISSUES
Mistakes Researchers Make When Picking Software
Software problems rarely appear as errors, they appear as results that cannot be reproduced or defended, so the points below are checked before the first model is run.
Choosing Before the Method A platform picked first can force a simpler model than the question needs, or a long detour later, so the intended models are listed before the tool is chosen.
Trusting Defaults Defaults such as the variance estimator, the handling of missing values or the optimizer start values can differ between programs, so the options behind each result are recorded.
Versions Not Recorded Results can change between versions of a program or of a package, so the version of the software and of each package is written down and reported.
Switching Mid-Project Unchecked Moving an analysis to another platform without refitting a known model in both can hide translation errors, so key estimates are reproduced in each before the move is final.
Counting Codes as Statistics Qualitative software organizes coding, and counts of coded segments are descriptive, so they are tested only when the sampling and the coding unit support it.
Equating Cost With Validity A license type, free or commercial, does not make results correct, and validity rests on documented methods and checks against known results and not on the price.
REPORTING
Reporting the Software in a Methods Section
Naming the software is a small part of reproducibility, and it is the part that readers and reviewers most often find missing.
A methods section names the software and its version, and for R or Python it lists the packages used with their versions, so that the analysis can be repeated. APA 7 gives formats for citing software and packages, and many journals ask for a code or data availability statement. When syntax or scripts are shared, they are saved in plain text and annotated with what each step does and which data file it expects.
SOFTWARE
Each Platform in More Detail
Once the questions above point to a platform, its own page shows which analyses are carried out in it and what the work starts from, so this guide does not need to repeat it.
ANALYSIS SERVICES
Support Before and After the Platform Is Chosen
The platform is easiest to settle while the plan is still open, and support follows it with the analysis in the chosen platform, the reporting and a check on work already done.
Research Planning & Study Design
The intended models, the data requirements and the platform that follows from them, settled in the analysis plan before any data are cleaned.
Quantitative Data Analysis
The analysis run in the platform chosen for your models, with the syntax or script that lets each table be regenerated from your data.
Results Reporting & Interpretation
Methods wording that names the software, its version and the options used, with tables and figures prepared to the style your journal requires.
Independent Statistical Review
Existing output is examined for the options and defaults behind each number, and key estimates can be checked by refitting the model in another platform.
FREQUENTLY ASKED QUESTIONS
Questions About Choosing Statistical Software for Research
Researchers weighing platforms ask about open-source reliability, the value of learning to program, what to record for reproducibility and when data size matters.
Is free software as reliable as commercial software?
Reliability depends on whether the routine has been validated and the workflow documented, not on the price of the license. Open-source packages differ in how widely they are used and maintained, and commercial packages have defaults that researchers should know and report. For either, the check is whether a known dataset reproduces known results and whether the version and options are recorded.
Is it worth learning a programming language for one project?
It depends on whether the methods you need are available in software you already know, and on whether you will analyze data again after this project. For standard analyses, a menu-driven package with saved syntax gives a record that can be rerun, while R or Python repay the learning time when a model exists only as a package, when the analysis will be repeated on new data or when graphics and reports must be produced automatically.
What should I record so that my analysis can be repeated?
Record the software and package versions, the data file or version used, every step that changed the data, the model specification and options, and any random seed for simulations or resampling. A script or syntax file that runs from raw data to final tables carries most of this, and a short readme describes the rest.
When does data size start to matter for the choice?
It matters when the data no longer fit comfortably in the memory of the machine being used, or when the processing becomes too slow to iterate on. This depends on the hardware, the software version and the type of analysis, and many survey, clinical and experimental datasets are well within the reach of every common platform.
How do you protect my research data and confidentiality?
Whichever platform an analysis is carried out in, your data and project details are handled confidentially. Project information is not published, and researcher names and institutions are not used publicly without permission. An NDA is available where required and can be arranged before sensitive materials are shared. Read more about confidentiality and data security.
What happens when I request an assessment, and how long does it take?
You share your research question, design and relevant materials, such as a protocol, an analysis plan or a dataset, and a statistically trained Research Coordinator reviews the request and responds the same day. The analysis, deliverables, timeline and one fixed project fee are then confirmed before any work begins, so the timeline follows from the agreed scope.
Still have a question? Find more answers in our full FAQ.
NEXT STEP
Settle the Platform
Before the Analysis
Share the question, the data you hold and the software your team or field expects. The reply names the platform that fits your models and what the analysis in it would involve.
No Commitment Required
Strictly Confidential
Fixed Project Fee
In-House PhD-Level Statisticians
Same-Day Response
Serving Researchers Since 2014