search

IEEERobotics / high-level

CV, localization, mapping, planning, and generally anything that will run on the PandaBoard
BSD 2-Clause "Simplified" License
2 stars 1 forks source link

goToNextDropOff is not defined #28

Closed dfarrell07 closed 11 years ago

dfarrell07 commented 11 years ago

Planner currently fails because goToNextDropOff is not defined. It doesn't seem to be anywhere in the repo, so it's not a self.* issue.

daniel:~/Robot/current/fresh/high-level/qwe$ grep -rni "goToNextDropOff" ./*
./planning/Planner.py:149:          goToNextDropOff(armList[0], "sea")
./planning/Planner.py:152:          goToNextDropOff(armList[1], "sea")
./planning/Planner.py:159:          goToNextDropOff(armList[0], "land")
./planning/Planner.py:162:          armId = goToNextDropOff(armList[1], "land
")
./planning/Planner.py:168:          goToNextDropOff(armList, "sea")
./planning/Planner.py:172:          goToNextDropOff(armList, "land")
./planning/Planner.py:179:          goToNextDropOff(armList[1], "sea")
./planning/Planner.py:183:          goToNextDropOff(armList[0], "land")
Binary file ./planning/Planner.pyc matches
daniel:~/Robot/current/fresh/high-level/qwe$

It may not be possible to recreate this bug until comm echos my move commands or I clean up the nav-loc hack @jschornick and I implemented that gets the code execution past this limitation. That shouldn't matter too much, as the bug is obvious.

ghost commented 11 years ago

fixed...