How tplinderoth/popgenomicstools works
Project type and purpose
• This is not a web or mobile app but a CLI “toolkit” of population‐genetics programs. Each .cpp or script corresponds to a standalone command‐line utility (e.g., relateStats, dxyWindow, betaAFOutlier.R, selkit, etc.). The purpose is to perform various population‐genetic and selection‐analysis tasks on input files (pedigrees, relatedness matrices, allele‐frequency files, VCFs, etc.).
File structure
• Top‐level files:
• Makefile – build orchestration for all C++ tools
• LICENSE, .gitignore, README.md – project metadata
• Matrix.h, StatDist.cpp/h – a core numerical library for matrix operations and statistical distributions
• selkit.cpp/h – core of the selkit toolbox
• Multiple “Window” .cpp tools: dxyWindow.cpp, fstWindow.cpp, hetWindow.cpp, ihsWindow.cpp, xpehhWindow.cpp
• stand‐alone utilities: relateStats.cpp/h, betaAFOutlier.R, pafAlleles.cpp, ngsMisc.pl
• No “frontend” or web‐service directories. Everything is invoked from the CLI.
Extract architecture insights from the README
• All C++ programs are compiled via Makefile with g++ -O3.
• The R and Perl scripts are interpreted, not compiled.
• selkit depends on bgzip‐indexed VCFs; betaAFOutlier.R uses Rscript.
• Inputs and outputs are file‐based; there are no network calls or persistent services.
Elements
• Makefile → Compiler → Executables
• Core Lib → C++ Tools
• selkit Lib → selkit Executable
• Input Files → Tools → Output Files
• C++ executables in a third
• Scripts (R/Perl) in a fourth
• Data stores (input/output files) as parallelograms
Detail without overthinking
• Every executable and script as its own component
• Shared dependencies explicitly (e.g., which tools use Matrix.h)
• Runtime environment (g++ toolchain, R, Perl)
• File types each tool consumes and produces