ROS Index
No version for distro humble. Known supported distros are highlighted in the buttons above.
No version for distro jazzy. Known supported distros are highlighted in the buttons above.
No version for distro kilted. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.
Repository Summary
| Description | A scenario-based simulation framework for Autoware |
| Checkout URI | https://github.com/tier4/scenario_simulator_v2.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2025-07-31 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| agnocast_wrapper | 16.10.0 |
| get_parameter | 16.10.0 |
| arithmetic | 16.10.0 |
| geometry | 16.10.0 |
| scenario_simulator_exception | 16.10.0 |
| simple_junit | 16.10.0 |
| status_monitor | 16.10.0 |
| concealer | 16.10.0 |
| embree_vendor | 16.10.0 |
| zmqpp_vendor | 16.10.0 |
| kashiwanoha_map | 16.10.0 |
| simple_cross_map | 16.10.0 |
| cpp_mock_scenarios | 16.10.0 |
| openscenario_experimental_catalog | 16.10.0 |
| openscenario_interpreter | 16.10.0 |
| openscenario_interpreter_example | 16.10.0 |
| openscenario_interpreter_msgs | 16.10.0 |
| openscenario_preprocessor | 16.10.0 |
| openscenario_preprocessor_msgs | 16.10.0 |
| openscenario_utility | 16.10.0 |
| openscenario_validator | 16.10.0 |
| openscenario_visualization | 16.10.0 |
| real_time_factor_control_rviz_plugin | 16.10.0 |
| scenario_simulator_v2 | 16.10.0 |
| behavior_tree_plugin | 16.10.0 |
| do_nothing_plugin | 16.10.0 |
| simple_sensor_simulator | 16.10.0 |
| simulation_interface | 16.10.0 |
| traffic_simulator | 16.10.0 |
| traffic_simulator_msgs | 16.10.0 |
| random_test_runner | 16.10.0 |
| scenario_test_runner | 16.10.0 |
README
scenario_simulator_v2
Scenario testing framework for Autoware.
Documentation
See Documentation See C++ API Documentation
CONTRIBUTING
How to contribute
Thank you for your interest in improving scenario_simulator_v2. This contributor guidelines will help you get started.
If you have any questions, please feel free to make GitHub issues for asking your question.
Before you get started
To avoid duplicate work, please review current issues and pull requests.
Contribution workflow
Please take the following steps:
- Fork this repository.
- Clone down the repository to your local machine.
- Create a new branch from the
master. See Branch naming rules below. - Commit your changes to the branch and push the commit to your GitHub repository that was forked in Step 1.
- Open a Pull Request (PR). Our CI workflows will automatically test your changes. See Continuous integration below.
- The maintainers will review your PR. Once the PR is approved, the code will be merged into the
masterbranch. See Code review below.
Branch naming rules
Feature development
Each new feature development should be worked on in its own branch.
Please add the feature/ prefix to your branch name. For example:
feature/(name of the feature you are developing)
Bugfix
Please add the fix/ prefix to your branch name. For example:
fix/(name of bug what you are fixing)
Release
Only maintainers create the release/ branch.
release/prepare_(version_tag)
The release branches are used only to update the release notes. An example is here.
Continuous integration
Your changes proposed in your pull request will be tested automatically by the following checks:
| Checks | Description |
|---|---|
|
Build each package independently, run linters, unit tests and scenario tests. |
 |
Checking the branch is up to date. This workflow works on merge queue. |
 |
Checking the label for version control is labeled. |
|
Build the documentation sites. |
|
Checking the URLs in documentation are valid. |
|
Checking text files contain the blank line at the end of the files. |
|
Bump new version and create a release. This workflow works on merge queue. |
|
Run a spell checker and add warnings to the PR. |
If you contribute to the documentation, your changes should pass the checks below:
| Checks | Description |
|---|---|
|
Checking the branch is up to date. This workflow works on merge queue. |
|
Checking the label for version control is labeled. |
|
Build the documentation sites. |
|
Checking the URLs in documentation are valid. |
|
Bump new version and create a release. This workflow works on merge queue. |
|
Run a spell checker and add warnings to the PR. |
Code review
Any changes to the code or documentation are subject to code review. Maintainers will review your pull request.
As a good practice, reply to the reviewer’s comment with a link to your changes (e.g., Fixed in a0b1c2d).
To keep the commit hashes consistent, please DO NOT force-push the commit to your pull request during the code review.
If you want to force-push the commit during the review, please contact the maintainers for approval in advance.
If at least one maintainer approves your pull request and all checks are passed, your pull request will be merged into the master branch.
Pull requests must be labeled bump major, bump minor or bump patch.
Please follow the criteria below to determine which label to apply.
- If there is a destructive change to the scenario or traffic_simulator API, label it label it with
bump major. - If the scenario or traffic_simulator API has some additional functionality but no destructive changes, label it with
bump minor. - If there is no additional functionality and full backward compatibility is ensured, label it with
bump patch.
If you are in any doubt, please consult the maintainers @hakuturu583,@yamacir-kit,@HansRobo.
Update Documentation
If your pull request changes the behavior of the software, please update the documentation in the docs/ directory.
File truncated at 100 lines see the full file
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.
No version for distro noetic. Known supported distros are highlighted in the buttons above.