Skip to content

A research toolkit for extracting quantitative features from human movement data, offering computational methods to analyze movement qualities like smoothness, bilateral symmetry, contraction/expansion patterns, and synchronization. Built for researchers in motor control, biomechanics, and movement disorders.

active 2025-09-192026-04-07 (UTC)

Complete coverage26,435 / 26,435 hourly files (100%) · 2 absent upstream2023-08-152026-08-20 (UTC)
Events
190
Pushes
103
Pull requests
19
Issues
26
Stars
3
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 201 days from 2025-09-19 to 2026-04-07. Pushes: 103 total, peak 14 in a day. Pull requests: 19 total, peak 5 in a day. Issues: 26 total, peak 6 in a day. Comments: 14 total, peak 4 in a day. Stars: 3 total, peak 1 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
nicola-corbellini10476165
sanketsabharwal361417
gaggioaxel181102
simoneghisio2110
paolo-coletta1100
Foysal4401010

Recent activity

Latest issues, pull requests and releases

  • Issue#80nicola-corbellini2026-03-04 07:54
    Ensure all the features work both with 2D and 3D data
  • Issue#69nicola-corbellini2026-03-04 07:51
    Remove the print from Synchronization
  • Issue#79gaggioaxel2026-02-15 17:55
    Pass the SlidingWindow to the features' __init__ to ensure it is sufficiently (and perhaps not excessively) sized.
  • Issue#78gaggioaxel2026-02-12 14:37
    Divide the features design into "static" features and "dynamic" ones
  • Pull request#76nicola-corbellini2026-02-11 16:36
  • Issue#71nicola-corbellini2025-11-04 20:21
    Add Clusterability in the documentation
  • Pull request#70Foysal4402025-11-04 11:14
  • Issue comment#69nicola-corbellini2025-10-31 13:43
    Remove the print from Synchronization
  • Issue comment#62nicola-corbellini2025-10-31 13:35
    Add functionality to test real world sample data with appropriate flags
  • Issue#58sanketsabharwal2025-10-08 16:38
    Remove TD scripts from examples.
  • Issue#5sanketsabharwal2025-10-08 16:38
    Develop CLI
  • Issue comment#59nicola-corbellini2025-10-08 16:01
    Ask foysal to prepare example scripts and files showcasing use cases of pyeyesweb.
  • Issue#54sanketsabharwal2025-10-08 14:48
    Example in Smoothness is wrong
  • Issue comment#55gaggioaxel2025-10-08 13:14
    In NumPy, indexing is done by rows first and then by columns.
  • Issue#55gaggioaxel2025-10-08 13:14
    In NumPy, indexing is done by rows first and then by columns.
  • Issue comment#55gaggioaxel2025-10-08 13:14
    In NumPy, indexing is done by rows first and then by columns.
  • Issue#55gaggioaxel2025-10-08 10:45
    in numpy si indicizza per righe e poi colonne
  • Issue#54gaggioaxel2025-10-08 10:04
    Example in Smoothness is wrong
  • Issue#51sanketsabharwal2025-10-05 17:43
    Develop a robust logging framework
  • Issue#50nicola-corbellini2025-10-05 10:06
    Allow users to select the algorithm in feature computation
  • Issue comment#49nicola-corbellini2025-10-05 06:55
    Prepare list of features to be developed
  • Issue#49sanketsabharwal2025-10-04 23:16
    Prepare list of features to be developed
  • Issue comment#41sanketsabharwal2025-10-04 22:14
    `physical_signals` subpackage need to be developed
  • Issue#42sanketsabharwal2025-10-04 22:08
    Check for race conditions for all features
  • Issue#39sanketsabharwal2025-10-04 21:55
    Standardize API calls

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