Skip to content

Multi-Mission Time Correlation (MMTC)

active 2025-01-092026-08-12 (UTC)

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

Activity over time

Daily event counts in the loaded window

Line chart, 581 days from 2025-01-09 to 2026-08-12. Pushes: 63 total, peak 5 in a day. Pull requests: 14 total, peak 2 in a day. Issues: 23 total, peak 3 in a day. Comments: 70 total, peak 8 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
rmseng9742819
Lagejohn6518517
sonarqubecloud[bot]230023

Recent activity

Latest issues, pull requests and releases

  • Issue#74rmseng2026-08-07 16:11
    Calculate and report predicted time to reach thresholds in Time History File
  • Issue#72rmseng2026-08-07 16:10
    Time correlation automation
  • Issue#97rmseng2026-06-05 20:27
    Possible incorrect behavior when using rollback feature to set products to initial state
  • Issue#71rmseng2026-05-22 20:50
    Support scientific notation for input & output SCLK kernels
  • Issue#38rmseng2026-04-06 19:33
    Add certain options for uplink command output file formatting
  • Issue#68Lagejohn2026-02-17 19:04
    If MMTC fails at certain points after creating its lockfile, the file is never removed and will block future run attempts until it's manually deleted
  • Releasermseng2026-01-16 14:32
    MMTC 1.6.0
  • Issue comment#14rmseng2026-01-06 17:24
    MMTC 1.6.0 User Guide
  • Issue comment#57sonarqubecloud[bot]2026-01-05 20:48
    Merge MMTC UI feature branch into main
  • Issue comment#57sonarqubecloud[bot]2026-01-05 20:06
    Merge MMTC UI feature branch into main
  • Issue comment#57sonarqubecloud[bot]2026-01-05 18:16
    Merge MMTC UI feature branch into main
  • Issue comment#57sonarqubecloud[bot]2025-12-29 21:51
    Merge MMTC UI feature branch into main
  • Issue comment#57sonarqubecloud[bot]2025-12-09 14:36
    Merge MMTC UI feature branch into main
  • Issue comment#56rmseng2025-12-08 19:48
    [gh-22] Reformat encoded sclk from scientific notation to integer in the Time History File
  • Issue comment#56sonarqubecloud[bot]2025-12-08 18:37
    [gh-22] Reformat encoded sclk from scientific notation to integer in the Time History File
  • Issue comment#56sonarqubecloud[bot]2025-12-04 21:38
    [gh-22] Reformat encoded sclk from scientific notation to integer in the Time History File
  • Issue#62rmseng2025-12-04 19:33
    Significantly decrease execution time of end-to-end test suite
  • Issue#61rmseng2025-12-04 19:30
    MMTC 1.7.0 General Maintenance
  • Issue#18rmseng2025-12-04 19:22
    Add SCA
  • Issue comment#60sonarqubecloud[bot]2025-12-03 15:21
    [#18] Add SpotBugs to Gradle build, and change build from JDK 8 -> 17
  • Issue#59rmseng2025-12-03 04:47
    Start enforcing SCA checks and quality gates on codebase
  • Pull request#57rmseng2025-12-01 20:31
  • Issue#55rmseng2025-11-21 16:42
    Create a time correlation telemetry & calculation output product suitable for thorough analysis
  • Issue comment#18Lagejohn2025-11-18 21:46
    Add SCA and linting
  • Issue#48rmseng2025-11-18 00:43
    MMTC should migrate forward its built-in output products between versions

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.