Closed aklos closed 1 year ago
This should already work - just set edf_target
to end in .bdf
and it should automatically be saved with BDF+
However, this change should be fine as well.
could you also change the file name accordingly in line 697
and possibly a simple test to test_highlevel.py
?
then I'll merge.
This should already work - just set
edf_target
to end in.bdf
and it should automatically be saved with BDF+However, this change should be fine as well.
The issue is that I actually need a plain EDF (no annotations) to work with wfdb, so inferring from file extension isn't enough.
I'll make the requested changes, thanks!
right! so vanilla EDF. Then this check makes sense. I would not have thought that vanilla EDF is still used anywhere.
Does pyedflib
create valid vanilla EDF files? I do remember there to be some problems
They're valid enough that wfdb can process them. I suppose wfdb 4.0.0 now handles EDF/EDF+ without conversion, but a lot of algorithms still rely on using edf2mit which only accepts vanilla EDFs.
I'm very much a layman when it comes to this stuff. Just trying to get some heartbeat classification models working correctly and wfdb is really hard to understand.
looks good, thanks a lot!
drop_channels forces the target to EDF+ but it should allow you to choose the file type.