AssignMeasurementsToLeds.h File Reference

Header. More...

#include "BeaconIdTypes.h"
#include "LED.h"
#include <LedMeasurement.h>
#include <boost/assert.hpp>
#include <opencv2/core/core.hpp>
#include <algorithm>
#include <cstddef>
#include <iostream>
#include <iterator>
#include <stdexcept>
#include <tuple>
#include <utility>
#include <vector>

Go to the source code of this file.

Classes
class	osvr::vbtracker::AssignMeasurementsToLeds

Namespaces
	osvr
	The main namespace for all C++ elements of the framework, internal and external.

Functions
bool	osvr::vbtracker::handleOutOfRangeIds (Led &led, const std::size_t numBeacons)
	In theory this shouldn't happen, but there are checks scattered all over the code. More...
float	osvr::vbtracker::sqDist (cv::Point2f const &lhs, cv::Point2f const &rhs)
	Get the squared distance between two OpenCV points.

Detailed Description

Header.

Date

2016

Author

Sensics, Inc. http://sensics.com/osvr

Function Documentation

handleOutOfRangeIds()

bool osvr::vbtracker::handleOutOfRangeIds ( Led &  led, const std::size_t  numBeacons  )

inline

In theory this shouldn't happen, but there are checks scattered all over the code.

Now we can say that it doesn't happen because we won't let any bad values escape this routine.

Todo:

a kinder way of doing this? Right now this blows away the measurement history