the periodic mapping also folds the incoming value into the allowed range. The resulting value will be ( N * period ) from the input value and inside the range, period being upper - lower. For splines done with PERIODIC boundary conditions, if the shape of the core for this axis is M, we'd pass 0 to _lower and M to _upper. More...

#include <map.h>

Inheritance diagram for vspline::periodic_gate< rc_type, _vsize >:

Public Types
typedef vspline::unary_functor< rc_type, rc_type, _vsize >	base_type

typedef vector_traits< IN, vsize >::type	in_v
	vectorized in_type and out_type. vspline::vector_traits supplies these types so that multidimensional/multichannel data come as vigra::TinyVectors, while 'singular' data won't be made into TinyVectors of one element. More...

typedef vector_traits< OUT, vsize >::type	out_v

Public Types inherited from vspline::unary_functor< rc_type, rc_type, vspline::vector_traits< rc_type > ::size >
enum

enum

enum

typedef rc_type	in_type

typedef rc_type	out_type

typedef vspline::vector_traits< rc_type >::ele_type	in_ele_type

typedef vspline::vector_traits< rc_type >::ele_type	out_ele_type

typedef vigra::TinyVector< in_ele_type, dim_in >	in_nd_ele_type

typedef vigra::TinyVector< out_ele_type, dim_out >	out_nd_ele_type

typedef vector_traits< rc_type, vsize >::ele_v	in_ele_v
	a simdized type of the elementary type of result_type, which is used for coefficients and results. this is fixed via the traits class vector_traits (in vector.h). Note how we derive this type using vsize from the template argument, not what vspline::vector_traits deems appropriate for ele_type - though both numbers will be the same in most cases. More...

typedef vector_traits< rc_type, vsize >::ele_v	out_ele_v

typedef vector_traits< rc_type, vsize >::nd_ele_v	in_nd_ele_v

typedef vector_traits< rc_type, vsize >::nd_ele_v	out_nd_ele_v

typedef vector_traits< rc_type, vsize >::type	in_v
	vectorized in_type and out_type. vspline::vector_traits supplies these types so that multidimensional/multichannel data come as vigra::TinyVectors, while 'singular' data won't be made into TinyVectors of one element. More...

typedef vector_traits< rc_type, vsize >::type	out_v

typedef vector_traits< int, vsize >::ele_v	ic_v
	vsize wide vector of ints, used for gather/scatter indexes More...

Public Member Functions
	periodic_gate (rc_type _lower, rc_type _upper)

void	eval (const rc_type &c, rc_type &result) const

template<typename = std::enable_if < ( _vsize > 1 ) >>
void	eval (const in_v &c, out_v &result) const

Public Attributes
const rc_type	lower

const rc_type	upper

Additional Inherited Members
Static Public Attributes inherited from vspline::unary_functor< rc_type, rc_type, vspline::vector_traits< rc_type > ::size >
static const bool	has_capped_eval

Detailed Description

template<typename rc_type, size_t _vsize = vspline::vector_traits < rc_type > :: size>
struct vspline::periodic_gate< rc_type, _vsize >

the periodic mapping also folds the incoming value into the allowed range. The resulting value will be ( N * period ) from the input value and inside the range, period being upper - lower. For splines done with PERIODIC boundary conditions, if the shape of the core for this axis is M, we'd pass 0 to _lower and M to _upper.

Definition at line 376 of file map.h.