Fix requestSpeedChange sets target_speed only when it's reached #40
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Abstract
The statement
target_speed_ = target_speed.getAbsoluteValue(getCanonicalizedStatus(), other_status_);
in firs example sets the target speed only in cases where the target speed has already been reached, which seems counter intuitive. This statement’s position is inconsistent with second example.scenario_simulator_v2/simulation/traffic_simulator/src/entity/entity_base.cpp
Lines 471 to 480 in b931744
scenario_simulator_v2/simulation/traffic_simulator/src/entity/entity_base.cpp
Lines 458 to 464 in b931744
Details
Described statement is moved down, outside of the “if” statement. This way the most up to date target speed will be set on each iteration until the target speed is reached. This is consistent with
continuous
case.References
Jira ticket: internal link
Destructive Changes
There are no destructive changes.