Skip to content

IAPSO-CTDO2/IAPSO_CTDO2_processing

View on GitHub ↗Related repositories →

active 2024-11-242025-04-17 (UTC)

Complete coverage26,649 / 26,649 hourly files (100%) · 2 absent upstream2023-08-152026-08-29 (UTC)
Events
45
Pushes
23
Pull requests
0
Issues
7
Stars
4
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 145 days from 2024-11-24 to 2025-04-17. Pushes: 23 total, peak 8 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 7 total, peak 6 in a day. Comments: 0 total, peak 0 in a day. Stars: 4 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
katrinSCH3748800
yfiring6500
beeberx6000
AnthonyBosse6600
clangdon35004400

Recent activity

Latest issues, pull requests and releases

  • Issue#3beeberx2025-04-17 14:47
    Order of processing steps - analysis
  • Issue#4beeberx2025-04-17 14:47
    Reach out to the participants with follow up questions on SBE processing order
  • Issue#5beeberx2025-04-17 14:47
    Create dataset of different processing order typologies
  • Issue#5beeberx2025-04-17 14:42
    1. Reach out to the participants and ask them
  • Issue#4beeberx2025-04-17 14:39
    Reach out to the participants with follow up questions on SBE processing order
  • Issue#3beeberx2025-04-17 14:36
    Order of processing steps - analysis
  • Issue#2yfiring2024-11-25 13:49
    private vs public

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