[ml] non constant input

Eric Glover eric at ericglover.com
Mon Jun 15 23:22:28 UTC 2009

I was not able to make it last Weds: (just changed my list address to be 
the same as my from):

Just to ask a stupid question - but aren't we going to use filtering 
(see the types below) to average things out and remove 'noise'

Simply put, if there is less than some given delta - then ignore the "point"

We should also be doing smoothing/averaging if necessary - the paper we 
had discussed a few weeks ago talks in some detail about the different 
filtering/smoothing they did.

Also - I recommend we do a z-rotation normalization - so no matter how 
they hold it at least the "Z-plane" lines up.


Almir Karic wrote:
> by take in account you mean sort the input or something more complicated? 
> On Mon, Jun 15, 2009 at 01:42:17PM -0700, Michael C. Toren wrote:
>> On Sat, Jun 13, 2009 at 04:10:42AM +0200, Almir Karic wrote:
>>> regarding the non constant input we got from the wiimote, is it
>>> possible that it is due to BT and not to wiimote itself? 
>> That sounds possible to me, but I'm not very familiar with bluetooth,
>> and I'm not sure what type of experiment we could design to test that
>> hypothesis.  More importantly, though, even if it is due to bluetooth
>> issues rather than the wiimote itself, it's still something I think
>> we'll need to take into account if we want to make use of the device.
>> -mct
> _______________________________________________
> ml mailing list
> ml at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/ml

More information about the ml mailing list