-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Remove tier4_ad_api_adaptor #3096
Remove tier4_ad_api_adaptor #3096
Comments
Hello @isamu-takagi -san, Lines 28 to 31 in c9c4546
Since this comment is present, I guess this issue is still relevant. Is there a timeline for this issue to be completed? (Is this low priority?) Could you provide a list of packages to be modified/refactored to achieve this task? |
@xmfcx RTC has not been deleted yet. This will be completed by migrating to this API. I'm currently implementing this API. |
@isamu-takagi thanks for the information. I couldn't find Cooperation API in the default_ad_api.
Is it being implemented into the Are there ongoing PRs for this task? |
There are no PRs for AD API yet. I'm currently changing the implementation to match the API. |
@isamu-takagi -san
mfc@bunny:~/projects/autoware$ rg "tier4_ad_api_adaptor" --hidden --no-ignore -g '!*.rst' -g '!{build,install,log,**/.git,**/.idea}/**'
./autoware-nightly.repos
22: universe/external/tier4_ad_api_adaptor: # TODO(TIER IV): Migrate to AD API and remove this repository entry.
24: url: https://github.com/tier4/tier4_ad_api_adaptor.git
./src/universe/external/tier4_ad_api_adaptor/.github/workflows/sync-micro-bus.yaml
25: sync-target-repository: https://github.com/tier4/tier4_ad_api_adaptor
./autoware.repos
37: universe/external/tier4_ad_api_adaptor: # TODO(TIER IV): Migrate to AD API and remove this repository entry.
39: url: https://github.com/tier4/tier4_ad_api_adaptor.git |
@xmfcx The following packages in tier4_ad_api_adaptor are used when
Releted files: |
Checklist
Description
Currently, tier4_ad_api_adaptor is imported as a sample API. However, it is now possible to drive the vehicle even with the newly introduced AD API. It's confusing to have two API examples, so I plan to remove tier4_ad_api_adaptor.
Purpose
Unify API samples to default_ad_api.
Possible approaches
Definition of done
Remove tier4_ad_api_adaptor from autoware.repos
The text was updated successfully, but these errors were encountered: