statacons is a set of tools for the SCons build-system to allow running Stata projects. It does not require changes to existing code, is correct (no unnecessary rebuilds), extensible via Python, and git-friendly.
With data analysis projects it can be difficult to know what needs to be rebuilt when code changes (either because the there are many dependencies to track or it involves multiple contributors) and some tasks take a long time, making full-rebuilds costly. "Build systems" solve this by allowing the user to define how task inputs generate ouputs (for SCons, using SConstruct files) and tracking file changes to know what must be rebuilt. Thinks of this as a more robust way to specify a project's "master" run script. The SConstruct provides an easy view for what happens in a projects.
Citation: Guiteras, Raymond, Ahnjeong Kim, Brian Quistorff and Clayson Shumway, "statacons: An SCons-based build tool for Stata," The Stata Journal, 23(1):149-196, March 2023, doi:10.1177/1536867X231162032.
The Project Web Page at https://bquistorff.github.io/statacons/index.html hosts or links to all statacons resources, including
- The final pre-publication version of the paper: Guiteras, Raymond, Ahnjeong Kim, Brian Quistorff and Clayson Shumway, "statacons: An SCons-based build tool for Stata," CEnREP Working Paper 22-001, May 2022, https://go.ncsu.edu/cenrep-wp-22-001. PDF
- The Installation Guide: https://bquistorff.github.io/statacons/installation.html.
- The Online Appendices:
- Online Appendix A: Other Advanced Features
- A.1 SConscripts and Hierarchical Builds
- A.2 Parallel Builds
- Online Appendix B: Compiling a PDF
- Online Appendix A: Other Advanced Features
- A web tutorial based on Software Carpentry's
makelesson: https://bquistorff.github.io/statacons/swc.html - The project Wiki Page with additional advanced features, a troubleshooting guide, ideas for future improvements, and fixes for common errors (user contributions welcome): https://github.com/bquistorff/statacons/wiki
- Documentation for
statacons,stataconsign, andpystatacons - The MetaArXiV site archiving all pre-publication drafts of the paper: https://osf.io/preprints/metaarxiv/qesx6/.
- The OSF site archiving all versions of the software and replication code and data: https://osf.io/gbh4m/
See the Installation Guide: https://bquistorff.github.io/statacons/installation.html.
We have tested statacons with Stata versions 16, 17, 18, 19 (including StataNow 18 and 19), Stata flavors / editions IC/BE, SE and MP, on Windows, Mac and Unix, with Python 3.6, 3.8, 3.10, 3.11, 3.13 and SCons 4.3, 4.4, 4.5, 4.9 and 4.10, although not all combinations of these. SCons 4.5+ requires statacons version 3.0.1+.
Requires: Stata 16 or later; Python 3.6 or later (3.8 or later required for some advanced options); python packages pystatacons, scons (SCons 4.3 or later required), and on Windows pywin32.
If you install user-written Stata packages to a folder that is local to a project (for example, for consistency across users on a shared project), you should be sure that you also install statacons to your default ado/plus directory.
To update the statacons Stata package to the latest version, enter the following in Stata:
net install statacons, from(https://raw.github.com/bquistorff/statacons/main/) force replace
As above, if you install user-written Stata packages to a folder that is local to a project (for example, for consistency across users on a shared project), you should be sure that you also update statacons in your default ado/plus directory.
This will update all the core program files (statacons.ado, statacons.ado, complete_datasignature.ado, runscons.py, sconsign-script.py, sconstruct_fns.py) and the help files as necessary, but not the pystatacons Python package.
To update the pystatacons Python package to the latest version, enter the following at the appropriate Python prompt:
pip install --upgrade pystatacons
If you are working from behind a firewall or on an otherwise restricted machine, you may not be able to use net install. To install statacons manually, see https://github.com/bquistorff/statacons/wiki/Manual-installation.
- A Stata
stataconscommand to runscons(a Python package/script) from inside of Stata so that one does not have to use the system terminal. - A Python
pystataconspackage to aid in writing SCons build scripts, calledSConstructfiles. It provides (a) an SCons build environment that can automatically find most Stata installations, (b) aStataBuilder()method that takes care of running Stata in batch-mode, and checking the output for errors, (c) smart checking of Stata.dtafiles to know when their content atually changes (and not just their internal timestamp), and (d) a simple configuration system to over-ride package defaults - Optional ancillary files: sample
SConstructfile to get started, sample configuration files to override package defaults (a git-versionableconfig_project.iniand a not-to-versionconfig_local.ini), and some worked-examples with more functionality.
Suppose your project has a "master.do" file to run scripts:
do dataprep.do /* uses input.dta to generate input-cleaned.dta */
do analysis.do /* uses input-cleaned.dta to generate results.dta */You can re-write this as an SConstruct file:
import pystatacons
env = pystatacons.init_env()
env.StataBuild(do_file="dataprep.do", target=["input-cleaned.dta"], depends=["input.dta"])
env.StataBuild(do_file="analysis.do", target=["results.dta"], depends=["input-cleaned.dta"])You can build your project from the terminal using scons or from Stata using statacons. Output from the latter would be
. statacons
scons: Reading SConscript files ...
Using 'Strict' custom_datasignature.
Calculates timestamp-independent checksum of dataset, including all metadata.
Edit use_custom_datasignature in config_project.ini to change.
(other options are DataOnly, VVLabelsOnly, False)
scons: done reading SConscript files.
scons: Building targets ...
Computed dta-signature: <path>\input.dta
stata_run(["input-cleaned.dta"], ["dataprep.do"])
Running: StataMP-64.exe /e do "dataprep.do"
Computed dta-signature: <path>\input-cleaned.dta
stata_run(["results.dta"], ["analysis.do"])
Running: StataMP-64.exe /e do "analysis.do"
Computed dta-signature: <path>\results.dta
scons: done building targets.
If you modify dataprep.do, running scons will re-execute that file, then check if input-cleaned.dta actually changed to decide if analysis.do needs to be run also (see the section below for details). If a git pull updates lots of scripts, then a simple scons command will only rebuild what is necessary. If you execute scripts directly in Stata (i.e., not using statacons) then we provide helpful tools to ensure that running scons won't re-run scripts you've already ran (see our 'content-timestamp-newer' Decider).
For more details about general SCons usage and SConstruct files, see the SCons help. For more details about our specific additions to SCons, see our WP.
Our included complete_datasignature Stata command creates file signatures for .dta files that do not depend on the embedded timestamp, but optionally can depend on variable and value labels or other metadata.
The scons default is to use an MD5 signature. Because .dta files include an embedded timestamp, MD5 signatures will change every time a .dta file is rebuilt even if the data have not changed. Stata's datasignature command produces a signature that does not depend on the timestamp but also ignores metadata such as variable values and labels. complete_datasignature gives the user control over the inputs to the signature: data only (Stata's datasignature); data plus variable and value labels; data plus all metadata (variable and value labels, notes, characteristics); scons default MD5.