-
Notifications
You must be signed in to change notification settings - Fork 1
gather data
In order to keep the training data organized and in the same format so we call can benefit from your AWESOME driving skillz we have made some helper scripts. These require some one-time setup steps, but they should make life a bunch easier moving forward.
-
Edit
ssh_to_car.sh
: This script adds the correct parameters to allow you to ssh to the car (Pi/Nano) but also allow the car to send data back viarsync
. All you need to do is change theCAR_ADDRESS
variable to[email protected]
. ie: My username on the Pi isjosh
and my Pi's name on the network isdingo1
so I would set[email protected]
. -
Edit
info.json
: This file should be edited anytime you have changed the type of track or location you are gathering data in. It is used to keep track of information about the training data contained in a tub. ie: If I was training on a 40cm wide track on a timber floor in Buckingham Palace with thick green tape, no centerline myinfo.json
would look like this:
{
"count": -1,
"date": "SET AUTOMTICALLY",
"tape": "thick green",
"floor" : "timber",
"location": "Buckingham Palace",
"centre line" : false,
"lane width" : "40cm"
}
- ssh to the Pi: To ssh to the pi we have a simple bash script so you don't need to remember the command. It's pretty simple but all the little things tend to add up.
cd dingocar
./ssh_to_pi
-
cd play/roba1/mycar
-
Fill in the
info.json
: Theinfo.json
is used to help keep track of when a dataset was gathers and what type of data is in the tub that is gathered. I recomend you fill this is at the start of a labelling session (or whenever your track or track environment changes). A sampleinfo.json
is below:
{
"count" : SET AUTOMATICALLY,
"date" : SET AUTOMATICALLY,
"tape" : "thick yellow",
"floor" : "timber",
"location" : "bill gates' house",
"centre line" : true,