Skip to content

CancerDataAggregator/cdapython

View on GitHub ↗Related repositories →

A Python-based interface to CDA

active 2024-03-212026-07-27 (UTC)

Complete coverage26,356 / 26,356 hourly files (100%) · 2 absent upstream2023-08-152026-08-17 (UTC)
Events
626
Pushes
487
Pull requests
18
Issues
23
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 859 days from 2024-03-21 to 2026-07-27. Pushes: 487 total, peak 58 in a day. Pull requests: 18 total, peak 3 in a day. Issues: 23 total, peak 9 in a day. Comments: 43 total, peak 16 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
abradyGDIT489444517
tanner-coon-bh452389
ACharbonneau230014
fthomas64115453
KutnerBroadie1000

Recent activity

Latest issues, pull requests and releases

  • Issue#29abradyGDIT2026-01-20 17:33
    Create POC slim functionality prior to full integration
  • Issue#29abradyGDIT2026-01-20 17:31
    Create POC slim functionality prior to full integration
  • Issue#24abradyGDIT2025-10-29 15:24
    Check API response values for `column_values()` vs. `cdapython` expectations re: empty `dict` vs. `None`/`null`
  • Issue comment#24abradyGDIT2025-10-29 15:24
    Check API response values for `column_values()` vs. `cdapython` expectations re: empty `dict` vs. `None`/`null`
  • Issue comment#25abradyGDIT2025-10-28 16:45
    Guarantee cdapython never generates queries which include Boolean values in IN clauses
  • Issue#19abradyGDIT2025-10-28 14:45
    Return full SQL version of user queries upon request
  • Issue comment#19abradyGDIT2025-10-28 14:45
    Return full SQL version of user queries upon request
  • Issue#26abradyGDIT2025-10-06 21:09
    Create style/standards guide for cdapython UI
  • Issue#24abradyGDIT2025-10-06 20:14
    Check API response values for `column_values()` vs. `cdapython` expectations re: empty `dict` vs. `None`/`null`
  • Issue#23abradyGDIT2025-10-06 20:12
    Update `data_source` parameter in `column_values()` to allow multiple-value (list) requests as is now supported by API
  • Issue#22abradyGDIT2025-10-06 20:10
    Hook validation logic into `discover.py`
  • Issue#21abradyGDIT2025-10-06 19:46
    Review result-filtration discomfort re: `add_columns`
  • Issue#20abradyGDIT2025-10-06 19:41
    Add virtual `data_source` column to `columns()` for `file` and `subject` to mirror the `data_source` parameter
  • Issue#15abradyGDIT2025-07-30 15:16
    I don't think i can search by age anymore
  • Issue#11abradyGDIT2025-07-30 15:15
    Where did all the garbage data go?
  • Pull request#17tanner-coon-bh2025-04-10 17:28
  • Pull request#17tanner-coon-bh2025-04-10 17:27
  • Issue comment#16tanner-coon-bh2025-03-27 16:58
    significant digits
  • Issue#16tanner-coon-bh2025-03-27 16:58
    significant digits
  • Issue comment#10tanner-coon-bh2025-03-26 18:01
    Is there really only one science column in observation??
  • Issue comment#10ACharbonneau2025-03-25 13:58
    Is there really only one science column in observation??
  • Issue comment#14ACharbonneau2025-03-25 13:54
    summary counts display isn't the pretty boxes
  • Issue comment#10ACharbonneau2025-03-25 13:28
    Is there really only one science column in observation??
  • Issue comment#16ACharbonneau2025-03-25 13:27
    significant digits
  • Issue comment#16tanner-coon-bh2025-03-24 21:05
    significant digits

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.