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.

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

Questions on Converting .p Files in robot0 Folder and Modifying Task Runners for Custom Tasks #14

Open
ondals opened this issue Jan 24, 2024 · 0 comments

Comments

@ondals
Copy link

ondals commented Jan 24, 2024

Hello,

I've been working with the [demo] project and encountered a couple of issues that I need some guidance on. I successfully converted initial_configs.p and target_object_names.p in the benchmark folder from .p to .json, modified them, and converted them back to .p, which worked fine. However, I'm facing issues with the .p files in other folders, such as robot0.

Issue with Converting .p Files in robot0 Folder:
I tried a similar approach to convert and modify .p files in the robot0 folder but encountered errors during execution. I suspect that something might be getting lost or misinterpreted during the conversion process. Could you provide insights on what the .p files in these folders should contain or if there's a specific structure or content that I need to maintain while modifying these files?
image

Customizing Task Runners for Specific Tasks:
Additionally, I am interested in using this model to plan tasks where only the initial state and goal pose are provided, without the need for grasping and manipulating objects. Is it possible to modify the prepare_task_runners function to configure tasks based solely on initial states and goal poses? If yes, could you provide some guidance or examples on how to achieve this?

Any assistance or pointers on these matters would be greatly appreciated. Thank you for your support and for the great work on this project.

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

No branches or pull requests

1 participant