Closed TheOne-1 closed 1 year ago
@TheOne-1 What exactly is the issue? Does the loadGRF
call fail, or does it load the data incorrectly?
It loaded the data incorrectly. I can't remember very well but it's probably related to the sampling rate, which was not loaded as 200 Hz.
I think it's possible that this was fixed in the latest revision of the GRF loader, which now always gets exactly the desired timestamps in the output, even if it has to linearly interpolate between frames.
nimble.biomechanics.OpenSimParser.loadGRF was not working properly with such kind of timestamp: If I round the timestamp with 3 digit precision as follows, the function worked properly. repeat the issue.zip