Skip to content

pluxbiosignals/python-samples

View on GitHub ↗Related repositories →

Python programming examples using PLUX's API.

active 2023-10-042025-08-05 (UTC)

Complete coverage26,388 / 26,388 hourly files (100%) · 2 absent upstream2023-08-152026-08-18 (UTC)
Events
41
Pushes
4
Pull requests
0
Issues
5
Stars
9
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 672 days from 2023-10-04 to 2025-08-05. Pushes: 4 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 5 total, peak 1 in a day. Comments: 22 total, peak 5 in a day. Stars: 9 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
GRamosPlux173012
Smruti06037006
XiaoxiZZZZ5004
Inzarcon1000
DFNOsorio1100

Recent activity

Latest issues, pull requests and releases

  • Issue comment#19GRamosPlux2025-06-02 12:10
    Linux64/plux.so version 1.9 crashes on unstable connection with muscleBAN devices
  • Issue#19Inzarcon2025-05-23 14:36
    Linux64/plux.so version 1.9 crashes on unstable connection with muscleBAN devices
  • Issue#18GRamosPlux2024-06-24 09:44
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-06-04 09:53
    Error:The device could not be found
  • Issue comment#18Smruti06032024-06-04 06:39
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-06-03 12:17
    Error:The device could not be found
  • Issue comment#18Smruti06032024-06-01 12:25
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-05-31 19:48
    Error:The device could not be found
  • Issue comment#18Smruti06032024-05-31 10:44
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-05-31 10:30
    Error:The device could not be found
  • Issue comment#18Smruti06032024-05-30 09:55
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-05-29 11:40
    Error:The device could not be found
  • Issue comment#18Smruti06032024-05-29 10:02
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-05-29 09:47
    Error:The device could not be found
  • Issue comment#18Smruti06032024-05-29 09:32
    Error:The device could not be found
  • Issue comment#18GRamosPlux2024-05-29 09:29
    Error:The device could not be found
  • Issue#18Smruti06032024-05-24 12:18
    Error:The device could not be found
  • Issue comment#17GRamosPlux2024-01-03 11:18
    The communication port could not be initialized
  • Issue#17GRamosPlux2024-01-03 11:18
    The communication port could not be initialized
  • Issue comment#17XiaoxiZZZZ2023-12-26 08:07
    The communication port could not be initialized
  • Issue comment#17GRamosPlux2023-11-07 15:15
    The communication port could not be initialized
  • Issue comment#17XiaoxiZZZZ2023-11-06 12:13
    The communication port could not be initialized
  • Issue comment#17GRamosPlux2023-11-03 10:45
    The communication port could not be initialized
  • Issue comment#17XiaoxiZZZZ2023-11-01 08:26
    The communication port could not be initialized
  • Issue comment#17GRamosPlux2023-10-27 10:44
    The communication port could not be initialized

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