During the SR2017 competition event, we shipped an update to libkoki to the robots. This shipped libkoki d99631f1 out to the robots. This patched version of libkoki did not reach this repository until yesterday, and is not yet merged into master :) There are currently conclusions floating around out there about what markers libkoki can and can't see, and most of these are possibly based on the libkoki from master, which is not actually what the robots are running!
My memory is that the patch shipped during the SR2017 competition in order to make the robots be able to see whatever marker it was at the time that they couldn't. I remember this being successful, and happened because I had some patches to libkoki lying around (and luckily I still do, hence the push yesterday!) from using it in my PhD work.
We need to work out what markers can actually be seen by libkoki after the patch referenced above has been merged.
During the SR2017 competition event, we shipped an update to libkoki to the robots. This shipped libkoki d99631f1 out to the robots. This patched version of libkoki did not reach this repository until yesterday, and is not yet merged into master :) There are currently conclusions floating around out there about what markers libkoki can and can't see, and most of these are possibly based on the libkoki from master, which is not actually what the robots are running!
My memory is that the patch shipped during the SR2017 competition in order to make the robots be able to see whatever marker it was at the time that they couldn't. I remember this being successful, and happened because I had some patches to libkoki lying around (and luckily I still do, hence the push yesterday!) from using it in my PhD work.
We need to work out what markers can actually be seen by libkoki after the patch referenced above has been merged.