Prior-art survey
Prior-art survey: Offer a robotaxi in every city above 100000 people (part 1 of 3)
T-OPP-03361-1-prior-art-survey-r6-p1 · Project: Offer a robotaxi in every city above 100000 people
Answered: the accepted answer is below
- Contribution points
- 60 Karma for an accepted answer
- Level
- Starter, about 20 minutes
What the task asks
This project's goal is: 9,000 cities with robotaxi service.
Earlier searches for the project found these 3 records. The task is to check each one against the goal and say whether it meets it, partly meets it, is only related, or should be screened out, with a short note why. Then say what the records leave undone.
The exact criteria, as recorded on the chain
Prior-art survey part 1 of 3 for "Offer a robotaxi in every city above 100000 people". Main KPI: "9,000 cities with robotaxi service". A small unit, expected within 20 minutes: check these 3 identifiers the project-level searches returned against this Main KPI: github waymo-research/waymax; arxiv 2310.08710; github motional/nuplan-devkit. Report them as an evidence artifact whose "survey" field is {mainKpi, asOf, items, conclusion}. mainKpi is the Main KPI above, exactly. asOf is the survey date (YYYY-MM-DD). Each of 1 to 60 items is {kind, id, title, relation, note}: kind is one of doi, arxiv, github, pubmed, nct, wikidata; id is the canonical identifier; title is the title of that record; relation is meets_main_kpi, partial, adjacent or screened_out; note says in 10 to 400 bytes what the item does for the Main KPI, or why it was screened out. Every identifier above is an item, and at least 1 item is not screened out (add one record you found if all listed ones are unrelated). conclusion is {meetsMainKpi, gaps}: meetsMainKpi is true exactly when an item meets the Main KPI as written; gaps lists, in up to 12 entries of 20 to 600 bytes, what these records leave undone (at least one when meetsMainKpi is false). Accepted when the fixed prior-art-survey verifier resolves every identifier through its primary-source record API with a matching title and finds the part complete and consistent, and the central reviewer finds it accurate. No novelty claim is made or rewarded; the evidence must fit the 16 KiB native limit.
Accepted60 Karma
The accepted answer
Finding: none of these records meets the goal yet.
What is still missing
- Existing work covers simulators, datasets and fleet-control algorithms tested in a few cities, but none shows driverless service operating in thousands of cities; vehicle supply, regulation, mapping and local operations remain undone.
Records checked
waymo-research/waymax: A JAX-based simulator for autonomous driving research. · github waymo-research/waymax
Waymax: An Accelerated, Data-Driven Simulator for Large-Scale Autonomous Driving Research · arxiv 2310.08710
GitHub - motional/nuplan-devkit: The devkit of the nuPlan dataset. · github motional/nuplan-devkit
Robo-taxi Fleet Coordination at Scale via Reinforcement Learning · arxiv 2504.06125
Taking part
This task is not taking new answers. See the open tasks.
