-
Notifications
You must be signed in to change notification settings - Fork 156
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
Duplicate planning scene msgs in solution #638
Comments
captain-yoshi
added a commit
to captain-yoshi/moveit_task_constructor
that referenced
this issue
Dec 14, 2024
Example with an object in the scene, the start scene world is the same as the first diff scene from the first sub trajectory. Also should the sub trajectories Start scene name: (noname)
robot_state: ...
world:
collision_objects[]
collision_objects[0]:
header:
seq: 0
stamp: 0.000000000
frame_id: base
pose:
position:
x: 0
y: 0
z: 0
orientation:
x: 0
y: 0
z: 0
w: 1
id: sphere
type:
key:
db:
primitives[]
primitives[0]:
type: 2
dimensions[]
dimensions[0]: 0.01
primitive_poses[]
primitive_poses[0]:
position:
x: 0
y: 0
z: 0
orientation:
x: 0
y: 0
z: 0
w: 1
meshes[]
mesh_poses[]
planes[]
plane_poses[]
subframe_names[]
subframe_poses[]
operation: 0
octomap: ...
is_diff: 0 Scene Diff of first sub trajectory name: (noname)
robot_state: ...
world:
collision_objects[]
collision_objects[0]:
header:
seq: 0
stamp: 0.000000000
frame_id: base
pose:
position:
x: 0
y: 0
z: 0
orientation:
x: 0
y: 0
z: 0
w: 1
id: sphere
type:
key:
db:
primitives[]
primitives[0]:
type: 2
dimensions[]
dimensions[0]: 0.01
primitive_poses[]
primitive_poses[0]:
position:
x: 0
y: 0
z: 0
orientation:
x: 0
y: 0
z: 0
w: 1
octomap: ...
is_diff: 0
|
captain-yoshi
added a commit
to captain-yoshi/moveit_task_constructor
that referenced
this issue
Dec 16, 2024
captain-yoshi
added a commit
to captain-yoshi/moveit_task_constructor
that referenced
this issue
Dec 16, 2024
captain-yoshi
added a commit
to captain-yoshi/moveit_task_constructor
that referenced
this issue
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think part of #432 introduced the redundant msgs.
Setting a planning scene in the
FixedState
stage results in having identical scene msgs when filling the solution :The text was updated successfully, but these errors were encountered: