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

[composites] Reduce circulation when the parallel node policy is SuccessOnOne #440

Merged
merged 3 commits into from
Sep 3, 2024

Conversation

starrye
Copy link
Contributor

@starrye starrye commented Mar 20, 2024

motivation: reduce circulation when the parallel node policy is SuccessOnOne

Update: Iterate in reverse order, updating new_status and self.current_child when the first child whose status iscommon.Status.SUCCESS is found, then terminating the loop

@starrye
Copy link
Contributor Author

starrye commented Mar 20, 2024

@stonier please review

Copy link
Collaborator

@sea-bass sea-bass left a comment

Choose a reason for hiding this comment

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

This looks good, though I have a suggestion for simpler syntax.

py_trees/composites.py Outdated Show resolved Hide resolved
@sea-bass sea-bass changed the title [composites]reduce circulation when the parallel node policy is SuccessOnOne [composites] Reduce circulation when the parallel node policy is SuccessOnOne Sep 3, 2024
@sea-bass sea-bass merged commit 7d3d907 into splintered-reality:devel Sep 3, 2024
2 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants