-
#11 bug
-
New home position is not always the closest to desired ik 0 of 3 tasks completed
-
Paper 6 of 12 tasks completed
-
multiple pybullet instances simultaneously for running experiments 0 of 3 tasks completed
-
Swept volume collision check in pybullet 6 of 6 tasks completed
-
Combined schedule 5 of 5 tasks completed
-
Check what collision regions between pairs of trajectories look like 3 of 3 tasks completed
-
save a plan and load it 2 of 2 tasks completed
-
handoff for executing plan on hardware 2 of 2 tasks completed
-
Dec-MCTS to real plan 7 of 8 tasks completed
-
Make time for between-contour-trajectories realistic 0 of 3 tasks completed
-
Add buffer time for joint scheduler 2 of 2 tasks completed
-
Improve Dec-MCTS to real plan logic 2 of 3 tasks completed
-
CominedScheduler should only add plans to one arm if thats the most efficient 0 of 3 tasks completed
-
Zone blocking 2 of 2 tasks completed
-
decmcts and greedy with a simple list of contours 4 of 4 tasks completed
-
Dec-MCTS full print 1 of 2 tasks completed
-
Dec-MCTS for 3 arms 2 of 3 tasks completed
-
Sample Print for Hardware demo 11 of 11 tasks completed
-
Run on bulk stl files for testing 12 of 13 tasks completed
-
Align planning parameters with true hardware 3 of 4 tasks completed
-
Sample Print for Hardware demo 2 3 of 3 tasks completed
-
Move slightly up and down between contours 2 of 2 tasks completed
-
Greedy 3 arm test 3 of 3 tasks completed
-
Use calibrated arm and tip positions 3 of 3 tasks completed
-
Plan fails when there are impossible contours 4 of 6 tasks completed
-
Collision check against completed layers 3 of 5 tasks completed
-
Create test plans for hardware testing for one arm 5 of 6 tasks completed
-
JointScheduler bugs 7 of 7 tasks completed
-
JTraj for contours are not always executable 1 of 1 task completed