ros-industrial-consortium / scan_n_plan_workshop

53 stars 30 forks source link

Modified behavior tree to allow immediate replanning upon tool path planner modification #104

Closed gopikaajaykumar closed 4 months ago

gopikaajaykumar commented 5 months ago

Edited the behavior tree and related to code to allow the user to re-generate the tool path plan immediately upon tool path planner modification

marip8 commented 5 months ago

Can you add a screen capture of what this change does/looks like in the GUI?

gopikaajaykumar commented 5 months ago

image

When the user opens the tool path planner GUI to make modifications to the tool path plan after generating a tool path plan, the UI now has the "Generate Tool Path Plan" option enabled so they no longer have to navigate to the previous page to regenerate the tool path plan.

marip8 commented 5 months ago

Can you add a screen capture of what this change does/looks like in the GUI?

By this I meant that I would like for you to record a video of your screen while you demonstrate the changes. I think I understand what you are trying to do from the code changes, but I'm not entirely sure

gopikaajaykumar commented 5 months ago

Below is a video showing how the application works now (using snp_automate_2022). The relevant part showing tool path replanning starts at 00:20.

https://github.com/ros-industrial-consortium/scan_n_plan_workshop/assets/15222261/eef2892f-b7c1-47b8-b927-d0c70b6c0c27

marip8 commented 5 months ago

I think there is too much "stateful" logic in this single block, and I think it would be better and more clearly implemented as a sub-tree or modification to the existing tree instead. If I understand this correctly, you are trying to use the TPP config tool button to interrupt the task of motion planning approval to put you back into the task of tool path planning approval. It seems like you could accomplish that with the existing blocks like this:

tree

Then you would only need to add the tppconfig button to the blackboard to get the behavior you are looking for

gopikaajaykumar commented 5 months ago

Thanks, I'll try the alternative approach you suggested

marip8 commented 4 months ago

@gopikaajaykumar @DavidSpielman any follow up on whether the change to the BT file per my suggestion resulted in the behavior you were looking for?

DavidSpielman commented 4 months ago

@gopikaajaykumar @DavidSpielman any follow up on whether the change to the BT file per my suggestion resulted in the behavior you were looking for?

I haven't gotten a chance to test this behavior yet.

marip8 commented 4 months ago

Closing in favor of #119

gopikaajaykumar commented 3 months ago

@marip8 @DavidSpielman Sorry this is late, but I just tried the latest code with Michael's behavior tree update and (not sure if I am doing something wrong/misunderstanding) it seems like it's back to the original behavior where you have to click Back to get the Generate Tool Path Plan button to become enabled.

Screencast from 06-20-2024 05:32:05 PM.webm ^ Don't know if it's clear from the video but I click Back first to get the button to get enabled again after modifying the tool path plan parameter