Skip to content

corceslab/ATAC_IterativeOverlapPeakMerging

View on GitHub ↗Related repositories →

active 2024-02-032026-03-27 (UTC)

Partial coverage17,392 / 22,297 hourly files (78%) · 2 absent upstream · 4,904 failed, retryable2024-01-262026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
21
Pushes
0
Pull requests
0
Issues
3
Stars
8
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 784 days from 2024-02-03 to 2026-03-27. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 3 total, peak 1 in a day. Comments: 9 total, peak 4 in a day. Stars: 8 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
ChangshengWei973002
rcorces2002
eafyounian1001
katecycho1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#5eafyounian2026-01-30 09:10
    run code error
  • Issue comment#8rcorces2025-07-23 22:51
    Is "score per million" or p-value used?
  • Issue comment#8rcorces2025-07-23 20:37
    Is "score per million" or p-value used?
  • Issue comment#8jtls0n2025-07-23 20:31
    Is "score per million" or p-value used?
  • Issue comment#8rcorces2025-07-23 19:18
    Is "score per million" or p-value used?
  • Issue#8jtls0n2025-07-23 19:06
    Is "score per million" or p-value used?
  • Issue comment#6ChangshengWei972024-03-25 04:42
    Creating merged peak sets in output directory out_dir Error in bed$thickStart : $ operator is invalid for atomic vectors
  • Issue comment#6ChangshengWei972024-03-25 03:21
    Creating merged peak sets in output directory out_dir Error in bed$thickStart : $ operator is invalid for atomic vectors
  • Issue comment#6rcorces2024-03-23 13:28
    Creating merged peak sets in output directory out_dir Error in bed$thickStart : $ operator is invalid for atomic vectors
  • Issue#6ChangshengWei972024-03-23 09:06
    Creating merged peak sets in output directory out_dir Error in bed$thickStart : $ operator is invalid for atomic vectors
  • Issue comment#4rcorces2024-02-03 14:31
    chrY in union peak set
  • Issue#4katecycho2024-02-03 01:10
    chrY in union peak set

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