Closed
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Contributor
Author
Ok, I'll just switch this PR to `rolling` and continue.In Since in Getting' Started section |
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
2 times, most recently
from
4ea1187 to
43c9536
Compare
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
5 times, most recently
from
6c4ac95 to
782c455
Compare
This comment was marked as resolved.
This comment was marked as resolved.
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
2 times, most recently
from
1b4fc0a to
1d8627d
Compare
This comment was marked as resolved.
This comment was marked as resolved.
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
from
1d8627d to
28de005
Compare
This was referenced Jun 12, 2023
Contributor
Author
Octomap is not showing.In This doesn't seem published. pointcloud is published (from the rosbag file). So use it. These prints expected values though. Found a set of params that look suspecious. With yaml: Result on param server: Maybe I should know how a code gets these params. UPDATE: All examples of ros2 parameter .yaml files I've seen so far use:But in my case, I tried this but no good? Resulted in: With yaml: Result on param server: Maybe I should know how a code gets these params. Also noticed: Found someone already ported moveit_tutorial to ros2 answers.ros.org#389233/moveit2-add-pointcloud2-to-occupancymapmonitor/. Swapping sensor config to sensor_3d.yaml, Hm, now this.Beginning of failure seems these: Pkg does exist and is reachable by ros2: For some reasons googling by So questions:
|
Contributor
Author
|
As ticketed #708, I found changes that are merged into moveit1's tutorial but not to moveit2's. Not sure if a culprit of the issue I'm seeing (i.e. no octomap shown) but I will test those as well. |
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
from
28de005 to
bb901d8
Compare
This comment was marked as resolved.
This comment was marked as resolved.
130s
added a commit
to 130s/moveit_resources
that referenced
this pull request
Jun 28, 2023
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
3 times, most recently
from
54d5e3c to
a432168
Compare
Okay so I tried this out in my humble workspace. I was indeed able to visualize the point cloud, and even plan around the obstacles it inserts, but this was not entirely straightforward. I had to make a couple of tweaks (ex: remove world->panda_link0 static tf from launch xml because its already published, and run the rosbag play separately after starting up everything else otherwise rviz would just crash). My biggest concern is the following messages : which goes up to handle 11. We can see it comes from here and here, but I am not sure what exactly this complains about. Missing TF for robot links? I can see in TF that robot frames are well published. I increased the @130s Any thoughts? |
Removing dep on panda_moveit_config and franka_description (instead, continue to depend on moveit_resources_panda pkgs)
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
from
a432168 to
1962b20
Compare
…e (unverified) decision moveit#704 (comment)) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
130s
added a commit
to 130s/moveit2_tutorials
that referenced
this pull request
Sep 27, 2023
…ent) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
130s
added a commit
to 130s/moveit2_tutorials
that referenced
this pull request
Sep 27, 2023
…address in PR moveit#700 (comment)) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
130s
commented
Sep 27, 2023
| + html_context["github_user"] | ||
| + "/moveit_resources/tree/ros2" | ||
| # + html_context["github_user"] | ||
| + "130s" |
Contributor
Author
There was a problem hiding this comment.
Reminder to revert the changes in this line and 2 lines below, once moveit/moveit_resources#181 is merged.
…ent) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp> Remove unnecessary functionality (moveit#700 (comment)) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
…address in PR moveit#700 (comment)) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
130s
force-pushed
the
feature-perceptionpipeline-ros2fy
branch
from
92aca72 to
9b7e620
Compare
Contributor
Author
|
Thanks for the review and testing! @Tejas-Shastha
Ok...Not sure why it fails on your env, but I removed that static publisher.
I'm unsure what's going on. If you can spot particular error output, would you mind posting (Can that look similar to moveit/moveit_resources#170?)?
Hm, no idea yet. |
I think the entity responsible for publishing this TF changes somewhere between all the configs. I would keep whatever works for the instructions of the tutorial (I did not test the tutorial environment, rather a custom environment of my own, so I am not sure what is correct either). Apologies if this created too much confusion! I also found out that the error I mentioned above: is caused by TF issues. I guess that since the bag contains only 1 msg and it is being relaunched at a pretty high rate, it messes up TF? I recorded my own bag and tried it and got the same results. However, on a real robot with a live feed from an Intel realsense D435, I did not have this issue at all (except once when the camera dropped some frames I think, which is what led me to conclude this is a TF issue). So, as you suggested, maybe it is sufficient to declare this phenomenon as a warning and move on? A separate issue can be raised to investigate this better. Overall, I tested the configuration suggestions you made with a real Panda FER1 and it works very well! (Again, my environment is somewhat different from what is prescribed in the tutorial). I think this PR adds sufficient value that it can be merged, I'm sure it would help many moveit users! P.S. : I am apparently unable to change my review from "Changes requested" for some reason. Please consider this as approved. |
Member
|
closes #708 |
|
@henningkayser Could you please review or push for a review of this PR? |
2 tasks
Contributor
Author
|
Closing as the similar work (that started after this PR) got merged and addressed the same issue #25. See more in #906 (comment) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue aimed at
Description of changes
git cherry-pickthose changes, but some PRs included changes outside of perception tutorial, which is not my scope of this PR, so I gave up and went ahead manually applying changes.Checklist
panda_moveit_configormoveit_resources_panda_moveit_config? Unclear the direction and rationale #704panda_moveit_configormoveit_resources_panda_moveit_config? Unclear the direction and rationale #704 (comment)moveit_resources?Peek.2023-06-28.14-37.webm