Time vectors for raw_force and cds.enc.kin are sometimes not aligned (handleForceFromRaw.m)

[raeedcho]

Temporary fix by rounding time vectors to sample rate precision.

[mattperich]

handleForceFromRaw is still broken... the number of inputs defined in commonDataStructure and passed in during forceFromNSx is different from the inputs defined in the header of handleForceFromRaw, and in the subsequent code. Clearly someone had a plan there, but I don't think it got implemented properly...

The temporary fix Raeed implemented breaks on the file I'm trying to convert right now. The force actually seems to align properly with the time vector of the kinematics, and the rounding fix breaks that...

[tuckertomlinson]

this is persistent. The essential problem is that we occasionally get a timestamp that, due to machine precision, is included in one timeseries but not the other. We have addressed this on an ad-hoc basis by fiddling with the roundTime function, but that's obviously just pushing the problem around.

I think the 'correct' solution is to do something like:
-detect the error
-identify which series has the extra point
-confirm no duplicate time points
-confirm no missed timepoints in shorter series
-identify whether extra point is at beginning or at end of series
-truncate series