Add path shortening utils and consolidate examples#33
Conversation
sea-bass
left a comment
There was a problem hiding this comment.
you know me, reviewing the draft PRs like a sociopath
Co-authored-by: Sebastian Castro <4603398+sea-bass@users.noreply.github.com>
Uh oh. |
Gahh... so I guess I either need to pay up or we make this repo public. Preferences? |
Third option, move it to an org? Would that reset the count? |
Yeah I think that's what I meant by making it public. The org itself cannot be private, and I'm additionally not sure right now if one can have a private repo in a free tier org. I can check later. |
|
4th option: Give me permissions and I'll add this to my linux runner under my desk. |
|
Your CI is back, kind sir. |
Thank goodness I can see that broken rolling build, again. |
|
Ah gonna stop playing with this since I think this is a reasonable functional baseline. |
| from roboplan.viser_visualizer import ViserVisualizer | ||
|
|
||
|
|
||
| def visualizePath( |
There was a problem hiding this comment.
So once the Franka PR lands, I think this is what we'll need:
- Factor out the existing
visualizePathto two separate functions,visualizeRRTandvisualizePath, which accepts the name of the thing to visualize as an input arg. - The original example will call one of each
- This example will call
visualizeRRTonce, andvisualizePathtwice (for the raw and shortcutted paths)
There was a problem hiding this comment.
Follow-up: Maybe we instead just want to modify the existing RRT examples and add a flag for whether we want shortcutting or not?
There was a problem hiding this comment.
Done and done.
I'm assuming it's preferable just to have all of the configurable parameters directly in code rather than adding arguments or something to these example scripts to do more code consolidation?
There was a problem hiding this comment.
Either/or. Viser uses this other package named tyro which makes command line args pretty nice, if you wanna check it out. The viser examples are a good reference.
There was a problem hiding this comment.
Oh that is need. Do you want to tackle that here? I would probably merge the ik and rrt examples together and make everything an argument, including the robot models. Thoughts?
There was a problem hiding this comment.
That sounds great -- up to you if you wanna split it off or club it all together.
Working on it but my little machine is on the struggle bus right now. |
I'll let you in on a secret. I never actually built Pinocchio for my visualizer PRs. I just added the files to my install space and copied them into the repo when they worked. |
Rule number 1: I never half-ass anything. I'm a whole-ass man. |
|
That's a lovely ball of yarn. |
|
Sigh. Does anyone like ros? (I do) |
I ran into this pain too. Just pin the typing_extensions version in your install command: roboplan/.docker/ros/Dockerfile Line 31 in 7af1866 Or you can pin tyro itself. See brentyi/tyro#324 |


Resolves #19.
Shamelessly converting https://github.com/sea-bass/pyroboplan/blob/main/src/pyroboplan/planning/path_shortcutting.py.
The quality of the example is highly dependent on the original path, but I suppose that's to be expected. Here's a good run: