Create a time correlation telemetry & calculation output product suitable for thorough analysis
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the existing time-correlation telemetry flow, the Raw Telemetry Table, and the TelemetrySource implementations. Read how telemetry and associated metrics are currently represented and consumed. Done would require a defined human- and machine-readable output suitable for analysis and lossless reingestion, but the issue does not specify files, formats, or acceptance tests.
Written by the indexing model from the issue text.
Description
The basic idea is to have a human + machine-readable log of all time correlation telemetry, along with associated metrics.
Purposes for use would include:
- Aiding in allowing systems and TK engineers to run their own analysis & answer questions when interesting or anomalous situations arise
- Aiding in the ability for lossless reingestion of time correlation telemetry, via a new TelemetrySource implementation (and which would deprecate the Raw Telemetry Table as a telemetry source)
- 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
-
[BUG] 增量 SSE 解析器未识别单独 CR 换行，导致事件无法及时交付Possibly taken @king-wwwhhh claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
langchain4j/langchain4j#6669 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenAPITools/openapi-generator#25237 ·
Maintainers usually reply within 1 day
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
quelea-projection/Quelea#711 ·
-
bug pdd
Difficulty 2/5 Under an hour Newbie friendliness 67/100
objectionary/eo#9450 ·
Maintainers usually reply within 1 day