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

Change Rhino visualization to work on Actions/States instead of hardcoded key-positions #43

Open
yck011522 opened this issue Aug 5, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request ITJ_Library Core ITJ Library / Geometry / Assembly / Process

Comments

@yck011522
Copy link
Member

No description provided.

@yck011522 yck011522 self-assigned this Aug 5, 2021
@yck011522 yck011522 added enhancement New feature or request ITJ_Library Core ITJ Library / Geometry / Assembly / Process labels Aug 5, 2021
@yck011522
Copy link
Member Author

The first problem is that visualizing Actions / Movements step-by-step is very slow. There are too many steps. And some steps are not important. Therefore the previous method of using KeyPositions are much more efficient.

  • Alternative solution: Modify Visualize Movement to automatically check for collision and skip to only visualize problematic Movements. Then completely abandon Grasp Pose Tab.

The second problem is that the Key Position gives an overview of all objects in their key moments, for example:

  • All Clamps and Gripper in the final moments before clamping and retracting.
  • All Clamps in the moments before attach and detach to beam. (2 attach + attached + 2 detach steps)
  • Gripper Retract after placement

The current KeyPositions combined the positions of multiple Movements for attaching and detaching tools in one big picture.

The intention to visualize these KeyPositions is for user to make adjustment to Tool Attachemnt / Gripper Grasp / Choice of Tool / Choice of Assembly Method. However, when these options are not yet valid, the auto-dependency computation may be invalid. I'm not sure, but this may not be able to generate Action and Movements for using them for visualization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ITJ_Library Core ITJ Library / Geometry / Assembly / Process
Projects
None yet
Development

No branches or pull requests

1 participant