-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Sensor/Detector Registration to Infrastructure Ambassador (#152)
<!-- Thanks for the contribution, this is awesome. --> # PR Details ## Description <!--- Describe your changes in detail --> Added additional information to the Infrastructure Registration Message including : - Port for transmitting relevant interactions - List of sensors/detectors to register for infrastructure instance Added functionality to process new registration message, trigger sensors/detectors registration interactions to prompt creation of sensors/detectors. Added functionality to process incoming Detected Object interactions from sensors and forward them via the new interactions port to registered infrastructure instances based on the sensor that reports the detection. ## 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? --> New functionality will be used to create sensor in CARLA and retrieve detection information for the VRU use case ## 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. --> Unit tested and Integration testing with XIL Cloud setup Only tested that CDASim properly processes Infrastructure registration and still forwards time sync messages. Further testing for detection interaction processing is advised once CARLA Ambassador work completes. ## 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. - [] I have updated the documentation accordingly. - [x] I have read the **CONTRIBUTING** document. [CARMA Contributing Guide](Contributing.md) - [x] I have added tests to cover my changes. - [x] All new and existing tests passed.
- Loading branch information
Showing
31 changed files
with
2,603 additions
and
384 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.