instantreality 1.0

• node reference
• tutorials
• tools
• devices
• api
• forum
• home

MotionFilter

supported on WIN32LinuxDarwin

Node for filtering out erroneous pieces of tracker data and for data prediction to compensate latency.

Please check out the tutorial on input/output streams for further information on how to use devices. Due to technical reasons the input and output fields of a device can only be determined at runtime and therefore do not appear in this interface description. Use the "Web Interface Device Management" entry in the "Help" menu of a running InstantPlayer to determine available input and output fields of a device.

Inheritance

• IONode 56
• MotionFilter

Code

XML encoding

<IOSensor type="MotionFilter" PosBufferSize='33'
PosMonotonyLength='4'
OriBufferSize='33'
OriMonotonyLength='4'
 />

Classic encoding

IOSensor {
	type "MotionFilter"
	PosBufferSize "33"
	PosMonotonyLength "4"
	OriBufferSize "33"
	OriMonotonyLength "4"
}

Interface

Filter: X3D only | Avalon only | All

id	Name	DataType	PartType	Default	ValueType	Description
	OriBufferSize	SFString	initializeOnly	33		The number of orientations to be stored in the buffer. Usually, the default should work well. 15 or 33 are suggested.
	OriMonotonyLength	SFString	initializeOnly	4		Number of orientations to use for the monotony test. 0 forces the assumption of monotony.
	PosBufferSize	SFString	initializeOnly	33		The number of positions to be stored in the buffer. Usually, the default should work well. 15 or 33 are suggested.
	PosMonotonyLength	SFString	initializeOnly	4		Number of positions to use for the monotony test. 0 forces the assumption of monotony.