Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Qwen-Drive

AI overview

Sign in and the AI will write an overview from our coverage.

Headlines · 4

  1. Qwen-Drive Resume Runs May Skip New Predictions

    A static review of Qwen-Drive’s official batch runner found that it reads scene tokens from existing output files and skips scenes already marked complete. The token check does not verify whether the previous run used the same weights, planning mode, seed or candidate count, so changing configuration and reusing an output directory can skip new trajectory predictions or leave results from different configurations mixed together. The review recommends separate output directories for new configurations, configuration hashes and run identifiers, records of requested and newly predicted scene counts, and explicit timing boundaries. Model loading may still use the GPU even when all scenes are skipped. The review did not download model weights, run GPU work, train the model or conduct a driving evaluation, leaving latency, memory use, success rates and trajectory quality unknown.

    掘金 · 人工智能 · 🔥 0
  2. Why Qwen-Drive Trajectories Do Not Transfer Directly to Mobile Robots

    An analysis argues that Qwen-Drive's future x, y, and heading outputs cannot be adapted to a mobile robot merely by renaming coordinates and scaling distances. It proposes checking coordinate frames, observation timestamps, differential-drive kinematics, sensing coverage, memory, and training labels before deployment, then presents a pending migration acceptance record for an indoor door-seeking task. The author reports no weight downloads, model training, simulation, or robot-closed-loop experiments, so the framework has not demonstrated successful cross-embodiment transfer.

    掘金 · 人工智能 · 🔥 0
  3. Qwen-Drive's 91.4 NAVSIM score is an oracle best-of-6 result

    A Juejin AI technical audit finds that Qwen-Drive-1.0-RL's reported 91.4 PDMS score on NAVSIM v1.1 navtest comes from selecting the highest-scored trajectory among six candidates per scene using evaluation-time PDMS, while the default single trajectory scores 90.7. The analysis says this oracle result describes the potential of the candidate set rather than deployable selection ability, and it also examines evaluation denominators, time grids, data splits, and closed-loop evidence. The audit relied on official documentation, papers, and source code without running the model, simulator, scorer, or vehicle tests.

    掘金 · 人工智能 · 🔥 0
  4. Qwen-Drive’s Trajectory Pipeline and Integration Boundaries

    A Juejin analysis of Qwen-Drive’s public code and technical report maps how its Qwen3.5-4B visual-language backbone feeds separate BEV perception and planning components. The planning interface can return multiple candidate trajectories, while the singular trajectory property simply selects the first candidate rather than scoring it; the reported default is 50 future points per trajectory over five seconds at a 10 Hz data interval. The review also details camera, motion-state and navigation inputs, training stages, and the boundary between trajectory generation, candidate selection, and downstream control.

    掘金 · 人工智能 · 🔥 0

Experience and discussion from the community

Share my Qwen-Drive experienceAsk about Qwen-Drive

Nobody has shared their experience with Qwen-Drive yet.