Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
1–10 of 37 posts
Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#2Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#3Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#4Great to see this is still going! This space needs competition, and I can't see a future where this potentially life-threatening (and also life-saving) technology is close source. It only seems logical it will eventually be 100% open, in order to gain public trust.
Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#5Great to see this is still going! This space needs competition, and I can't see a future where this potentially life-threatening (and also life-saving) technology is close source. It only seems logical it will eventually be 100% open, in order to gain public trust.
I really like the idea of all of this tech being open source, but I don't think it's logical that eventually it will all be 100% open. There's tons of safety critical software now that's closed source (avionics software, utility and power plant software, spacecraft control systems, etc).
Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#6Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#7I have mix feeling about comma.ai I like what they stand for and what they're trying to achieve. But after reading their Openpilot code, it seems completely irresponsible releasing the Eon dev kit they way it is especially after their NHTSA stunt (I only reviewed the code when it first came out so things may have changed). I also wonder why this code is not being ported to something like a Jetson TX2. Especially with…
I don't see how it's really irresponsible also, it is a relatively complicated set up ( getting easier all the time ), but people definitely are aware this isn't a fully fledged product and that they should be keeping an eye at all times.
Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#8Great to see this is still going! This space needs competition, and I can't see a future where this potentially life-threatening (and also life-saving) technology is close source. It only seems logical it will eventually be 100% open, in order to gain public trust.
I really like the idea of all of this tech being open source, but I don't think it's logical that eventually it will all be 100% open. There's tons of safety critical software now that's closed source (avionics software, utility and power plant software, spacecraft control systems, etc).
Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#9I have mix feeling about comma.ai I like what they stand for and what they're trying to achieve. But after reading their Openpilot code, it seems completely irresponsible releasing the Eon dev kit they way it is especially after their NHTSA stunt (I only reviewed the code when it first came out so things may have changed). I also wonder why this code is not being ported to something like a Jetson TX2. Especially with…
A phone is actually a very nice and reliable piece of hardware. It has everything you need CPU, GPU, DSP, two cameras (front and back), a backup battery, a screen and wifi/lte to upload your data.
Re: Comma2k19 – A dataset of over 33 hours of commute in California's 280 highway
#10Earlier quoted context omitted.
I really like the idea of all of this tech being open source, but I don't think it's logical that eventually it will all be 100% open. There's tons of safety critical software now that's closed source (avionics software, utility and power plant software, spacecraft control systems, etc).
We really should be demanding that Waymo be opensource by default from our congress though. May take a few more generations to overtake the current old-brain congress though.