Skip to content

Fix/concealer 7/transition #1584

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Apr 25, 2025
Merged

Fix/concealer 7/transition #1584

merged 9 commits into from
Apr 25, 2025

Conversation

yamacir-kit
Copy link
Collaborator

@yamacir-kit yamacir-kit commented Apr 22, 2025

Description

Abstract

This pull request fixes some bugs in Autoware state control in scenario_simulator_v2.

Background

None.

Details

  • FieldOperatorApplication::initialize, plan, and engage now wait if the current Autoware state is earlier than expected. This allows Autoware to transition states appropriately even if it takes a long time to process a service request after accepting it.
  • The member function FieldOperatorApplication::waitForAutowareStateToBe now takes not only the target state but also the state at the time of the call. This allows state waiting to be performed for that range of states, and also allows the wait to be properly terminated if the state is ahead of the target state (which occurs when the member function is called and the Autoware state changes at the same time).
  • The default retry interval for service requests has been extended from 1 second to 3 seconds. This means that requests are rarely resent endlessly when Autoware takes more than 1 second to respond to a service. However, there are no specifications for how long Autoware requires for a service response, and it is also affected by machine specifications, so it is not possible to set an appropriate value based on technical grounds. Therefore, 3 seconds is also just an arbitrary number that has been experimentally verified to not cause any major problems at present.

References

None.

Destructive Changes

None.

Known Limitations

None.

@yamacir-kit yamacir-kit added bug Something isn't working bump patch If this pull request merged, bump patch version of the scenario_simulator_v2 labels Apr 22, 2025
@yamacir-kit yamacir-kit self-assigned this Apr 22, 2025
Copy link

github-actions bot commented Apr 22, 2025

Checklist for reviewers ☑️

All references to "You" in the following text refer to the code reviewer.

  • Is this pull request written in a way that is easy to read from a third-party perspective?
  • Is there sufficient information (background, purpose, specification, algorithm description, list of disruptive changes, and migration guide) in the description of this pull request?
  • If this pull request contains a destructive change, does this pull request contain the migration guide?
  • Labels of this pull request are valid?
  • All unit tests/integration tests are included in this pull request? If you think adding test cases is unnecessary, please describe why and cross out this line.
  • The documentation for this pull request is enough? If you think adding documents for this pull request is unnecessary, please describe why and cross out this line.

Copy link

Failure optional scenarios

Note

This is an experimental check and does not block merging the pull-request.
But, please be aware that this may indicate a regression.

scenario failed: execution_time_test
      <failure type="SimulationFailure" message="CustomCommandAction typed &quot;exitFailure&quot; was triggered by the named Conditions {&quot;update time checker&quot;, &quot;avoid startup&quot;}: {&quot;update time checker&quot;: Is the /simulation/interpreter/execution_time/update (= 0.007603000000000000382915921193) is greaterThan 0.005?}, {&quot;avoid startup&quot;: Is the simulation time (= 1.050000000000000266453525910038) is greaterThan 1.000000000000000000000000000000?}" />

@yamacir-kit yamacir-kit requested a review from HansRobo April 24, 2025 05:56
@yamacir-kit yamacir-kit marked this pull request as ready for review April 24, 2025 05:57
Copy link
Member

@HansRobo HansRobo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, waiting for green CIs.

Copy link

Failure optional scenarios

Note

This is an experimental check and does not block merging the pull-request.
But, please be aware that this may indicate a regression.

scenario failed: execution_time_test
      <failure type="SimulationFailure" message="CustomCommandAction typed &quot;exitFailure&quot; was triggered by the named Conditions {&quot;update time checker&quot;, &quot;avoid startup&quot;}: {&quot;update time checker&quot;: Is the /simulation/interpreter/execution_time/update (= 0.005442999999999999921618254461) is greaterThan 0.005?}, {&quot;avoid startup&quot;: Is the simulation time (= 13.000000000000049737991503207013) is greaterThan 1.000000000000000000000000000000?}" />

Copy link

@HansRobo HansRobo merged commit 6b25dcb into master Apr 25, 2025
14 checks passed
@github-actions github-actions bot deleted the fix/concealer-7/transition branch April 25, 2025 03:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working bump patch If this pull request merged, bump patch version of the scenario_simulator_v2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants