Skip to content

SomeoneInParticular/dcm-classic-ml

View on GitHub ↗Related repositories →

Machine learning analysis for predicting post-surgical outcomes in Degenerative Cervical Myelopathy (DCM)

active 2024-10-232025-06-17 (UTC)

Complete coverage26,730 / 26,730 hourly files (100%) · 2 absent upstream2023-08-152026-09-01 (UTC)
Events
138
Pushes
59
Pull requests
15
Issues
28
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 238 days from 2024-10-23 to 2025-06-17. Pushes: 59 total, peak 6 in a day. Pull requests: 15 total, peak 2 in a day. Issues: 28 total, peak 5 in a day. Comments: 19 total, peak 3 in a day. Stars: 1 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
SomeoneInParticular121591519

Recent activity

Latest issues, pull requests and releases

  • Issue#11SomeoneInParticular2025-06-17 17:50
    [Feature] Normalize Imaginge Metrics w/ PAM50
  • Issue comment#29SomeoneInParticular2025-06-17 17:47
    The Special Case of Per-Slice Angle Statistics
  • Issue#29SomeoneInParticular2025-06-17 17:47
    The Special Case of Per-Slice Angle Statistics
  • Issue comment#30SomeoneInParticular2025-02-07 19:08
    Per-Slice Statistics Analyses
  • Pull request#30SomeoneInParticular2025-01-14 02:28
  • Issue#29SomeoneInParticular2025-01-10 18:47
    The Special Case of Per-Slice Angle Statistics
  • Issue comment#18SomeoneInParticular2025-01-09 18:56
    Add hook to report correct/incorrectly classified samples during validation/testing etc.
  • Issue#18SomeoneInParticular2025-01-09 18:56
    Add hook to report correct/incorrectly classified samples during validation/testing etc.
  • Issue#23SomeoneInParticular2025-01-09 18:50
    [Refinement] Re-write data pre-processing to reduce code redundancy
  • Pull request#28SomeoneInParticular2025-01-09 18:50
  • Issue comment#27SomeoneInParticular2025-01-06 19:57
    Repository Split
  • Pull request#27SomeoneInParticular2025-01-06 15:52
  • Issue comment#24SomeoneInParticular2024-12-18 17:26
    [Restructure] Split sct_processing in its own repos
  • Issue#14SomeoneInParticular2024-12-18 16:46
    [Feature] Extend the range in which vertebral metrics are calculated to include C7
  • Issue comment#14SomeoneInParticular2024-12-18 16:46
    [Feature] Extend the range in which vertebral metrics are calculated to include C7
  • Pull request#22SomeoneInParticular2024-12-18 16:45
  • Issue comment#22SomeoneInParticular2024-12-18 16:45
    C2-C7 extended
  • Issue comment#23SomeoneInParticular2024-12-17 21:58
    [Refinement] Re-write data pre-processing to reduce code redundancy
  • Issue comment#25SomeoneInParticular2024-12-17 21:58
    [Refactor] Remove Duplicated Codes Across Processing Scripts in `sct_processing`
  • Issue#25SomeoneInParticular2024-12-17 21:58
    [Refactor] Remove Duplicated Codes Across Processing Scripts in `sct_processing`
  • Issue#26SomeoneInParticular2024-12-17 21:44
    Update SoftSeg model description to be clearer that it is a variant of DeepSeg, not a unique model
  • Issue#25SomeoneInParticular2024-12-17 21:36
    remove duplication across processing scripts in sct_processing
  • Issue#24SomeoneInParticular2024-12-17 21:32
    Split sct_processing in its own repos
  • Issue#23SomeoneInParticular2024-12-17 04:46
    [Refinement] Re-write data pre-processing to reduce code redundancy
  • Pull request#22SomeoneInParticular2024-12-17 04:42

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