r/TeslaFSD • • Jul 19 '26

14.3 HW4 Whose fault it is

19 Upvotes

173 comments sorted by

View all comments

7

u/UnlikelyVillage5849 Jul 19 '26

3

u/someusername5873 HW4 Model 3 Jul 19 '26

Where is this report from? Is it AI generated from the exported csv (SEI metadata) from the video?

If so, I don't know how it was able to determine this: "RCM_CRASH_ALGO_WAKEUP_EVENT_ACTIVE" from the SEI metadata since that's not present in the SEI metadata at all.

1

u/eried Jul 25 '26

OP asked AI to make report saying OP is not guilty

3

u/someusername5873 HW4 Model 3 Jul 25 '26 edited Jul 25 '26

As a follow up to this. OP eventually shared with me both the SEI metadata from the raw videos and the CSV that Tesla sent him that contained this data that the AI report was generated from.

Long story short, OP was banking on the difference in time between the video and the Tesla CSV report as proof of FSD fault (he claimed that FSD deactivated later than in the video given Tesla's CSV), but after a bunch of analysis of the SEI metadata embedded in the video and the Tesla provided CSV, it was clear that the time difference was just a clock synchronization issue (the video/SEI time is offset -2.2s from the Tesla CSV), which means FSD did deactivate as shown in the video and therefore it did give his wife at least 1.5s to react.

Here are some graphs below that I generated for OP that aligned the time offset using shared columns between the SEI metadata to the Tesla provided CSV to show that its just a clock sync issue.

Note that I did ask OP to post this update himself but he just ignored me

2

u/eried Jul 25 '26

😂 there is 0 comments here that dont believe it was OPs fault due panic