Skip to content

A segmentation network for intracranial aneurysm on CTA images using pytorch

active 2023-10-282026-01-09 (UTC)

Partial coverage20,535 / 26,291 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-14 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
24
Pushes
0
Pull requests
0
Issues
5
Stars
12
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 805 days from 2023-10-28 to 2026-01-09. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 5 total, peak 1 in a day. Comments: 6 total, peak 4 in a day. Stars: 12 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
MeteorsHub6004
KuroTetsuya3002
AliJ91000
Fjch-Ryan1000

Recent activity

Latest issues, pull requests and releases

  • Issue#18MeteorsHub2024-12-30 05:53
    Clarification Needed on is_ruptured in internal_instances.csv for Subjects with Multiple IAs
  • Issue comment#18MeteorsHub2024-12-30 05:53
    Clarification Needed on is_ruptured in internal_instances.csv for Subjects with Multiple IAs
  • Issue#18AliJ92024-12-27 22:17
    Clarification Needed on is_ruptured in internal_instances.csv for Subjects with Multiple IAs
  • Issue#17MeteorsHub2024-12-24 03:05
    ay I ask why this error often occurs when I encounter ruptured aneurysm data while running with your code:an illegal memory access was encountered
  • Issue comment#17MeteorsHub2024-08-19 02:23
    ay I ask why this error often occurs when I encounter ruptured aneurysm data while running with your code:an illegal memory access was encountered
  • Issue#17Fjch-Ryan2024-08-17 03:25
    ay I ask why this error often occurs when I encounter ruptured aneurysm data while running with your code:an illegal memory access was encountered
  • Issue comment#16KuroTetsuya2023-11-19 16:50
    Mismatch channels between weight and input patch
  • Issue comment#16MeteorsHub2023-11-19 16:10
    Mismatch channels between weight and input patch
  • Issue comment#16KuroTetsuya2023-11-19 15:54
    Mismatch channels between weight and input patch
  • Issue comment#16MeteorsHub2023-11-19 14:34
    Mismatch channels between weight and input patch
  • Issue#16KuroTetsuya2023-11-17 08:32
    Mismatch channels between weight and input patch

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