|
|
|
|
|
by DesolationJones
1948 days ago
|
|
This is what Geohot said in a reddit post. "We have done most of the ISO26262 analysis, we're hiring someone right now to get it written up nicely and open sourced. (those interested can find the job posting) It's one of our goals for openpilot 1.0" They have a slightly more in depth explanation of their safety model in the "Background — safety architecture" section of this post. https://medium.com/@comma_ai/how-to-write-a-car-port-for-ope... |
|
This is the first place I've seen this acknowledged - and, bizarrely, I read most of the PRs and commits to the `safety` part of Panda, and didn't find a single reference to the checklist in that Medium post (and, only some of the requirements seem to be implemented in most cars). It feels really late to me to be doing this, and it seems like they could use a good docs person and some, well, leadership in the project.
One thing I noticed in general was that it seems like most Comma communication is side-channeled - most commits and PRs do not have much of anything in terms of description or documentation, and code review is really sparse, it feels like there's a back-room discussion happening rather than GitHub, presumably on Discord? This makes it almost impossible to understand the safety constraints and reasoning, or to audit changes to the system.
But, it also sounds like they could very well be on the right track for 1.0, provided they hire the right person and they're able to clean things up.
Thank you for pointing this out, cheers!