A better walkthrough of the training data collection process? about self-driving-car

[RyanZotti]

It’s late at night on the West Coast right now, so I’m just going to post a short comment for now.

Very short answer: my data collection process really sucks (because it’s unitinuitive) and I’m currently refactoring it based on best practices from here: http://docs.donkeycar.com/guide/get_driving/. If you scroll down about half way on that page you’ll see a really slick mobile web UI that you can use to gather training data. The full refactoring will take another 5-6 week’s most likely. I highly recommend looking at the donkeycar repo in general.

The long answer is sort of in the main readme of my repo, but if that’s insuifficent then a better answer will take me too long to type over my phone now. I’ll reply back to this issue with better instructions once I’ve finished he refactoring.

[CT83]

Okay, I am now reading more into the code and the readme. Respond with a thumbs up, so I know I am going in the right direction.

1. We install FFMPEG to stream video from RPi to PC
2. Use stream_mjpeg_video.py and display it using OpenCV streamer from util.py to confirm it is working.
3. Then basically save_streaming_video_data.py saves streamed video on local pc and the server logs the key strokes.
4. We copy paste them to a single location.
5. Then cross reference the saved images time stamp with the saved keystrokes timestamps and make clean training data

[CT83]

Not really relevant here but adding it incase someone else stumbled on this problem, I was using the code here, to capture the frames and stream back to the server.
I had used
for _ in camera.capture_continuous(stream, 'jpeg'):
instead of
for _ in camera.capture_continuous(stream, 'jpeg', use_video_port=True):
That was the source of the problem!! Getting smooth 20-30 FPS now!

Thanks a bunch for all your help @RyanZotti