Skip to content

river-view/riverview-central

View on GitHub ↗Related repositories →

active 2025-03-122025-04-03 (UTC)

Complete coverage26,752 / 26,752 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
40
Pushes
3
Pull requests
0
Issues
29
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 24 days from 2025-03-12 to 2025-07-23. Pushes: 3 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 29 total, peak 10 in a day. Comments: 6 total, peak 5 in a day. Stars: 0 total, peak 0 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
osjanity34204
yunks1283002

Recent activity

Latest issues, pull requests and releases

  • Issue comment#22yunks1282025-04-03 21:05
    Task 4.1 Software Lifecycle
  • Issue#23osjanity2025-04-03 19:24
    Task 4.2 Engagement with SWOT Science Data System
  • Issue#22osjanity2025-04-03 19:23
    Task 4.1 Software Lifecycle
  • Issue#21osjanity2025-04-03 19:22
    Task 2.4 River discharge from multi-sensor nadir altimetry
  • Issue#20osjanity2025-04-03 19:21
    Task 2.3 River Discharge from multi-sensor water extent
  • Issue#19osjanity2025-04-03 19:20
    Task 2.2 Lake Storage Change from single-sensor swatch altimetry
  • Issue#18osjanity2025-04-03 19:19
    Task 2.1 SWOT-based river discharge effort
  • Issue#17osjanity2025-04-01 20:54
    Task 3.2.5 Exercise and validate RAPID2 Uncertainty Quantification
  • Issue#16osjanity2025-04-01 20:53
    Task 3.2.4 Implement Data Assimilation in RAPID2 using Efficient Operator
  • Issue#15osjanity2025-04-01 20:52
    Task 3.2.3 Implement Uncertainty Quantification in RAPID2 using daily propagation
  • Issue#13osjanity2025-04-01 20:49
    Task 3.2 Refinement of Uncertainty Propagation and Data Assimilation
  • Issue#12osjanity2025-04-01 20:48
    Task 3.2.1 Draft RAPID2 basic simulation capabilities using Python
  • Issue#6osjanity2025-03-31 21:21
    Create a shared JPL RiverView Google Drive to host the information that cannot be shared publicly
  • Issue#10osjanity2025-03-26 23:06
    Test Ticket 1.B
  • Issue#11osjanity2025-03-26 23:06
    Test Ticket 1.C
  • Issue#10osjanity2025-03-26 18:51
    Test Ticket C
  • Issue#9osjanity2025-03-26 18:51
    Test Ticket B
  • Issue#8osjanity2025-03-26 18:50
    Test Ticket A
  • Issue comment#4yunks1282025-03-13 21:37
    Integrate KS' RiverView landing site repository into the RiverView Github Project
  • Issue#4yunks1282025-03-13 21:37
    Integrate KS' RiverView landing site repository into the RiverView Github Project
  • Issue#7osjanity2025-03-13 20:53
    Discuss meeting time at group meeting Thursday 3/13/25
  • Issue#7osjanity2025-03-13 01:03
    Discuss meeting time at group meeting Thursday 3/13/25
  • Issue comment#5osjanity2025-03-13 00:59
    Define a RiverView Template for that populates when creating new tickets
  • Issue#5osjanity2025-03-13 00:59
    Define a RiverView Template for that populates when creating new tickets
  • Issue comment#3osjanity2025-03-13 00:52
    Create a primary repository for RiverView

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