Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Software Update 2018.39 4a3910f (plus other v9.0 early access builds)

This site may earn commission on affiliate links.
Again, you’re stating as fact a whole lot of not-publicly-visible(and otherwise unreported) information about Tesla’s FSD development codebase. So do you have a source for this?

I'm only logically comparing and contrasting. If chip A runs all the NN models necessary for LVL 5 perception including way more NN models than chip B using 75% less processing power. Then Chip b should theoretically be able to handle the amount of NN models that chip A does even if it came with some overhead (even with the difference in efficiency and accelerators). The only other contingency would be planning, but again like i said i don't believe Tesla software are as advanced as some people believe they are.
 
  • Like
Reactions: kavyboy and ord3r
I'm only logically comparing and contrasting. If chip A runs all the NN models necessary for LVL 5 perception including way more NN models than chip B using 75% less processing power. Then Chip b should theoretically be able to handle the amount of NN models that chip A does even if it came with some overhead. The only other contingency would be planning, but again like i said i don't believe Tesla software are as advanced as some people believe they are.

Not if chip B is memory constrained. The whole network has to fit in memory. And while it may be able to run, it may not be able to run in real time to meet the requirements of driving.
 
Can you PM me?
just to be clear. everything you need to know about this process was posted further upthread. I do not distribute Tesla binary firmwares for legal reasons, so you need to find some other source than me. There was one and I listed it, now that it's closed, I do not know of any other public sources I could direct people to. If anybody knows better, perhaps they'll update here in the thread with more sources.
 
Not if chip B is memory constrained. The whole network has to fit in memory. And while it may be able to run, it may not be able to run in real time to meet the requirements of driving.

DrivePX2
8 GB LPDDR4 (50+ GB/s)

Xavier
16 GB 256-bit LPDDR4 137 GB/s

Pegasus
16GB HBM2 RAM 1TB/s

I don't have datasheet for eyeq4.

I know elon mentioned memory but you can't just take him at his word. The biggest problem with DL GPU chips was when you had multiple chips trying to access memory which was problematic with a bus bandwidth speed of 50 GB/s which nvidia fixed by utilizing nv link 2 (1TB/s).

But again its not a reason why Tesla's current software CAN'T run on ap2.0.
 
Moderator note: It looks like 2018.39.5 qualifies as the first 9.0 release, and someone already created a thread for it, so I've moved 50-some-odd posts about 2018.39.5 to that thread:

Software Update 2018.39.5 a1c2332 (first 9.0 release)

Posts relevent to this particular release should go to that thread, as with most firmware threads.

I might break out some other topics to their own threads later. Please note that manually splitting threads like this is an imperfect process, and I apologize in advance for any confusion created.

Bruce.
 
That was fast. It seems to imply they are monitoring this thread.

Wish they had the gonads to comment now and then.

Remember those NDAs that were mentioned for Early Access/Adopters, whatever you want to call it... the R&D team at Tesla likely has even much more restrictive and easily enforcable NDAs. So please don’t question their gonads as I’m sure they have massive gonads to take on this incredibly difficult problem as their day job when they could easily go work at Google, Apple, or any other tech firm in Silicon Valley working on AI and/or computer vision and not have the weight of Tesla’s mission and Elon’s twitter habit on their shoulders.

If they are reading this... hats off to you guys on what you’ve accomplished to date.
 
just to be clear. everything you need to know about this process was posted further upthread. I do not distribute Tesla binary firmwares for legal reasons, so you need to find some other source than me. There was one and I listed it, now that it's closed, I do not know of any other public sources I could direct people to. If anybody knows better, perhaps they'll update here in the thread with more sources.
I totally understand. Thanks for the reply.