Skip to content

Irregular behaviour of planning modules when object IDs are above 110 #188

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

Open
AlexAntn opened this issue Mar 22, 2016 · 1 comment
Open

Comments

@AlexAntn
Copy link
Collaborator

goalCompiler and geometricGrounding modules start mis-behaving when the IDs of the objects are between 110 and 129.

This is probably due to a misunderstanding of the tags for the hands (11 and 12).

@AlexAntn AlexAntn added the bug label Mar 22, 2016
@gsaponaro
Copy link
Collaborator

This problem manifests itself only in these conditions (i) after 15-20 restart commands (startPlanner) are issued, and (ii) there are 5-6 objects in the scene, and (iii) modules are never restarted.

In the review we will only issue a lower number of startPlanner commands.

Fixing this requires to change a fair bit of the planner code and message exchange, so @AlexAntn and I think that it's better to postpone this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants