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

Port pinpoint to ros2 and update carma script #228

Merged
merged 4 commits into from
Jul 11, 2024

Conversation

MishkaMN
Copy link
Contributor

@MishkaMN MishkaMN commented Jul 9, 2024

PR Details

Description

This PR supports migration of pinpoint driver to ROS2 in this PR: usdot-fhwa-stol/carma-torc-pinpoint-driver#46

Related GitHub Issue

NA

Related Jira Key

https://usdot-carma.atlassian.net/browse/CAR-5907

Motivation and Context

Migration of pinpoint to ROS2

How Has This Been Tested?

Set the config and tried starting without issue. Just needs to test on actual Tahoe vehicle now.
NOTE: image intentionally comments out the other components other than pinpoint
image

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 JonSmet July 9, 2024 17:33
@MishkaMN MishkaMN self-assigned this Jul 9, 2024
@MishkaMN MishkaMN added the enhancement New feature or request label Jul 9, 2024
@@ -78,12 +76,12 @@ services:
command: bash -c 'source /opt/carma/install/setup.bash && ros2 launch /opt/carma/vehicle/config/drivers.launch.py drivers:=dsrc_driver'

torc-pinpoint-driver:
image: ${DOCKER_ORG}/carma-torc-pinpoint-driver:${DOCKER_TAG}
image: local/carma-torc-pinpoint-driver:SNAPSHOT
Copy link
Contributor

Choose a reason for hiding this comment

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

why is this a local build?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh sorry artifact from testing, replacing

@MishkaMN MishkaMN requested a review from saina-ramyar July 9, 2024 20:15
MishkaMN added a commit to usdot-fhwa-stol/carma-torc-pinpoint-driver that referenced this pull request Jul 11, 2024
<!-- Thanks for the contribution, this is awesome. -->

# PR Details
## Description
This PR updates the pinpoint driver to ROS2.
NOTE: integration test has only been done in local VM. Further
integration testing on the vehicle with pinpoint is needed.
Supporting PR:
usdot-fhwa-stol/carma-messenger#228

Also fixed CI to work on ROS2 and not run code coverage because there is
no unit test in this package. Sonar still checks for code smells or
bugs.
<!--- Describe your changes in detail -->

## Related GitHub Issue
NA
<!--- This project only accepts pull requests related to open GitHub
issues or Jira Keys -->
<!--- 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 DO NOT name partially fixed issues, instead open an issue
specific to this fix -->
<!--- Please link to the issue here: -->

## Related Jira Key
https://usdot-carma.atlassian.net/browse/CAR-5907
<!-- e.g. CAR-123 -->

## Motivation and Context
Migration to ROS2
<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?
Local VM integration test:
- launched using launch file

![image](https://github.com/usdot-fhwa-stol/carma-torc-pinpoint-driver/assets/20613282/2880ea28-a7e7-4449-8592-188495de73d5)

![image](https://github.com/usdot-fhwa-stol/carma-torc-pinpoint-driver/assets/20613282/d81bfc9c-a2b6-49d8-97f0-6037f8cc1f69)

Appears to be trying to reconnect as expected:

![image](https://github.com/usdot-fhwa-stol/carma-torc-pinpoint-driver/assets/20613282/57fe5d2f-eb81-4466-8ba1-0ef5251d7c3f)

Tested docker images build process with incremental process as well:

![image](https://github.com/usdot-fhwa-stol/carma-torc-pinpoint-driver/assets/20613282/0a1c5d25-486f-4a2e-b03a-56c4cf04a397)

it is also tested as docker-compose and its results are in
usdot-fhwa-stol/carma-messenger#228

<!--- 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
- [ ] My change requires a change to the documentation.
- [X] I have updated the documentation accordingly.
- [X] I have read the
[**CONTRIBUTING**](https://github.com/usdot-fhwa-stol/carma-platform/blob/develop/Contributing.md)
document.
- [X] I have added tests to cover my changes.
- [X] All new and existing tests passed.
@MishkaMN MishkaMN merged commit d2452e9 into develop Jul 11, 2024
3 checks passed
@MishkaMN MishkaMN deleted the car-5907-pinpoint-driver branch July 11, 2024 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants