Edit: Someone else in this thread commented that the repo linked in the article isn't the right one and apparently this is where the code resides https://github.com/commaai/openpilot
Edit: Someone else in this thread commented that the repo linked in the article isn't the right one and apparently this is where the code resides https://github.com/commaai/openpilot
That said, Hotz claimed to have read state of the art papers, but it doesn't seem he meant hard real time physics/mechanics computations; probably neural net, computer vision and deep learning. Hacker way ?
It's not about bandwidth or complexity, it's about latency. And no, even a recent core i7 can be stalled for long enough to cause underruns in a simple audio stream.
an i7 in this case will be significantly worse than a Cortex-M0. Entirely due to the features in the i7 that make it high performance, such as instruction reordering, branch prediction, etc. All those types of features make the performance less deterministic.
Hmm. Sorry, but no.
I am not going to let my car being driven by dynamically typed code without any tests.
Frankly, it looks like a hobby project that has grown a bit messy over time.
How are you going to enforce that? Make Tesla show you their source?
How are you not already enforcing that? Make the existing automobile makers show their source for the plethora of computer driven systems!
That is a very quantifiable amount that I totally understand.
>bunch of tests for regulators
Oh and how many of our emissions testings have been gamed by at least one company?
Also they rely on python neuralnetwork libs which lowers the line count, probably tremendously, with the right abstraction already done you can go pretty far without a lot of lines (think yacc).
Commits are an essential ingredient in a modern codebase to describe why each line of the code is there.
I don't want to go back to blocks being commented out and code intertwined with comments like /* 6-dec-2016 tomtomtom: moved from other_function() to fix latency */