pystatsv1 / pystatsv1/PyStatsV1

Start here: Welcome to PyStatsV1 (v0.17.0)

Open
#68 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
Python
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Start here: Welcome to PyStatsV1 (v0.17.0) 🎓📊

Welcome! PyStatsV1 is an open-source project that ports applied statistics case studies
(from an R-based textbook) into modern Python scripts and reproducible workflows.

The goal: give students and instructors working, well-documented examples they can
clone, run with make, and adapt to their own teaching and learning.


🔍 What’s in the repo?

PyStatsV1 currently includes:

Chapter 13 — Experimental Designs
  • Stroop within-subject reaction-time study
  • 2×2 fitness mixed-design study (mixed effects)
Chapter 14 — Classic A/B Test
  • Tutoring study with two-sample t-test
  • Simulator + analyzer with reproducible workflow
Chapter 15 — Reliability & Psychometrics
  • Cronbach’s alpha for survey internal consistency
  • Intraclass correlation (ICC) for test–retest reliability
  • Bland–Altman plot for agreement

See:


🧰 How to run things locally

Requirements:

  • Python 3.10+
  • git
  • Recommended: VS Code, PyCharm, or any editor

Clone and set up:

git clone git@github.com:pystatsv1/PyStatsV1.git
cd PyStatsV1
python -m venv .venv
source .venv/bin/activate     # Windows: .venv\Scripts\activate
pip install -r requirements.txt

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue contains a project welcome and setup overview but names no file or documentation change. Read CHAPTERS.md and ROADMAP.md first, then clarify which onboarding content should be added or revised and what completed documentation should cover.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.