Skip to content

Align custom traffic action with osc #523

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

Merged
merged 5 commits into from
Sep 7, 2021

Conversation

caspar-ai
Copy link
Contributor

Reference to a related issue in the repository

Closes #522

Add a description

Add a second string field to the custom action to mirror that in the OSC definitions.

In line with standard OSI the field is optional so this is not a breaking change.

Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:

  • My suggestion follows the style and contributors guidelines.
  • I have taken care about the documentation.
  • I have done the DCO signoff.
  • My changes generate no errors when passing CI tests.
  • I have successfully implemented and tested my fix/feature locally.
  • Appropriate reviewer(s) are assigned.

@caspar-ai caspar-ai added Bug Problems in the build system, build scripts, etc or faults in the interface. TrafficParticipants The group in the ASAM development project working on traffic participants. labels Jun 2, 2021
@caspar-ai caspar-ai requested review from pmai and clemenshabedank June 2, 2021 08:17
@caspar-ai caspar-ai self-assigned this Jun 2, 2021
caspar-ai added 2 commits June 2, 2021 09:17
Signed-off-by: Caspar de Haes <caspar.dehaes@five.ai>
Signed-off-by: Caspar de Haes <caspar.dehaes@five.ai>
@caspar-ai caspar-ai force-pushed the feature/align-custom-traffic-action-with-osc branch from 2fbd5ba to e3452d3 Compare June 2, 2021 08:17
@caspar-ai caspar-ai added the ReadyForCCBReview Indicates that this MR is ready for a final review and merge by the CCB. label Jun 3, 2021
Comment on lines 490 to 496
// The custom command given to the traffic participant.
//
optional string command = 2;

// The type of the custom command given to the traffic participant.
//
optional string command_type = 3;
Copy link

Choose a reason for hiding this comment

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

Output CCB 09.06.2021:

  1. Please provide more documentation on the "command" and "command_type" messages, stating the difference between them and how/in which situations should it be used.
  2. As a "note", please mention for both commands that they are mapped to OSC.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @kmeids I have updated the comments as suggested.

Does that look OK to you?

Copy link

@kmeids kmeids left a comment

Choose a reason for hiding this comment

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

Please check comments

@kmeids kmeids removed the ReadyForCCBReview Indicates that this MR is ready for a final review and merge by the CCB. label Jun 9, 2021
Signed-off-by: Caspar de Haes <caspar.dehaes@five.ai>
@caspar-ai caspar-ai added the ReadyForCCBReview Indicates that this MR is ready for a final review and merge by the CCB. label Jun 14, 2021
@clemenshabedank clemenshabedank added this to the V3.4.0 milestone Jun 23, 2021
@caspar-ai
Copy link
Contributor Author

@kmeids any update from the CCB group about whether this can be merged?

@kmeids
Copy link

kmeids commented Jul 21, 2021

CCB Output 21.07.2021

  1. @max-rosin please do a documentation check.
  2. @pmai to merge after documentation check is done.

@kmeids kmeids added Documentation Everything which impacts the quality of the documentation and guidelines. ReadyToMerge This PR has been approved to merge and will be merged by a member of the CCB. and removed ReadyForCCBReview Indicates that this MR is ready for a final review and merge by the CCB. labels Jul 21, 2021
Co-authored-by: max-rosin <62103539+max-rosin@users.noreply.github.com>
Signed-off-by: Caspar de Haes <caspar.dehaes@five.ai>
@caspar-ai caspar-ai force-pushed the feature/align-custom-traffic-action-with-osc branch from a4edb29 to 6aaadca Compare August 10, 2021 09:25
@caspar-ai
Copy link
Contributor Author

@max-rosin I agreed with your comment suggests and have applied those changes. Is there anything else to do on the documentation side?

@pmai if not, I think over to you to merge.

@stefancyliax stefancyliax merged commit cddc509 into master Sep 7, 2021
@stefancyliax stefancyliax deleted the feature/align-custom-traffic-action-with-osc branch October 21, 2021 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Problems in the build system, build scripts, etc or faults in the interface. Documentation Everything which impacts the quality of the documentation and guidelines. ReadyToMerge This PR has been approved to merge and will be merged by a member of the CCB. TrafficParticipants The group in the ASAM development project working on traffic participants.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistency between OSC and OSI for custom traffic actions
5 participants