Releases: tier4/scenario_simulator_v2
22.6.3
Description
Abstract
This PR makes the StatusMonitor threshold configurable as a simulator parameter.
Background
The default execution constraints are too restrictive for scenarios involving extensive map data, leading to unintended interruptions during evaluation. I have made these constraints configurable to allow for more flexibility during heavy processing tasks.
Reference
Regression Test: 1 Failure. It passed multiple times in my local environment, so I suspect this is a flaky test.
Destructive Changes
None
Known Limitations
None
Related Issues
22.6.2
Description
Abstract
Previously, simulation_api_schema::TrafficSignal opperator of TrafficLight class does not fill relation_ids field and this pull-reuest fixes this.
Background
A bug was reported where traffic light topics were incomplete when using the detected channel.
After investigation, I found that when configuring only the detected channel without configuring ground-truth channel, the relation_ids field was not set, resulting in missing content.
This pull request fundamentally resolves this issue by adding the relation_ids field using a conversion operator rather than adding it each time.
References
Regression Test: OK
Destructive Changes
None
Known Limitations
None
Related Issues
22.6.1
Abstract
This PR will remove some of Boost dependency code.
boost::filesystemboost::variant- iterator related things (replaced by C++17 algorithm)
Related Issues
22.6.0
Description
Abstract
This pull-request adds traffic signal predictions to V2I traffic light topic.
The predictions are calculated from traffic signal phase definitions.
Background
The predictions field has introduced into autoware_perception_msgs/msg/TrafficLightGroup.msg.
autowarefoundation/autoware_msgs#134
Details
The predictions are published only when the traffic light message has predictions field.
References
Regression Test: OK
Destructive Changes
None
Known Limitations
The prediction calculation only takes into account the current State Sync setting, not intermediate enabling/disabling.
Related Issues
22.5.1
Description
Abstract
This pull-request fixes the build CI errors by using ros image.
And I added some workflow optimizations.
Background
After GitHub runner image update for ubuntu22 (version: 20260112.2 ), the build CI started to fail.
https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20260112.2
Destructive Changes
None
Known Limitations
The build CI for RelWithDebInfo is still failed due to lack of disk space
Related Issues
22.5.0
Description
Abstract
This pull-request add a support RoutingAction__use_lane_ids_for_routing parameter for AcquirePositionAction.
Background
Originally, I was intended to implement the content of this pull-request in #1611
But I forgot to implement it.
References
Regression Test: OK
Destructive Changes
None
Known Limitations
None
Related Issues
22.4.0
Description
Abstract
This pull request clearly separates ground-truth state and Autoware detected state.
This is implemented in both conventional and v2i traffic lights, and in the scenario, Autoware detected state is indicated by adding _detected to the end of the traffic light ID for each traffic light model.
This pull request also adds EnableTrafficSignalV2IFeatureAction@v1 / DisableTrafficSignalV2IFeatureAction@v1 to support synchronization of conventional traffic light -> V2I traffic light states, making it easier to mimic actual V2I traffic lights where the optical state output and the V2I output over the network are the same.
Details
See TrafficLightsArchitecture.md in the pull-request
Traffic Lights Architecture - Scenario testing framework for Autoware.pdf
References
Regression Test: OK
Destructive Changes
None
Known Limitations
None
Related Issues
22.3.5
Bumps docker/bake-action from 6.9.0 to 6.10.0.
Release notes
Sourced from docker/bake-action's releases.
v6.10.0
- Check provenance attestation set in bake definition before overriding by
@crazy-maxin docker/bake-action#359- Bump
@docker/actions-toolkitfrom 0.63.0 to 0.68.0 in docker/bake-action#360- Bump js-yaml from 3.14.1 to 3.14.2 in docker/bake-action#357
Full Changelog: docker/bake-action@v6.9.0...v6.10.0
Commits
5be5f02Merge pull request #360 from docker/dependabot/npm_and_yarn/docker/actions-to...4f25520chore: update generated contenteeacb3dchore(deps): Bump@docker/actions-toolkitfrom 0.63.0 to 0.68.0cce027fMerge pull request #358 from docker/dependabot/github_actions/actions/checkout-653ce91fMerge pull request #357 from docker/dependabot/npm_and_yarn/js-yaml-3.14.26b8437dchore(deps): Bump actions/checkout from 5 to 6d14785bMerge pull request #359 from crazy-max/check-attest-definition597dc07chore: update generated content8ba51accheck provenance attestation set in bake definition before overriding23c049fchore(deps): Bump js-yaml from 3.14.1 to 3.14.2- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Related Issues
22.3.4
22.3.3
Bumps actions/upload-artifact from 5 to 6.
Release notes
Sourced from actions/upload-artifact's releases.
v6.0.0
v6 - What's new
[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (
runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.Node.js 24
This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.
What's Changed
- Upload Artifact Node 24 support by
@salmanmkcin actions/upload-artifact#719- fix: update
@actions/artifactfor Node.js 24 punycode deprecation by@salmanmkcin actions/upload-artifact#744- prepare release v6.0.0 for Node.js 24 support by
@salmanmkcin actions/upload-artifact#745Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0
Commits
b7c566aMerge pull request #745 from actions/upload-artifact-v6-releasee516bc8docs: correct description of Node.js 24 support in READMEddc45eddocs: update README to correct action name for Node.js 24 support615b319chore: release v6.0.0 for Node.js 24 support017748bMerge pull request #744 from actions/fix-storage-blob38d4c79chore: rebuild dist7d27270chore: add missing license cache files for@actions/core,@actions/io, and mi...5f643d3chore: update license files for@actions/artifact@5.0.1 dependencies1df1684chore: update package-lock.json with@actions/artifact@5.0.1b5b1a91fix: update@actions/artifactto ^5.0.0 for Node.js 24 punycode fix- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)