DATA COVERAGE
Manual run entries: what can and cannot be analyzed?
A manually entered distance and time can preserve a useful training record. They cannot recreate a route, a split pattern or a measured heart-rate trace.
Start with the inputs you actually have
Suppose you know that an outing covered five kilometers in 30 minutes. Those two totals support an average pace of 6:00 per kilometer. Add a correct date and you can also place the distance in a weekly history. None of those calculations needs a second-by-second recording.
Now ask whether kilometer three was faster than kilometer four. The totals do not answer that question. Many different split patterns add up to the same finish time. A straight line drawn between a start and finish is a presentation choice, not recovered evidence about the middle.
Match each question to its required data
| Question | Minimum useful evidence |
|---|---|
| What was the average pace? | Distance and a defined duration |
| How much did I run this week? | Distance, date and inclusion rules |
| Where did I run? | Recorded positions or a separately supplied route |
| How did pace change? | Suitable time/distance samples or recorded laps |
| How did heart rate change? | Heart-rate samples with timestamps |
| Was the second half less efficient? | Comparable time-aligned speed and heart-rate segments |
An average heart-rate value adds a summary signal. It still does not reveal when the heart rate rose or how much of the activity was actually measured. Keep a supplied average distinct from a full sensor stream.
Preserve uncertainty when filling gaps
If you know only approximately how long the run took, keep that context in your note. Entering a highly precise value does not make an estimate precise. Similarly, copying a route from another day may help describe the location but does not establish that the actual path and distance were identical.
Keep an original export if one exists before entering a duplicate manually. A later import can otherwise make one outing appear twice in distance totals. Review date, start time and distance when reconciling the two records.
Use the record for the questions it supports
Runome can use activity totals within a running history while detailed analysis depends on the data available. Read absent stream-based metrics as missing evidence. Do not substitute an estimated curve and describe it as a continuous measurement.
The pace calculator is useful for checking the known distance and time. For imported files, see why a workout can arrive without every metric. For another important measurement distinction, read camera pulse points versus a recorded heart-rate stream.