wba.py always outputs odd values for trajectories

alexandroid000 / self-assembly

weaselballs are hard to control on their own. what if we stick them together?

7 stars 2 forks source link

wba.py always outputs odd values for trajectories #5

Open austinborn opened 5 years ago

austinborn commented 5 years ago

I have not checked on the most recent commit to the reorganization branch for open_cv, but it appears that the trajectory values are always odd integers. Could be an off-by-one issue or floor or ceiling calculations, but I haven't taken a closer look yet.