Currently, footprint update has a few issues:
- boundary expansion - feature missing. unsure if needed since merging is in place. This operation is also expensive, costing tens of microseconds within each loop.
- tolerance - need some kind of graceful failure for when footprint estimate just isn't good enough at the moment, and we have to wait until more frames have come in.
Currently, footprint update has a few issues: