Richard Veale

OK so on windows you found some file named 4.2.762.0? Sorry, please clarify -- You found the velocity columns are "broken anyway"? What do you mean? You mean they contain...

Sorry, the bug is for the velocity columns, but the original issue in pyedfread (reading too many tokens/rows) was not fixed by the SDK update (it was an error in...

This update adds some default arguments to parse(), so it results in the same original behavior by default, but also gives options to exclude velocity data if you know your...

But, this is not clean code, if you will merge to the mainline, let me do a clean checkout and fork and only one checkin.

To reproduce the "issue", run read_edf on any data recorded at 2000 Hz. Samples will be doubled up in "time", i.e. every pair of adjacent rows will have the same...

OK, here is an example function to compute the correct times (only where necessary) using the flags. It also adds an "iflags" (int16) column in case users want to use...

Hey, nice that you solved it before! Regarding out-of-order, I see it quite often, but I am figuring it out why. It seems it may be some kind of issue...

Yes, I am definitely hitting a repeated but random issue in which pyedfread continues to "read" past the end of the EDF file samples. I'm hoping it is a mis-sized...

EDIT: SOLVED -- it was a mis-sized samples array which is only partially used but the whole thing is returned. It is definitely reading past the number of samples in...