Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

event latencies quantified by matlab vs python code offset by 1.66667ms #20

Open
darcywaller opened this issue Apr 6, 2023 · 0 comments

Comments

@darcywaller
Copy link
Contributor

The timing of the peak spectral event latency for spectral events quantified from demo data with the MATLAB versus Python version of the toolbox are offset by 1.66667ms (MATLAB events being exactly 1 sample point later at 600Hz). (Suspect but am not 100% certain that this discrepancy may partially have something to do with differences in decimal point precision between MATLAB and Python, as functions like np.arange on line 198 of spectralevents.py return 4 fewer decimal points which could contribute to a difference in timing - ex: 0.1767 vs. 0.17666667.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant