search

aws-solutions-library-samples / guidance-for-training-an-aws-deepracer-model-using-amazon-sagemaker

DeepRacer workshop content. This Guidance demonstrates how software developers can use an Amazon SageMaker Notebook instance to directly train and evaluate AWS DeepRacer models with full control
https://aws.amazon.com/solutions/guidance/training-an-aws-deepracer-model-using-amazon-sagemaker/
MIT No Attribution
1.25k stars 713 forks source link

Track waypoint data documentation #74

Closed mdavis-xyz closed 2 years ago

mdavis-xyz commented 3 years ago

I've been looking at the Championship Cup 2019 Track.

In this repo, there's a .np file of waypoints.

https://github.com/aws-samples/aws-deepracer-workshops/blob/master/log-analysis/tracks/ChampionshipCup2019_track.npy

The track there is approximately 1.066 wide. I'm assuming the units of that file are meters. (Since the overall width of the map is about 8, and the official width is 34 feet.)

However all the tracks on this documentation page are 24 inches wide, which is 0.6096m.

Even accounting for the ambiguous 3cm grey curb, that would still only get us to 0.7602m.

Where did these numpy files come from?

I haven't seen a physical track myself, but in all the videos they do not look like they're a whole meter wide.

I would love to see a README at /log-analysis/tracks which explains what a .np file is, which column is which, that the units are in meters, and where the data came from.

mdavis-xyz commented 3 years ago

I just printed track_width within my reward function, and it does indeed say the with is 1.0666. So the data here is right.

It would still help to have a readme explaining this stuff. I'll add one.