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

Move CARMA-Streets Time Synchronization to CARMA-Streets Plugin #549

Open
paulbourelly999 opened this issue Jul 13, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@paulbourelly999
Copy link
Contributor

Summary

Currently the CDASim Adapter handles forwarding Time Sync messages directly to CARMA-Streets. A more appropriate implementation of this functionality would be to allow the CARMA-Streets plugin to extend our PluginClientTimeAware class to make it aware of simulation.

Reasoning for new functionality

This would be a more intuitive split of responsibilities and would allow the CDASimAdapter to be Kafka independent

@paulbourelly999 paulbourelly999 added the enhancement New feature or request label Jul 13, 2023
dan-du-car pushed a commit that referenced this issue Jul 20, 2023
#550)

…ets plugin

+ Update CARMA-Streets Plugin to be simulation time aware

<!-- Thanks for the contribution, this is awesome. -->

# PR Details
## Description

<!--- Describe your changes in detail -->
Move Kafka time producer for CARMA-Streets time synchronization to
CARMA-Streets plugin. This removes unnecessary dependency on kafka for
CDASimAdapter and also makes CARMA-Streets Plugin contain entire
interface to CARMA-Streets including simulation. CARMA-Streets Plugin
now extends our simulation time aware PluginClient which can be further
extended to listen for simulated messages.
## Related Issue
#549
<!--- 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?
Locally integration testing with python time step script to send udp
time step messages.
<!--- 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! -->

- [ ] 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.
[V2XHUB Contributing
Guide](https://github.com/usdot-fhwa-OPS/V2X-Hub/blob/develop/Contributing.md)
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
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

No branches or pull requests

1 participant