You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error("starting byte of a TAL must be '+' or '-'; found $sign")
(and there are probably be other ways that TAL parsing can go wrong).
Maybe a good way would be to add an option to not throw on TAL parse errors, and instead return a list of structured errors that tell you the offending byte range, alongside the requested EDF, to make it easier to fix the offending EDF bytes.
The text was updated successfully, but these errors were encountered:
Time-stamped
Annotations
Lists
If you need to deal with malformed TAL onsets, durations or annotations somehow, the irrecoverable errors that get thrown are not very helpful.
Two errors seen in the wild are
Float64
parse errors hereEDF.jl/src/read.jl
Lines 156 to 157 in f370e83
and here
EDF.jl/src/read.jl
Line 167 in f370e83
(and there are probably be other ways that TAL parsing can go wrong).
Maybe a good way would be to add an option to not throw on TAL parse errors, and instead return a list of structured errors that tell you the offending byte range, alongside the requested EDF, to make it easier to fix the offending EDF bytes.
The text was updated successfully, but these errors were encountered: