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.

Sign up for GitHub

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

Jump to bottom

decompose complex tasks #28

Open
rayvburn opened this issue Feb 13, 2022 · 1 comment
Open

decompose complex tasks #28

rayvburn opened this issue Feb 13, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@rayvburn
Copy link
Owner

E.g. SitDown should not consist of MoveToGoal -> SitDown -> Sitting -> StandingUp -> Standing. A better approach would use MoveToGoal, SitDown and StandUp (separately) - user has better control over scenario execution then.
@rayvburn rayvburn added the enhancement New feature or request label Feb 13, 2022
@rayvburn
Copy link
Owner Author

Such a decomposition disallows creation of object-oriented tasks, e.g. actor following robot while 'talking'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rayvburn