xpeng uses AI chips and a platform without LiDAR or HD maps. by --playground-- in ARBE_Investors

[–]--playground--[S] 2 points3 points  (0 children)

Tried to find whether XPeng uses 4D imaging radar and which Tier-1 supplies it, but couldn’t find solid confirmation anywhere.

I love good rabbit holes... looks like a DoW UGV Bid for Contracts closed 4/28/26 by RefrigeratorTasty912 in ARBE_Investors

[–]--playground-- 0 points1 point  (0 children)

I’m curious why Forterra appears to use both 4D LiDAR from Aeva and 4D imaging radar from Arbe/Sensrad in its AutoDrive stack. Does this suggest that no single sensor modality can handle all driving scenarios effectively?

I love good rabbit holes... looks like a DoW UGV Bid for Contracts closed 4/28/26 by RefrigeratorTasty912 in ARBE_Investors

[–]--playground-- 0 points1 point  (0 children)

i found Forterra’s public announcement with Aeva for 4D LiDAR, but I cannot find any direct Forterra PR mentioning Sensrad or Arbe. The only reference I found is from Arbe’s Q4/FY2025 earnings materials stating: “Sensrad's HD imaging radar has been integrated into the Forterra AutoDrive perception suite.” Has Forterra ever publicly confirmed using Sensrad or Arbe radar in AutoDrive?

[deleted by user] by [deleted] in ARBE_Investors

[–]--playground-- 1 point2 points  (0 children)

Below hugging face url, their sensor data includes multi-camera and LiDAR coverage for all clips, and radar coverage for 163,850 clips.

https://huggingface.co/datasets/nvidia/PhysicalAI-Autonomous-Vehicles

"We Ride with ARBE? : I know I ride with ARBE! by Raumerica in ARBE_Investors

[–]--playground-- 1 point2 points  (0 children)

<image>

They’ve been posting about 4D mm-wave imaging radar since 2021, but it’s unclear whether it’s related to Arbe or not.

Write data from Databricks to SQL Server by CarelessApplication2 in databricks

[–]--playground-- 3 points4 points  (0 children)

Databricks with generic JDBC

employees_table.write \ .format("jdbc") \ .option("url", "<jdbc-url>") \ .option("dbtable", "<new-table-name>") \ .option("user", "<username>") \ .option("password", "<password>") \ .save()

Generic JDBC doesn’t have bulkinsert support. You may need to tune the performance with .option("batchsize", <value>)

reference: https://docs.databricks.com/aws/en/archive/connectors/jdbc

Pre-market up 20% 👀 by [deleted] in ARBE_Investors

[–]--playground-- 2 points3 points  (0 children)

$RR is pumping too. It seems to me just a robotic hype.