Time correlation automation
@rmseng is already working on this.
Since Aug 7, 2026.
Assessment
This issue has not been assessed yet.
Description
MMTC's current design is meant to serve as a point of integration for external automation systems to drive, but some current users desire a built-in automation feature that offer more customizable conditions for producing new correlations, etc.
Add feature(s) to MMTC to support out-of-the-box automated time correlation, including:
- A new 'autocorrelate' feature
- Include support for custom conditions for writing new correlations (and possibly output files themselves)
- Expose the feature via CLI and UI
- Include systemd service and/or timer files to run MMTC's autocorrelate periodically or as a long-lived daemon
For example, we should support the case where:
- MMTC triggers periodically (e.g. daily or weekly) to check for new telemetry
- MMTC calculates trending information on any new telemetry (see table below), and records it to new output products,
and optionally emails it - Optionally, if certain conditions are met (which?), then new 'typical' correlation products are written, e.g. SCLK kernels & SCLK-SCET files, et al.
- MMTC calculates trending information on any new telemetry (see table below), and records it to new output products,
- MMTC allows a manual correlation to be made, when an outside process (involving humans or not) decides to write a new kernel
| Information | To where | Notes |
|---|---|---|
| New telemetry found since last run | ||
| SCLK vs. SCET Error plots | ||
| Ep(ms) and its derivates | Error in predicting latest SCET times using prior-generated kernel | |
| TDT(S) Error | ||
| Time to reach SCET Error threshold | ||
| Time to reach TDT(S) Error |
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NASA-AMMOS/MMTC
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NASA-AMMOS/MMTC#117 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
NASA-AMMOS/MMTC#113 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
NASA-AMMOS/MMTC#112 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
NASA-AMMOS/MMTC#106 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
NASA-AMMOS/MMTC#104 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug new windows
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GantMan/jail-monkey#380 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
objectionary/jucs#145 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
objectionary/lints#1559 ·
Maintainers usually reply within 2 days