Skip to content
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

Fix/assorted fix for yield #2200

Merged
merged 22 commits into from
Dec 5, 2023
Merged

Fix/assorted fix for yield #2200

merged 22 commits into from
Dec 5, 2023

Conversation

MishkaMN
Copy link
Contributor

@MishkaMN MishkaMN commented Nov 30, 2023

PR Details

Description

  • Enabled motion computation for sensor objects in config
  • reduced minimum_obstacle_speed for yield
  • fixed a lot of out of range errors in yield_plugin
  • using basic_autonomy library, added yield functionalities to stop_and_wait and light_controlled_intersection_tactical_plugins as they will be used for TRB demonstrations. Only inlanecruising_plugin was able to call yield_plugin before. Perhaps if this paradigm should continue is for future discussion.
  • added tactical_plugin_service_call_timeout as a global parameter in VehicleConfigParams as trucks sometime can require longer planning including yield_plugin this time in simulation as well. This enables easier modification of the timeout that can be applied to plan_delegator and other tactical plugins that call other tactical plugins such as when calling yield_plugin.
    ... more below

Related GitHub Issue

Number of lanelets returned is not enough: #2198
timeouts are not enough for tactical plugin and yield plugin - increased both timeouts: #2199

Related Jira Key

Motivation and Context

How Has This Been Tested?

Types of changes

  • Defect fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that cause existing functionality to change)

Checklist:

  • I have added any new packages to the sonar-scanner.properties file
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@MishkaMN MishkaMN requested a review from adamlm November 30, 2023 20:44
@MishkaMN MishkaMN marked this pull request as draft November 30, 2023 20:50
@MishkaMN MishkaMN marked this pull request as ready for review December 4, 2023 20:42
adamlm pushed a commit to usdot-fhwa-stol/carma-config that referenced this pull request Dec 4, 2023
<!-- Thanks for the contribution, this is awesome. -->

# PR Details
## Description
Supports usdot-fhwa-stol/carma-platform#2200

<!--- Describe your changes in detail -->

## Related Issue

<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->

## Motivation and Context

<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?

<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Defect fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that cause existing functionality
to change)

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [ ] I have added any new packages to the sonar-scanner.properties file
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
[CARMA Contributing
Guide](https://github.com/usdot-fhwa-stol/carma-platform/blob/develop/Contributing.md)
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
carma_wm/src/WMListenerWorker.cpp Outdated Show resolved Hide resolved
yield_plugin/src/yield_plugin.cpp Outdated Show resolved Hide resolved
carma_wm/src/WMListenerWorker.cpp Outdated Show resolved Hide resolved
inlanecruising_plugin/src/inlanecruising_plugin.cpp Outdated Show resolved Hide resolved
inlanecruising_plugin/src/inlanecruising_plugin.cpp Outdated Show resolved Hide resolved
yield_plugin/src/yield_plugin.cpp Outdated Show resolved Hide resolved
yield_plugin/src/yield_plugin.cpp Outdated Show resolved Hide resolved
adamlm pushed a commit to usdot-fhwa-stol/carma-config that referenced this pull request Dec 5, 2023
<!-- Thanks for the contribution, this is awesome. -->

# PR Details
## Description
Supports usdot-fhwa-stol/carma-platform#2200
This is similar PR to
#289, however this
adds the specific configurations to the TRB folder. This makes the
earlier PR unnecessary, so reverting it:
#288
<!--- Describe your changes in detail -->

## Related Issue
usdot-fhwa-stol/carma-platform#2199
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->

## Motivation and Context
using yield_plugin in TRB scenario
<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?
Simulation computer cdasim
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Defect fix (non-breaking change that fixes an issue)
- [X] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that cause existing functionality
to change)

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [X] I have added any new packages to the sonar-scanner.properties file
- [X] My change requires a change to the documentation.
- [X] I have updated the documentation accordingly.
- [X] I have read the **CONTRIBUTING** document.
[CARMA Contributing
Guide](https://github.com/usdot-fhwa-stol/carma-platform/blob/develop/Contributing.md)
- [X] I have added tests to cover my changes.
- [X] All new and existing tests passed.
@MishkaMN MishkaMN requested a review from adamlm December 5, 2023 14:24
basic_autonomy/include/basic_autonomy/basic_autonomy.hpp Outdated Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Outdated Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Outdated Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Outdated Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Show resolved Hide resolved
@MishkaMN MishkaMN requested a review from adamlm December 5, 2023 16:57
basic_autonomy/include/basic_autonomy/basic_autonomy.hpp Outdated Show resolved Hide resolved
basic_autonomy/include/basic_autonomy/basic_autonomy.hpp Outdated Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Show resolved Hide resolved
basic_autonomy/src/basic_autonomy.cpp Show resolved Hide resolved
@MishkaMN MishkaMN requested a review from adamlm December 5, 2023 18:18
@MishkaMN MishkaMN merged commit 889ce91 into develop Dec 5, 2023
2 of 3 checks passed
@MishkaMN MishkaMN deleted the fix/assorted-fix-for-yield branch December 5, 2023 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants