This code is legit (see other comment; download the tar and try to forget you ever visited Sourceforce) and incredibly interesting. I browsed this repo a year ago and still come back to it every so often. The architecture decisions that the Stanford team made in 2005 and 2007 have stood the test of time (at least as evidenced by many of the decisions in the architecture of our Voyage car, but anecdotally in others to…
Stanford Code From Cars That Entered DARPA Grand Challenges
11–20 of 21 posts
Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#12Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#13Not for use at high altitudes. From "perception/trafficlights/src/traffic_light_view.cpp:
sprintf(lightBuffer,"%f %f %f", currPose.latitude, currPose.longitude, currPose.altitude);
Yes, it's debug code.The perception end of things is mostly digesting the point cloud from the Velodyne LIDAR. There's vision code for traffic light recognition, but I haven't found other vision code yet.
Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#14> Stanford Made Available Code From Cars That Entered Darpa Challenges That's oddly worded. The wording makes it sound like it's the code from numerous different cars in the challenge, and not just Stanford's entry, but the site wording and the source structure itself look to be a single system. Then again, the code is from 2011, so I guess the past tense is somewhat justified...
Ok, we've replaced the title above with a grammatical one that we ripped off of https://news.ycombinator.com/item?id=14651524 .
Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#15This looks like an updated version of the DARPA Urban Challenge code. It uses ROS extensively, and ROS was only started in 2007. The files are all dated 2011. Not for use at high altitudes. From "perception/trafficlights/src/traffic_light_view.cpp: sprintf(lightBuffer,"%f %f %f", currPose.latitude, currPose.longitude, currPose.altitude); Yes, it's debug code. The perception end of things is mostly digesting the point…
Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#16This code is legit (see other comment; download the tar and try to forget you ever visited Sourceforce) and incredibly interesting. I browsed this repo a year ago and still come back to it every so often. The architecture decisions that the Stanford team made in 2005 and 2007 have stood the test of time (at least as evidenced by many of the decisions in the architecture of our Voyage car, but anecdotally in others to…
Hi Oliver, I have enrolled for the Udacity self-driving car Engineer Nanodegree and cannot wait to start! Do you think that browsing through this codebase will help me better understand some of the concepts taught on the course?
Most of this content isn't covered until Terms 2 & 3, but it's surprisingly relevant.
Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#17This looks like an updated version of the DARPA Urban Challenge code. It uses ROS extensively, and ROS was only started in 2007. The files are all dated 2011. Not for use at high altitudes. From "perception/trafficlights/src/traffic_light_view.cpp: sprintf(lightBuffer,"%f %f %f", currPose.latitude, currPose.longitude, currPose.altitude); Yes, it's debug code. The perception end of things is mostly digesting the point…
Why can't this be used at high altitudes?
Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#18Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#19Re: Stanford Code From Cars That Entered DARPA Grand Challenges
#20This looks like an updated version of the DARPA Urban Challenge code. It uses ROS extensively, and ROS was only started in 2007. The files are all dated 2011. Not for use at high altitudes. From "perception/trafficlights/src/traffic_light_view.cpp: sprintf(lightBuffer,"%f %f %f", currPose.latitude, currPose.longitude, currPose.altitude); Yes, it's debug code. The perception end of things is mostly digesting the point…
Why can't this be used at high altitudes?