Thinklab-SJTU / Thinklab-SJTU/Bench2Drive

non-reactive or reactive?

Open
#209 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.9k
Forks
144
PR merge metrics
No merged PRs in 30d

Description

In the Bench2Drive test routes, do the surrounding agents respond to the ego vehicle's actions? In other words, is this a non-reactive closed-loop test or a reactive closed-loop test?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Bench2Drive test routes and any project material describing closed-loop evaluation. Determine whether surrounding agents respond to ego-vehicle actions, then document the result as either non-reactive or reactive closed-loop testing.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.