Setup real dashcam logging
- Dominant language
- Python
- Stars
- 63.7k
- Forks
- 11.4k
- Avg merge
- 17h 53m
- Merged PRs (30d)
- 171
Description
This project is to maximize the usable dashcam storage space on a comma 3X. Currently, it's tuned for maximum training/debuggability. We should be able to tradeoff a bit of that for a great dashcam experience.
`.hevc` and `rlog` are needed for training and debugging, but they also take up most of the device's storage. They are overkill for dashcam purposes, but the current `qcamera` isn't quite sufficient either.
Some concrete TODOs
* deleter: setup two classes of files "dashcam" and "training"
* deleter: prioritize "dashcam" segments
* logger: bump up `qcamera` size to be great dashcam footage
* logger: setup `qcamera` streams for the wide and driver cams
---
Here's the current size breakdown:
```bash
2.2M qcamera.ts
2.2M qlog
56M rlog
72M dcamera.hevc
72M fcamera.hevc
73M ecamera.hevc
```
Contributor guide
Research direction
Start by locating the deleter and logger components responsible for qcamera, rlog, and the camera streams, then review how storage usage is currently prioritized. The issue identifies separate dashcam and training file classes, dashcam prioritization, larger qcamera footage, and wide and driver camera streams as the target. Done means these four behaviors work together within the comma 3X storage constraints.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100