-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup real dashcam logging #34131
Comments
On the comma 3X I just took out of my car:
I wonder if these folders are the same size on other devices? Assuming all 274 route segments are full minutes that would be 4.56 hours, but if we take the expected file sizes for a 1 minute segment as 277.4MB (qcam+qlog+rlog+dcam...) then 69GB/277.4MB gives 254.7 minutes or 4.25 hours. |
qcam + qlog (4.4M) is about 1.5% the size of the rest of the logs (275M). If we 4x the size of the qcam and had recordings for all three cameras it would be 28.6M (10.4%). On my 3X that would leave space for 238 minutes (just under 4 hours) without changing the priorities. Will have to see how good a 9MB qcam can be... |
It's roughly the same on all devices.
I'm thinking we only keep a tiny percent of training to start (5%?). |
Is 20 minutes of training data enough? That's about 5.3GB we could keep or 6.6% |
The actual number we set it to isn't super relevant. We just need to setup the slider, then research can set it to whatever they want or ship something to mine for interesting stuff on-device. |
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
andrlog
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 currentqcamera
isn't quite sufficient either.Some concrete TODOs
qcamera
size to be great dashcam footageqcamera
streams for the wide and driver camsHere's the current size breakdown:
The text was updated successfully, but these errors were encountered: