Skip to content

A drift-diffusion modeling (DDM) framework for Python

active 2023-08-182026-06-13 (UTC)

Complete coverage26,513 / 26,513 hourly files (100%) · 2 absent upstream2023-08-152026-08-23 (UTC)
Events
134
Pushes
39
Pull requests
2
Issues
16
Stars
42
Forks
7

Activity over time

Daily event counts in the loaded window

Line chart, 1031 days from 2023-08-18 to 2026-06-13. Pushes: 39 total, peak 8 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 16 total, peak 3 in a day. Comments: 22 total, peak 4 in a day. Stars: 42 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
mwshinn5838112
Hyphcha6004
SiebrenKuiper3001
mberns-ru2002
alessandromazza932001
bpesquet1010
tkononow1000
Jiashun971001
zhengli-hub1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#128mwshinn2025-07-22 06:05
    Analytic solutions not calculated for custom ICPoint* dependences
  • Issue#128mwshinn2025-07-22 06:05
    Analytic solutions not calculated for custom ICPoint* dependences
  • Issue#128covertg2025-07-21 22:14
    Analytic solutions not calculated for custom ICPoint* dependences
  • Issue comment#79mwshinn2025-07-12 20:02
    error with analytical solver with collapsing bound and noise > 1
  • Issue comment#67mwshinn2025-07-12 19:59
    Undecided trial support
  • Issue#67mwshinn2025-07-12 19:59
    Undecided trial support
  • Issue#127Hyphcha2025-04-20 11:59
    Multithreading-related issues
  • Issue comment#127Hyphcha2025-04-17 13:33
    Multithreading-related issues
  • Issue comment#127Hyphcha2025-04-17 10:36
    Multithreading-related issues
  • Issue comment#127mwshinn2025-04-17 06:07
    Multithreading-related issues
  • Issue comment#127Hyphcha2025-04-17 01:27
    Multithreading-related issues
  • Issue comment#127mwshinn2025-04-16 21:51
    Multithreading-related issues
  • Issue comment#127Hyphcha2025-04-16 17:07
    Multithreading-related issues
  • Issue#127Hyphcha2025-04-16 17:05
    Multithreading-related issues
  • Issue#126SiebrenKuiper2025-03-29 10:23
    Ask for help: Fit too slowly, related to boundaries
  • Issue comment#126SiebrenKuiper2025-03-29 10:14
    Ask for help: Fit too slowly, related to boundaries
  • Issue comment#126mwshinn2025-03-29 06:38
    Ask for help: Fit too slowly, related to boundaries
  • Issue#126SiebrenKuiper2025-03-29 05:54
    Ask for help: Fit too slowly, related to boundaries
  • Issue comment#119Jiashun972025-02-24 14:15
    Deprecation warning of prob_correct()
  • Issue comment#119mwshinn2025-02-24 13:47
    Deprecation warning of prob_correct()
  • Issue#101mwshinn2024-06-30 21:53
    Numpy 2.0 compatibility
  • Issue#101mwshinn2024-06-19 17:06
    Numpy 2.0 compatibility
  • Issue#87mwshinn2024-05-16 06:46
    access trial-by-trial drift
  • Issue comment#98mwshinn2024-05-16 06:32
    How to visualize or output the value of the drift rate, boundary, and the value of 'x' during the simulation for a fitted model with given parameters. I want to visualize the process of how the information is accumulated and how the boundary is changed like the figure below:
  • Issue#98mwshinn2024-05-16 06:32
    How to visualize or output the value of the drift rate, boundary, and the value of 'x' during the simulation for a fitted model with given parameters. I want to visualize the process of how the information is accumulated and how the boundary is changed like the figure below:

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 42 stars here means stars gained during the window, not the repo's star count.