Flow
CPU and memory are not shown, because the Monitor cannot reach the Docker API. Check that the service is running, and in .env.
Days built at once
It changes only how soon days are built, never what they become, so nothing is rebuilt.
- PostgreSQL PostgreSQL. Home has one database, at the bottom left, and the cloud one of its own, in its band; every home service that reads or writes home's has it drawn underneath.
- Garage Garage, the S3 store that keeps every uploaded file's bytes.
- Working right now Working right now.
- Settings Settings: how many days the Processor builds at once, Auto or a count of your choosing.
- Not running Not running: Docker has no running container for it, or, while Docker cannot be asked, it has not reported.
- Not linked Not linked: home and the cloud are not connected, so nothing is known of the other side's services, and what it shows is greyed out.
-
CPU is a share of one core and memory what the container holds, both as
docker statscounts them.
Maintenance
After a change to the Preprocessor or Processor settings, every day was built with the old numbers. This queues all of them again. It does not reset the heatmap: until a day is rebuilt all the way, the heatmap keeps showing it as it was built before.
Resetting the heatmap throws every heat tile away and adds back only the days that are processed with their latest data. The others go into the heatmap as they are rebuilt, so nothing old is left on it.
After a fix to how a file format is read, the points already taken from those files are stale. This reads every current file again, which also rebuilds the days they cover.
No files match.
| File | Origin | State | Points | Covers (UTC) | Uploaded (UTC) | Issues |
|---|---|---|---|---|---|---|
Versions
| Uploaded (UTC) | As | From | State | Points | SHA-256 | |
|---|---|---|---|---|---|---|
Days with its points
None.
Issues
None.
No day has any data yet.
How the estimate agrees with the labels
Nothing to compare yet. Label segments on the day pages; once their days are rebuilt, this shows how much of each labelled mode the rules got right, and what they took it for instead.
Overall the rules agree with the labels for of the labelled time. Rows are what the label says, columns what the rules chose without it.
| Labelled \ estimated | |
|---|---|
Labels
None yet.
Striped: as estimated. Solid: labelled. Outlined: changed and not saved yet. Finely lined: longer than an hour, and drawn an hour long, with its middle squeezed. Zooming keeps the picked stretch in view. Click a stretch to say what it was; drag the edge between two, or move it with ←/→ (Shift: a minute), and the map shows where it is. "Delete" is for GPS noise: the stretch's time goes to the one beside it, and a stretch saved as stationary stands still on the map. "Save whole day" makes every stretch a label of its own, in place of the day's labels.
Layers
Segments
None.
Labels
None. A label says what a stretch really was; it wins over the estimate, and the Labels view measures the estimate against it.
Click the track on the map, or a segment above, to fill this in with its times and the mode it was estimated as. The stretch is outlined on the map.
Issues
None.